Skip to content

Conversions API Setup for Google Ads and Meta — The Practical Guide

· by Nazar Mazur · 4 min read

TL;DR

After iOS 14’s App Tracking Transparency, Meta lost ~30% of browser-side conversion signal. Google Ads has similar (though less dramatic) attribution loss. The fix is Conversions API (CAPI) for Meta and offline conversion imports for Google Ads — sending conversion events from your server directly to the ad platforms, bypassing browser restrictions. Three implementation paths: (1) native platform plugins (Shopify, WooCommerce, HubSpot have one-click CAPI/offline-conversion setups), (2) Zapier/Make automations connecting CRM events to the platforms, (3) server-side GTM with custom event forwarding. Implementing CAPI typically restores 20–40% of lost attribution and improves Smart Bidding performance by 30–50% within 30–60 days.

Why this matters now

Three structural changes have eroded browser-side conversion tracking since 2021:

  1. iOS 14 App Tracking Transparency (April 2021): Apple requires apps (including in-browser apps like Safari) to ask permission before tracking. Most users decline. Meta lost ~30% of conversion attribution.
  2. Third-party cookie deprecation: Safari (ITP), Firefox (ETP), and eventually Chrome are restricting third-party cookies that ad platforms use for conversion attribution.
  3. Ad blocker adoption: 25-40% of users now run some form of ad/tracking blocker, which blocks pixel firing entirely.

The result: if you rely only on browser-side pixels (Meta Pixel, Google Ads tag), Smart Bidding is making decisions on incomplete data. It optimizes for what it can see, which means it over-allocates to easier-to-track audiences and under-allocates to (often higher-value) privacy-conscious segments.

Conversions API is the server-side alternative. Your server sends conversion events directly to Meta/Google via API, bypassing the browser entirely. This is more reliable, more accurate, and resistant to all three of the above issues.

What’s different between Meta CAPI and Google Ads offline conversions

Worth clarifying terminology because the two platforms use different names for the same idea:

  • Meta Conversions API (CAPI) is Meta’s server-side conversion API. Events can be sent in real-time (purchase happened just now) or batched.
  • Google Ads offline conversion imports is Google’s equivalent. Events are typically batched (uploaded daily / hourly) and used for sales-cycle conversions like “lead became customer” or “free trial became paid.”
  • Google Ads enhanced conversions is a related but different thing — it sends hashed user data (email, phone) alongside the browser pixel event to improve attribution match rates. It’s complementary to offline conversion imports, not a substitute.

For maximum effect, you want all three running: enhanced conversions for browser-side accuracy improvement, offline imports for sales-cycle conversion data, and Meta CAPI for the equivalent on Meta.

Three implementation paths

Pick the path that matches your stack complexity and team capacity.

Path 1: Native platform plugins (easiest)

For e-commerce stores on Shopify:

  • Meta CAPI: install Meta’s official “Facebook & Instagram” app in Shopify Admin. Native integration. 5-minute setup. Quality of integration varies — verify events fire correctly in Meta Events Manager test tool.
  • Google Ads enhanced conversions: install Google’s “Google & YouTube” app in Shopify. Native enhanced conversions + GA4 enhanced ecommerce. 10-minute setup.
  • Offline conversion imports for refunds: requires a separate automation (see Path 2).

For WooCommerce:

  • Meta CAPI: PixelYourSite Pro plugin, or the free PixelYourSite + manual setup. ~30 minutes.
  • Google Ads: similar plugins exist or use GA4 enhanced measurement + Google Tag for Ads.

For HubSpot:

  • Meta CAPI: HubSpot’s native Meta integration includes CAPI event forwarding for closed deals. Set up in HubSpot → Marketplace → Meta Ads integration.
  • Google Ads offline conversions: HubSpot’s native Google Ads integration handles offline conversion imports for closed deals.

Pros: Fast, well-tested, maintained by the platform. Cons: Limited customization. You’re constrained to whatever events the plugin supports.

Path 2: Zapier / Make automations (middle ground)

When your CRM/billing system doesn’t have a native integration, automation platforms bridge the gap.

Example workflow: Stripe → Meta CAPI

  1. Trigger: New successful payment in Stripe.
  2. Filter: Only for first-time customers (so you’re not double-counting subscription renewals).
  3. Action: Send event to Meta CAPI with hashed email, transaction value, currency.
  4. Action (parallel): Send to Google Ads offline conversion import with the GCLID stored at signup.

Make.com has pre-built modules for Meta CAPI and Google Ads offline conversions. Zapier has them too but typically requires more middle-step glue.

Pros: Flexible, can route any event from any source to any destination. No engineering required. Cons: Per-task pricing scales poorly at high volume. Real-time-ness depends on the automation polling interval. Debugging requires familiarity with the platform.

Path 3: Server-side GTM (most powerful)

For accounts with engineering capacity, server-side Google Tag Manager (sGTM) gives you full control over conversion event routing.

