What's the difference between GCLID click conversions and call matching?

GCLID conversions are deterministic — the click ID ties the call directly to its originating ad. Call matching is probabilistic and uses a confidence score based on time proximity (60% weight, ±120s) and duration similarity (40% weight, ±30s) to pair Google's call records to CallMatrix records when no click ID was captured.

Can I verify that Google actually received my uploads?

Yes. A one-click "Verify with Google Ads" action queries Google's offline_conversion_upload_client_summary endpoint and shows a daily breakdown, per-action diagnostics with actual error codes from Google, and a side-by-side "Our Records vs Google" comparison.

Is upload automatic or manual?

Both are supported. The Upload Schedule UI automates uploads every 1, 2, 4, 6, 8, 12, or 24 hours with per-campaign conversion-action mapping. An admin review workflow is available when you want to inspect matches, approve/reject, and confirm before upload.

How does CallMatrix prevent silent rejections?

Type validation guards run before every upload: GCLID uploads are only sent to compatible conversion action types. This prevents the common failure mode where Google accepts the API call but discards the data, and the full audit trail of payloads and responses makes any rejection traceable.

Conversion Upload

Q: What is Conversion Upload?

It is the module that reports qualified calls back to Google Ads as conversions. Calls that carry a GCLID (or gbraid/wbraid on iOS) are uploaded deterministically; calls without a captured click ID are matched probabilistically against Google's own call records.

Close the loop. Tell Google which clicks become revenue. Verify every upload.

What is Conversion Upload?

Conversion upload is the step that tells Google Ads which calls became revenue, so the ad platform's bidding algorithm can learn from them. Calls tied to a click ID are uploaded deterministically; calls without one are matched probabilistically against Google's own call records using time-proximity and duration scoring — every upload verifiable against Google's offline-conversion diagnostics API.

Key Capabilities

Deterministic GCLID-based click conversion upload: calls captured via DNI with a GCLID (or gbraid/wbraid for iOS) are uploaded directly to Google Ads with conversion value, timestamp, and currency
Probabilistic call matching: matches Google Ads call records to client call records using a confidence scoring algorithm based on time proximity (60% weight, +/-120s window) and duration similarity (40% weight, +/-30s window)
Full audit trail: every upload record stores the exact JSON payload sent to Google plus the API response, so you can drill into any batch and see precisely what went out and what came back
Type validation guards: pre-upload checks ensure GCLID uploads only go to compatible conversion action types — prevents silent rejections where Google accepts the API call but discards the data
Upload Schedule UI: configurable start hour, upload frequency (every 1/2/4/6/8/12/24 hours), enable/disable toggle, and per-campaign conversion action mapping — all from the dashboard
Verify with Google Ads: one-click query to Google's offline_conversion_upload_client_summary to confirm uploads were received, with daily breakdown, per-action diagnostics with actual Google error codes, and a side-by-side "Our Records vs Google" comparison
Admin review workflow: run matching → review matches with confidence scores → approve/reject → preview upload (dry-run) → type conversion action name to confirm → upload

Key Benefit

Every qualified call that originated from a Google Ads click gets reported back as a conversion — with full transparency into what was sent, what Google accepted, and what needs attention. No more black-box uploads.

Real-World Use Case

Law Firm Conversion Attribution

A law firm's campaign generates 500 calls/month from Google Ads. Of those, 180 are qualified leads worth an average of $120 each. CallMatrix matches 165 of the 180 to their original Google click using GCLID (deterministic) or call matching (probabilistic). The $19,800 in conversion value is uploaded to Google Ads, and the firm's Target ROAS bidding strategy immediately begins optimizing toward high-value keywords.

Request a Demo Request a Demo

Frequently Asked Questions

Stop Leaving Revenue on the Table

Join hundreds of businesses who switched to CallMatrix and cut their call routing costs by 40%.

Request a Demo

What is Conversion Upload?

Key Capabilities

Deterministic GCLID-based click conversion upload: calls captured via DNI with a GCLID (or gbraid/wbraid for iOS) are uploaded directly to Google Ads with conversion value, timestamp, and currency

Probabilistic call matching: matches Google Ads call records to client call records using a confidence scoring algorithm based on time proximity (60% weight, +/-120s window) and duration similarity (40% weight, +/-30s window)

Full audit trail: every upload record stores the exact JSON payload sent to Google plus the API response, so you can drill into any batch and see precisely what went out and what came back

Type validation guards: pre-upload checks ensure GCLID uploads only go to compatible conversion action types — prevents silent rejections where Google accepts the API call but discards the data

Upload Schedule UI: configurable start hour, upload frequency (every 1/2/4/6/8/12/24 hours), enable/disable toggle, and per-campaign conversion action mapping — all from the dashboard

Verify with Google Ads: one-click query to Google's offline_conversion_upload_client_summary to confirm uploads were received, with daily breakdown, per-action diagnostics with actual Google error codes, and a side-by-side "Our Records vs Google" comparison

Admin review workflow: run matching → review matches with confidence scores → approve/reject → preview upload (dry-run) → type conversion action name to confirm → upload

Real-World Use Case