Set up conversion tracking with GA4, Consent Mode and Meta CAPI
A conversion tracking plan for ads: one primary goal per platform, Google Ads and GA4 without double counting, Consent Mode for EEA, UK and Swiss visitors, Meta Pixel plus Conversions API with deduplication, and CRM results sent back daily.
This is a practical, copy-paste process for you are about to spend on google or meta ads and need trustworthy conversion data. Use it when you want a clear structure, then add your own details.
Verified on 2026-10-2213 sources cited
Quick start
1. Pick the one action that matters most and that happens often enough. Make it the main goal on each platform. 2. Remove duplicate tags so nothing is counted twice. Leads count once per click. 3. If people from Europe, the UK or Switzerland visit, use a consent banner that sends Google's four consent signals before any tag loads. 4. On Meta, use both the Pixel and the Conversions API, sending the same event ID and name. 5. If sales close later, use enhanced conversions for leads and upload results from your CRM every day. 6. Test with preview and test modes, not fake purchases. 7. Compare the platforms with your CRM every week at first, then every month.
Before you start
- You need a full analytics tracking plan for product usage, not ad conversions. Create a marketing tracking plan (GA4 & events)
- You need a legal opinion on cookie consent; this task sets up the signals, it is not legal advice. Check data-privacy compliance gaps
Full method
How to use this method
- 1. Copy or downloadCopy the prompt below, or download the method file and attach it to your chat.
- 2. Paste into any AIChatGPT, Claude, Gemini or Copilot. Replace each [PLACEHOLDER] with your details, or let the AI ask you.
- 3. Add your materialAttach your own files, data or brief so the AI works from your facts, not guesses.
The prompt
Paste it as-is. The AI will ask for anything still in [BRACKETS].
# Set up conversion tracking with GA4, Consent Mode and Meta CAPI Method by Deepstory Research: deepstoryresearch.com/method/conversion-tracking-ga4-consent-capi You are a marketing measurement lead who sets up ad tracking that stays accurate under privacy rules. Follow the method below step by step. Goal: A conversion tracking plan for ads: one primary goal per platform, Google Ads and GA4 without double counting, Consent Mode for EEA, UK and Swiss visitors, Meta Pixel plus Conversions API with deduplication, and CRM results sent back daily. ## My inputs - Business and conversion: [BUSINESS_AND_CONVERSION] (example: B2B SaaS, demo request form) - Website platform and tag setup: [WEBSITE_PLATFORM_AND_TAG_SETUP] (example: WordPress, HubSpot forms, GA4 via Google Tag Manager) - Ad platforms: [AD_PLATFORMS] (example: Google Ads and Meta) - Visitor regions: [VISITOR_REGIONS] (example: India, plus some UK and EU) - Where sales close: [WHERE_SALES_CLOSE] (example: HubSpot CRM, sales call 2 to 4 weeks later) Before you start: if any input above is still in [BRACKETS] or missing, ask me for it in one short numbered list and wait. Do not guess. If I attached files (data, briefs, Deepstory evidence files), treat them as the primary source. ## Steps to follow 1. Define one primary conversion per platform, check it has enough volume, and set values and counting. 2. Map each conversion to its source: Google Ads tag, GA4 key event, Meta Pixel and Conversions API, or CRM. 3. Set up Consent Mode for EEA, UK and Swiss visitors, with defaults that load before any tag. 4. Connect Google Ads conversions without double counting GA4 imports and Ads tags. 5. Set up the Meta Pixel and Conversions API with a shared event ID and the same event names. 6. Plan CRM results: enhanced conversions for leads first, click IDs as backup, uploaded at least daily. 7. Test every conversion in preview and test modes, not with fake live conversions. 8. Write the reconciliation check: weekly at launch, then monthly. ## Deliver the output in this structure - Conversion map (event, source, primary or secondary, value, counting) - Volume check - Consent Mode plan - Google Ads conversion setup - Meta Pixel and Conversions API setup - CRM and offline conversion plan - Test checklist - Reconciliation check ## Quality rules - Never count the same action twice as a primary goal on one platform. - Do not treat consent setup as legal advice; tell the user to confirm it with their privacy adviser. - State the attribution window behind every number compared across tools. - Never ask for raw customer data; use column names or fake sample rows. - Label every number as FACT (with source and date), ESTIMATE (show the calculation) or ASSUMPTION. - If a Deepstory evidence file is attached, use its figures as the reference values and cite its source references; tag claims that are not from it as [UNVERIFIED]. - End with: the 3 assumptions that matter most, what would change the answer, and the single best next step.
What you need to give the AI
| Input | Placeholder | Example |
|---|---|---|
| Business and conversion | [BUSINESS_AND_CONVERSION] | B2B SaaS, demo request form |
| Website platform and tag setup | [WEBSITE_PLATFORM_AND_TAG_SETUP] | WordPress, HubSpot forms, GA4 via Google Tag Manager |
| Ad platforms | [AD_PLATFORMS] | Google Ads and Meta |
| Visitor regions | [VISITOR_REGIONS] | India, plus some UK and EU |
| Where sales close | [WHERE_SALES_CLOSE] | HubSpot CRM, sales call 2 to 4 weeks later |
Use it when
- You are about to spend on Google or Meta ads and need trustworthy conversion data.
- Ad platforms, GA4 and your CRM show very different numbers.
- You get EEA, UK or Swiss visitors and are not sure your consent setup is right.
Best with: A chat AI for the plan; a developer or Tag Manager for the setup.
What you get
- Conversion map (event, source, primary or secondary, value, counting)
- Volume check
- Consent Mode plan
- Google Ads conversion setup
- Meta Pixel and Conversions API setup
- CRM and offline conversion plan
- Test checklist
- Reconciliation check
The AI will ask you first
Answer these before the AI advises you; each one changes what it recommends.
What is the one action that matters most on each ad platform, how many happen a month, and is there a value for it?
Google recommends one consistent primary goal; a deep goal with very few conversions cannot train bidding.
If unknown: Purchases with order value for e-commerce; for leads, the highest-volume reliable lead event with a value, plus qualified-lead events as they build.
How are tags and forms installed today: Google Ads tag, GA4, Meta Pixel, Tag Manager, site plugins, third-party checkout or booking pages?
Duplicate tags cause double counting, and third-party checkouts break attribution without cross-domain setup.
If unknown: Audit the site with Tag Assistant and the Meta Pixel Helper first.
Do you get visitors from the EEA, UK or Switzerland, and which consent banner (CMP) do you use?
Google's EU user consent policy covers all three, and its tags need consent signals there for ad personalisation and measurement.
If unknown: Assume yes and plan a CMP that supports Consent Mode v2.
Is your business in health, finance, housing or jobs?
Meta limits some events and parameters for health and financial advertisers, and Google has stricter customer-data rules for sensitive categories.
If unknown: Ask; it explains many "events not received" problems.
Is the Meta Conversions API set up, with the same event ID and event name as the Pixel?
Without a matching event_id and event_name, Meta cannot deduplicate browser and server events.
If unknown: Assume Pixel only and plan the Conversions API next.
Do leads become sales later in a CRM, and does your form capture an email or phone and the click IDs?
Google recommends enhanced conversions for leads for new setups; click IDs are a backup, and uploads must arrive within 63 days (enhanced conversions) or 90 days (click ID).
If unknown: Plan enhanced conversions for leads with a native CRM connector, plus a hidden click-ID field.
Who has admin access to Tag Manager, GA4, Google Ads and Meta Business Suite, and are GA4 and Google Ads linked with auto-tagging on?
Importing GA4 key events needs linked accounts and auto-tagging, and changes need the right person to approve them.
If unknown: Check, and ask the admin to approve linking and auto-tagging before changing anything.
The procedure, step by step
Read this before you run it, so you can check the AI actually followed the method.
List conversions
One primary per platform, secondary for the rest, values where possible. Leads count "one" per click; purchases count "every", with a transaction or order ID for deduplication.
Audit tags
Tag Assistant and the Meta Pixel Helper. Remove duplicate tags and plugins. Set up cross-domain tracking and unwanted-referral lists for third-party checkout or booking pages.
Set up consent
A CMP that supports Consent Mode v2. Region defaults (denied for EEA, UK, Switzerland) load before any tag. All four signals. Basic or advanced mode, approved by the privacy adviser. Check Consent Mode diagnostics in Google Ads afterwards.
Set up GA4 key events
Mark the events as key events. Link GA4 and Google Ads and turn on auto-tagging, with the admin's approval.
Create Google Ads conversions
Google Ads tag with enhanced conversions as primary (turning on enhanced conversions accepts Google's customer data terms, so the admin does it). GA4 imports as secondary.
Set up Meta
Pixel plus Conversions API (direct, partner integration or Gateway) with a shared event_id and identical event names. Verify the domain. Check Event Match Quality.
Plan CRM results
Enhanced conversions for leads with a native CRM connector or Data Manager; hidden fields for click IDs and Meta click data. Upload at least daily. Set each offline conversion action's click-through window to cover the sales cycle (up to 90 days). Use conversion adjustments for refunds and disqualified leads.
Test and reconcile
Tag Manager preview, GA4 DebugView and Meta Events Manager test events. Avoid fake live conversions; if one is unavoidable, record it and retract it. Reconcile weekly for 4 to 6 weeks, then monthly.
Platform settings(show)
| Platform | Path | Setting | Note |
|---|---|---|---|
| Google Analytics 4 | Admin > Data display > Events > star icon | Mark as key event | Up to 30 key events on a standard property. |
| Google Analytics 4 | Advertising > Tools > Conversion management > New conversion | Create Google Ads conversions from key events | Needs linked accounts and auto-tagging. |
| Google tag / consent platform | Consent Mode configuration | ad_storage, ad_user_data, ad_personalization, analytics_storage | |
| Meta Events Manager | Dataset > Pixel and Conversions API events | Matching event_id and event_name for deduplication | |
| Meta Events Manager | Dataset > Overview > Event Match Quality | Event Match Quality score | Aim for Good or Great. |
| Google Ads | Goals > Conversions (or Data Manager) | Enhanced conversions for leads and offline conversion import | 63-day enhanced conversions window; 90-day click ID window. UI path as of October 2026. |
Worked example
The figures below are illustrative. Use your own numbers and facts.
Scenario: An Indian B2B SaaS company generating demo requests from Google and Meta, with some UK and EU visitors.
Input: WordPress, HubSpot forms, Google Tag Manager. GA4 live. Meta Pixel only. About 60 demo requests a month, about 12 become qualified, sales close 2 to 4 weeks later. Some UK and EU traffic. No consent banner.
Output excerpt: Google Ads: demo request stays primary with a value (about 60 a month); qualified demo added from HubSpot through enhanced conversions for leads with a higher value, uploaded daily, made primary only once it reaches about 30 a month. GCLID kept in a hidden field as backup. Meta: Lead from Pixel and Conversions API sharing one event_id, plus a server-only CRM "qualified" event through the Conversions API with the click and browser IDs captured on the form. Consent: a CMP with Consent Mode, defaults denied for EEA, UK and Switzerland, advanced mode subject to the privacy adviser. The Indian DPDP Act also applies to Indian visitors; flag it for the adviser.
Check your result
Before you trust the AI's output, confirm each of these.
- ☐ Each platform has exactly one primary conversion for the main goal, with enough volume to learn.
- ☐ Leads count "one"; purchases carry an order or transaction ID.
- ☐ Tag Manager preview shows the Google Ads conversion tag firing once, GA4 DebugView shows the key event, and Meta Test events shows the event; Google Ads has no test mode, so do not create a fake live conversion to check it.
- ☐ EEA, UK and Swiss visitors see a banner whose defaults load before tags and send all four signals.
- ☐ Meta Pixel and Conversions API events show as deduplicated.
- ☐ CRM results upload at least daily, and the reconciliation names the attribution window for every number.
What you'll get(show template)
## Conversion tracking plan: [BUSINESS] ### Conversion map Action | Platform | Source (tag / GA4 / CAPI / CRM) | Primary or secondary | Value | Counting | Monthly volume ### Consent CMP: [name] | Mode: [basic / advanced, approved by ..] | Defaults denied for: [EEA, UK, Switzerland, ...] | Signals: ad_storage / ad_user_data / ad_personalization / analytics_storage ### Google Ads Primary: [Ads tag + enhanced conversions / GA4 import] | Secondary: [..] | Auto-tagging: [on/off] ### Meta Pixel: [status] | Conversions API: [direct / partner / Gateway] | event_id and event_name shared: [yes/no] | Domain verified: [yes/no] | EMQ: [score] ### CRM results CRM: [name] | Method: [enhanced conversions for leads / Data Manager / connector] | Backup IDs: [GCLID, gbraid, wbraid, Meta click data] | Upload: [daily] | Adjustments: [refunds, disqualified] ### Tests [ ] Tag Manager preview | [ ] GA4 DebugView | [ ] Meta test events | [ ] CRM upload status ### Reconciliation (weekly for 4 to 6 weeks, then monthly) Platform | Count | Attribution window | Ratio to CRM | Change vs last period
Quality checks built into the prompt
- • Never count the same action twice as a primary goal on one platform.
- • Do not treat consent setup as legal advice; tell the user to confirm it with their privacy adviser.
- • State the attribution window behind every number compared across tools.
- • Never ask for raw customer data; use column names or fake sample rows.
- • Every number labelled FACT, ESTIMATE or ASSUMPTION; claims outside attached evidence tagged [UNVERIFIED].
Decision rules
If/then rules the AI should apply. Heuristic rules are a practitioner's rule of thumb, not a platform rule.
| If | Then | Type |
|---|---|---|
| You mark events in GA4 for ads. | Mark them as key events (Admin > Data display > Events > star). A standard property allows up to 30. | Platform rule |
| You import GA4 key events into Google Ads while a Google Ads tag also tracks the same action. | Keep only one as primary. Google sets key-event conversions to secondary when the account already has Analytics goals, so the same action is not counted twice. | Platform rule |
| The site gets visitors from the EEA, the UK or Switzerland and uses Google tags for ads. | Collect consent and send it with Consent Mode: ad_storage, ad_user_data, ad_personalization and analytics_storage, with defaults set to denied for those regions before any tag fires. The EU user consent policy covers all three regions; the consent types reference lists the four signals. | Platform rule |
| You set ad_user_data. | Pass it exactly as the visitor chose; never default it to granted in these regions. Google requires it for enhanced conversions and tag-based conversion tracking, so denied visitors reduce matched volume. | Platform rule |
| You choose between basic and advanced Consent Mode. | Basic blocks tags until the visitor chooses, nothing is sent if they decline, and Google uses a general conversion model. Advanced loads tags with consent denied and sends cookieless pings before any choice, which allows an advertiser-specific model. Have your privacy adviser approve the mode for your regions. | Platform rule |
| You run the Meta Pixel and the Conversions API together. | Send the same event_id and event_name from both. Server events are kept if no matching browser event arrived in the previous 48 hours. | Platform rule |
| Leads close later in a CRM and you have not set up offline imports before. | Start with enhanced conversions for leads, which Google recommends for new setups, and keep click IDs as a backup. Upload within 63 days (enhanced conversions) or 90 days (click ID) of the click. | Platform rule |
| You upload CRM conversions for Smart Bidding. | Upload at least daily, and let daily uploads run for 1 to 2 conversion cycles before counting that conversion for bidding. | Platform rule |
| A developer builds a new automated offline conversion upload. | Use Data Manager or the Data Manager API. Since 15 June 2026, Google Ads API offline conversion uploads fail for developer tokens that never sent them before. | Platform rule |
| You compare Meta numbers over time or against GA4 and the CRM. | Name the attribution window for each number; the Ads Insights API stopped returning 7-day and 28-day view windows on 12 January 2026. | Platform rule |
| A deeper event (qualified lead, closed deal) has low volume. | Keep the highest-volume reliable event primary with a value, add deeper events with higher values, and make the deeper event primary only once it reaches about 30 a month on Google or about 50 a week per Meta ad set.Threshold: about 30 a month (Google, rule of thumb); about 50 a week (Meta learning phase page) | Heuristic |
| Leads arrive by phone call, WhatsApp or chat. | Track them as their own conversions (call conversions with a minimum call length, click-to-WhatsApp or chat starts as secondary until qualified), and send qualified outcomes back from the CRM like other leads. | Heuristic |
| The main Meta event itself happens fewer than about 50 times a week. | Expect Meta ad sets to stay in learning; combine similar ad sets and set a realistic budget. Switching to a more frequent event that still predicts sales is a rule of thumb, not Meta guidance. | Platform rule |
| You choose which Google Ads source is primary. | Prefer the Google Ads conversion tag with enhanced conversions as primary, and keep GA4 imports as secondary for observation, unless only GA4 tagging is available. | Heuristic |
| You reconcile platforms with the CRM. | Compare each platform with its own trailing baseline and the CRM, and investigate week-on-week shifts of more than about 20% in the ratio rather than absolute gaps between platforms. For CRM comparisons, use click-only windows.Threshold: about 20% shift (rule of thumb) | Heuristic |
Failure modes
Common mistakes with this method, how to spot them, and how to fix them.
| Mistake | Symptom | Fix |
|---|---|---|
| Counting both the GA4 import and the Google Ads tag as primary for the same purchase. | Conversions roughly double in Google Ads, and Smart Bidding overbids. | Keep one primary; set the other secondary. |
| Lead forms set to count "every" conversion. | Inflated lead counts from repeat submissions. | Count "one" per click for leads. |
| Consent defaults that load after tags, or tags blocked with no Consent Mode signals. | EEA conversions drop and remarketing lists stop growing. | Load defaults first and send consent updates through Consent Mode. |
| Pixel and Conversions API without a shared event ID, or with different event name casing. | Meta reports more purchases than the shop sold. | Pass identical event_id and event_name from both. |
| Making a rare deep event (closed deal) the only primary goal. | Bidding cannot learn; spend stalls or swings. | Keep a higher-volume primary with values until the deep event has volume. |
| Hidden click-ID field emptied by a form plugin or caching, or iOS traffic without a GCLID. | Offline matches fall silently. | Use enhanced conversions for leads and test the hidden fields. |
| Testing with fake live purchases. | Fake conversions train Smart Bidding. | Use preview and test modes; retract any live test conversion. |
| Building a new Google Ads API offline upload. | Requests fail for tokens that never uploaded before 15 June 2026. | Use Data Manager or the Data Manager API. |
Agent mode: if an AI agent runs this unattended
May do without asking
- • Draft the conversion map, consent plan and tag specifications.
- • Review a Tag Assistant or Events Manager export that the user attaches.
- • Write test cases for each conversion.
Must stop before (the user decides and does these)
- • Publishing changes to a live Tag Manager container or website.
- • Changing consent settings on a live site.
- • Changing which conversions are primary or secondary, conversion values or counting, which changes bidding and spend at once.
- • Linking or unlinking GA4, Google Ads or Meta assets, or granting partner access.
- • Turning on enhanced conversions or accepting data processing or customer data terms.
- • Uploading CRM or customer data to Google or Meta.
- • Changing billing.
Evidence for this method
This method runs on your own material: your files, brief or code. If your task needs market or economic numbers, attach a sourced context file from the evidence library alongside the prompt.
Browse evidenceRun next
Methods that chain well after this one.
Deepstory methods are process guidance for AI tools. Review AI output before relying on it; legal, tax, medical and investment decisions need a qualified professional.