Requesting a CallTrackingMetrics (CTM) connector. Windsor currently has callrail but no CTM equivalent — get_fields on both calltrackingmetrics and call_tracking_metrics returns “We don’t have this connector yet!”
Use case. We are a Phoenix behavioral healthcare provider running Google Ads and Microsoft Ads across two brands (Google Ads accounts 409-857-7460 and 295-621-2817, Bing account 187183834, all already connected to Windsor). Inbound phone calls are the primary conversion — roughly 340 inbound calls per week — and CTM is our call tracking platform. We grade every call for lead quality and upload a dollar value back to Google Ads against the GCLID as an offline conversion.
Because there is no CTM connector, we cannot join call-level attribution data to the Google Ads and Bing Ads data we already pull from Windsor. That join is the entire analysis: cost per qualified call by campaign, GCLID capture rate by tracking number, and click-ID coverage as a data-quality measure. Today we work around it by having CTM email a scheduled CSV report, catching it in Make, and dropping it in Google Drive — which gives us a weekly file with no history and no ability to query alongside the ad platform data.
Fields that would matter most, using CTM’s own column names: Tracking # Label, Tracking #, Direction, Duration, Talk Time, Date, Google Click ID, MS Click ID, source, medium, campaign, campaign_id, adgroup_id, keyword, Device, Referral, Page, CallId, Account Id, Account Name. The two click-ID fields are the critical ones — they are what let call outcomes be joined back to ad spend.
CTM publishes a REST API (api.calltrackingmetrics.com/api/v1) with account-scoped key/secret authentication and a paginated calls endpoint, which should map cleanly onto the pattern the existing callrail connector already follows.
Happy to be a design partner or beta tester — we have live data across both brands and would use this daily.