Why it matters
Browser tags alone miss conversions when cookies break, checkout happens off-site, or values update after the first fire (refunds, subscription upgrades, modeled predicted lifetime value (pLTV)). Google's bidding algorithms only optimize on events Google can attribute to ad clicks or eligible enhanced-conversion matches.
The Conversion API path gives you a durable, auditable server channel: your systems send structured conversion rows with click IDs, timestamps, values, and hashed customer data. That supports value-based bidding at scale without relying on a human to export spreadsheets. Match quality (GCLID capture, Enhanced Conversions completeness) determines how much of your signal enters learning, similar in role to Event Match Quality (EMQ) on Meta CAPI.
For performance teams, the API is the activation pipe on Google web. The data warehouse holds history for modeling; it does not replace API delivery to Google.
Google Ads Conversion API
Churney's Google web activation path uses the Google Ads Conversion API, not manual uploads:
- First-party data and revenue history live in your data warehouse.
- Churney models user-level pLTV and designs value magnitude, timing, and conversion action mapping.
- Churney sends events directly to Google Ads via the Google Ads API:
- UploadClickConversions for new conversions with GCLID (and value where applicable)
- UploadConversionAdjustments when values restate (refunds, calibration updates)
- Enhanced Conversions for Leads hashed identifiers when GCLID is unavailable but match is still possible
- Campaigns run tROAS, Maximize conversion value, or related value goals.
- Teams measure lift vs BAU conversion optimization in a holdout or structured pilot.
This is programmatic server delivery. It is distinct from one-time offline conversion spreadsheets or generic "upload" language that hides API requirements.
Category variants
| Model | How the Conversion API shows up |
|---|---|
| Ecommerce / DTC | Purchase and modeled pLTV on click conversions; adjustments for refunds or net revenue signals. |
| Subscription app | Web subscribe or trial-start with modeled LTV; pure app flows may use GA4 Measurement Protocol or MMP paths instead. |
| SaaS / PLG | Lead or qualified-lead conversions with Enhanced Conversions for Leads when GCLID is missing on long sales cycles. |
Common mistakes
- Calling any offline import "the Conversion API." Manual CSV and API uploads solve different operational and match problems.
- Missing GCLID persistence from ad click to conversion. Without click ID, attribution and value learning shrink.
- Skipping Enhanced Conversions for Leads when forms drop GCLID. Hashed email/phone can recover match on lead flows.
- Sending values once and never adjusting. Refunds and calibration shifts may require
UploadConversionAdjustments. - Flat value on every row. Value-based bidding needs variance; otherwise Smart Bidding behaves like count maximization.
- Treating the data warehouse export as activation. Modeling input ≠ Google Ads API delivery.
Advertiser lens
| Role | What they ask | What good looks like |
|---|---|---|
| Head of Performance / UA | Are we uploading conversions Google can use? | Match rate dashboard, GCLID coverage, value variance by campaign. |
| VP Growth / CMO | Is server-side Google worth the eng lift? | Documented path from modeled value to live tROAS campaigns. |
| Marketing Analytics / Data Science | Are values and timestamps correct? | Reconciliation: data warehouse outcomes vs Google attributed conversions. |
| Data Engineering | Who owns the Google Ads API integration? | Service account, conversion action mapping, retry monitoring, PII hashing. |
| Finance / Procurement | Does this change ROI proof? | Platform metrics vs incremental readout agreed upfront. |
FAQ
What is the Google Ads Conversion API?
It is Google's server-side mechanism (via the Google Ads API) to upload click conversions and conversion adjustments with values and match keys, so Smart Bidding can learn from complete, timely data.
Is this the same as offline conversion uploads in the UI?
No. Manual offline uploads and scheduled CSV imports are operational paths. The Conversion API here means programmatic UploadClickConversions and UploadConversionAdjustments through the Google Ads API, which is what Churney uses for web activation.
What is UploadClickConversions?
A Google Ads API method to send new click-based conversions with GCLID, conversion action, time, and optional value and enhanced conversion data.
What is UploadConversionAdjustments?
An API method to restate or retract prior conversions (for example value changes after refunds or model recalibration). Important when true value diverges from the first uploaded amount.
What is Enhanced Conversions for Leads?
A Google match enhancement that sends hashed first-party customer data with conversions when GCLID alone is insufficient, common on lead-gen flows.
Do I need pLTV to use the Conversion API?
No. Many teams upload purchase value only. pLTV matters when optimization should rank users by expected long-term value before it is observable.
How does Churney send values to Google?
Churney reads from your data warehouse, models pLTV, and sends values through the Google Ads Conversion API on your behalf. See the data guide for integration readiness.
Not the same as
| Term | Difference |
|---|---|
| Manual offline conversion upload | UI or CSV workflow; not the programmatic API Churney uses. |
| GA4 Measurement Protocol | Sends events to Google Analytics 4; different product path, often used for app/analytics flows. |
| Meta Conversions API (CAPI) | Meta's server-side channel; parallel concept, different schema and diagnostics. |
| Data warehouse | System of record for modeling input; not the pipe that delivers values to Google Ads. |