The architecture:

  • Browser-side GTM sends events to your sGTM container (hosted on your own subdomain like gtm.yourbrand.com).
  • sGTM forwards events to Meta CAPI, Google Ads, GA4, and any other destinations you configure.
  • You can enrich events server-side with first-party data (customer ID, lifetime value, segment) before forwarding.
  • You can deduplicate browser-side pixel events with server-side events using event_id matching.

Setup steps:

  1. Provision sGTM server (Google Cloud Platform: $30-$100/month for small accounts, scales with traffic).
  2. Configure browser-side GTM to send events to your sGTM container.
  3. Install Meta CAPI tag template, Google Ads conversion tag template in sGTM.
  4. Configure dedupe with event_id.
  5. Test using Meta Events Manager test tool + Google Tag Assistant.

Pros: Maximum data quality and control. First-party data enrichment. Full debugging visibility. Cons: Requires engineering effort. Ongoing GCP cost. Best ROI on accounts spending $20K+/month in ads where the data quality lift justifies the engineering investment.

What events to send (and how to weight them)

For lead-gen / B2B:

  • Form fill (low value, ~$1-5)
  • Marketing qualified lead — MQL (post-scoring, ~$10-50)
  • Sales qualified lead — SQL (sales team accepted, ~$50-200)
  • Opportunity created (~$200-1000)
  • Closed-won deal (full deal value)

Each event gets sent to the platform as a conversion with appropriate value. Smart Bidding learns to optimize for closed-won deals over time as enough volume accumulates.

For e-commerce:

  • Add to cart (low value, ~$0.50, for top-of-funnel optimization)
  • Begin checkout (~$2)
  • Purchase (full transaction value)
  • Refund (negative value adjustment)
  • Customer LTV update (positive adjustment when repeat purchase happens)

For SaaS:

  • Free trial signup (~$10-30)
  • Activation event — meaningful product usage (~$30-80)
  • Trial-to-paid conversion (full ARR value or first MRR × 12)
  • Expansion event (upgrade/upsell value)
  • Churn event (negative adjustment)

How long until you see results?

Smart Bidding doesn’t react instantly to new conversion data. Expect this timeline:

  • Week 1: Events flowing reliably. Verify in Meta Events Manager test tool and Google Ads Conversion Diagnostics. Fix any “low quality match” warnings.
  • Week 2-4: Smart Bidding begins to recalibrate. You may see CPM/CPC shifts, sometimes performance regresses briefly while the algorithm relearns.
  • Week 4-8: Stabilization. ROAS / CPA should improve vs. pre-CAPI baseline.
  • Week 8-12: Full benefit. The algorithm has accumulated enough conversion signal to optimize for real revenue, not just easy-to-track form fills.

Common implementation mistakes

Mistake 1: Browser-side pixel and server-side CAPI both sending the same event without deduplication. Result: Meta counts each conversion twice. Reported ROAS doubles, real ROAS doesn’t. Always set event_id deduplication.

Mistake 2: Sending only the “purchase” event server-side. Smart Bidding needs the full funnel for context. Send add-to-cart, begin-checkout, and purchase server-side, not just the final event.

Mistake 3: Not sending refund events as negative adjustments. Without refund adjustments, Smart Bidding optimizes for gross revenue, not net. Categories with high return rates (fashion 20-40%, electronics 10-15%) bleed margin on optimized-for-gross campaigns.

Mistake 4: Low match rate on hashed PII. Meta requires hashed email/phone/external_id for CAPI events to match back to user accounts. If your hashing is wrong, match rates drop to single digits and the events are useless.

Mistake 5: Not setting up enhanced conversions in Google Ads alongside offline imports. The two are complementary. Enhanced conversions improves browser-side attribution; offline imports adds sales-cycle conversion data. Set up both.

Practical action items

  1. Audit your current attribution gap. Compare Google Ads-reported conversions vs. GA4 conversions vs. actual CRM/Stripe data. Gaps > 20% indicate severe browser-side attribution loss.

  2. Pick an implementation path. If you’re on Shopify/HubSpot, native plugins are the right starting point. If on a custom stack, Zapier/Make is the middle ground. Above $20K/mo ad spend, invest in sGTM.

  3. Implement in this order: Meta CAPI first (biggest impact post-iOS 14), then Google Ads enhanced conversions (low effort, decent lift), then Google Ads offline conversions for sales-cycle data.

  4. Test for 60–90 days before evaluating impact. Smart Bidding needs time to relearn. Don’t make panic decisions in week 2.

  5. Monitor match rates and event quality in Meta Events Manager and Google Ads Conversion Diagnostics. These tell you whether the events are actually being usable, not just successfully transmitted.

If you’d like help implementing Conversions API or auditing whether your current setup is actually working, we offer free 30-minute audits. Book here.

Related reading:

Tagged

#conversions api#offline conversions#server-side tracking#smart bidding