---
name: "Send lead outcomes from your CRM back to your ad platforms"
description: "Closes the loop between your CRM and Google Ads, Meta and LinkedIn: decides which lead stages and values to send, checks each platform’s matching keys, time limits and data rules, and sets when bidding should switch from form fills to qualified leads or customers. Used when ads bring plenty of leads, but sales says few of them are any good."
version: 2
verified_on: 2026-11-10
reverify_by: 2027-02-08
sources:
  - id: t1-g-ecl-upgrade
    title: "Upgrade offline conversion import to enhanced conversion for leads"
    url: https://support.google.com/google-ads/answer/14274408
    tier: T1
    accessed_on: 2026-11-05
  - id: t1-g-ec-settings
    title: "Updates to your enhanced conversions settings"
    url: https://support.google.com/google-ads/answer/16884284
    tier: T1
    accessed_on: 2026-11-05
  - id: t1-g-oci-faq
    title: "Offline conversion imports FAQs"
    url: https://support.google.com/google-ads/answer/10029210
    tier: T1
    accessed_on: 2026-11-05
  - id: t1-g-qual-conv
    title: "About qualified leads and converted leads"
    url: https://support.google.com/google-ads/answer/11459091
    tier: T1
    accessed_on: 2026-11-05
  - id: t1-g-ljm
    title: "About Lead Journey Mapping in Google Ads"
    url: https://support.google.com/google-ads/answer/17233846
    tier: T1
    accessed_on: 2026-11-06
  - id: t1-g-jab
    title: "Journey-aware bidding (Accelerate with Google announcement)"
    url: https://business.google.com/us/accelerate/announcements/journey-aware-bidding/
    tier: T1
    accessed_on: 2026-11-10
  - id: t1-g-primary
    title: "About primary and secondary conversion actions"
    url: https://support.google.com/google-ads/answer/11461796
    tier: T1
    accessed_on: 2026-11-10
  - id: t1-g-counting
    title: "About conversion counting options"
    url: https://support.google.com/google-ads/answer/3438531
    tier: T1
    accessed_on: 2026-11-05
  - id: t1-g-window
    title: "About conversion windows"
    url: https://support.google.com/google-ads/answer/3123169
    tier: T1
    accessed_on: 2026-11-05
  - id: t1-g-adjust
    title: "How to adjust your conversions"
    url: https://support.google.com/google-ads/answer/7686280
    tier: T1
    accessed_on: 2026-11-05
  - id: t1-g-sf
    title: "How to set up a Salesforce integration"
    url: https://support.google.com/google-ads/answer/13548778
    tier: T1
    accessed_on: 2026-11-05
  - id: t1-g-dm-sf
    title: "Salesforce (Google Ads Data Manager)"
    url: https://support.google.com/google-ads/answer/14006189
    tier: T1
    accessed_on: 2026-11-05
  - id: t1-g-cust-data
    title: "Customer data policies"
    url: https://support.google.com/adspolicy/answer/7475709
    tier: T1
    accessed_on: 2026-11-10
  - id: t1-g-eu-ucp
    title: "EU user consent policy"
    url: https://www.google.com/about/company/user-consent-policy/
    tier: T1
    accessed_on: 2026-11-05
  - id: t1-g-eea-consent
    title: "Updates to consent mode for traffic in European Economic Area (EEA)"
    url: https://support.google.com/google-ads/answer/13695607
    tier: T1
    accessed_on: 2026-11-05
  - id: t1-g-dm-send
    title: "Send events: Google Ads offline conversions (Data Manager API)"
    url: https://developers.google.com/data-manager/api/devguides/events/google-ads/offline/send-events
    tier: T1
    accessed_on: 2026-11-05
  - id: t1-m-cli
    title: "Conversions API for CRM integration"
    url: https://developers.facebook.com/documentation/ads-commerce/conversions-api/conversion-leads-integration
    tier: T1
    accessed_on: 2026-11-05
  - id: t1-m-cli-start
    title: "2: Getting started with the CRM integration"
    url: https://developers.facebook.com/documentation/ads-commerce/conversions-api/conversion-leads-integration/crm-integration/2-getting-started-with-integration
    tier: T1
    accessed_on: 2026-11-10
  - id: t1-m-cli-verify
    title: "4: Verify your data"
    url: https://developers.facebook.com/documentation/ads-commerce/conversions-api/conversion-leads-integration/crm-integration/4-verify-your-data
    tier: T1
    accessed_on: 2026-11-05
  - id: t1-m-cli-funnel
    title: "5: Configure your sales funnel"
    url: https://developers.facebook.com/documentation/ads-commerce/conversions-api/conversion-leads-integration/crm-integration/5-configure-your-sales-funnel
    tier: T1
    accessed_on: 2026-11-05
  - id: t1-m-cli-follow
    title: "6: Follow-up steps after CRM integration"
    url: https://developers.facebook.com/documentation/ads-commerce/conversions-api/conversion-leads-integration/crm-integration/6-follow-up-steps
    tier: T1
    accessed_on: 2026-11-05
  - id: t1-m-cli-payload
    title: "Conversion Leads payload specification"
    url: https://developers.facebook.com/documentation/ads-commerce/conversions-api/conversion-leads-integration/payload-specification
    tier: T1
    accessed_on: 2026-11-05
  - id: t1-m-cli-faq
    title: "Conversions API for CRM FAQ"
    url: https://developers.facebook.com/documentation/ads-commerce/conversions-api/conversion-leads-integration/faq
    tier: T1
    accessed_on: 2026-11-05
  - id: t1-m-perf-goals
    title: "About performance goals for lead ads"
    url: https://www.facebook.com/business/help/782657799338685
    tier: T1
    accessed_on: 2026-11-05
  - id: t1-m-crm-setup
    title: "Set up your CRM for qualified leads"
    url: https://www.facebook.com/business/help/279369167153556
    tier: T1
    accessed_on: 2026-11-05
  - id: t1-m-bt-terms
    title: "Meta Business Tools Terms"
    url: https://www.facebook.com/legal/businesstech
    tier: T1
    accessed_on: 2026-11-05
  - id: t1-li-capi-help
    title: "LinkedIn Conversions API"
    url: https://www.linkedin.com/help/lms/answer/a1655394
    tier: T1
    accessed_on: 2026-11-05
  - id: t1-li-csv
    title: "Manually upload a conversion data CSV file to Campaign Manager"
    url: https://www.linkedin.com/help/lms/answer/a796520
    tier: T1
    accessed_on: 2026-11-05
  - id: t1-li-leadgen-obj
    title: "Lead generation ad objective"
    url: https://www.linkedin.com/help/lms/answer/a422440
    tier: T1
    accessed_on: 2026-11-05
  - id: t1-li-hubspot
    title: "Set up HubSpot integration to send conversion data to Campaign Manager"
    url: https://www.linkedin.com/help/lms/answer/a6888207
    tier: T1
    accessed_on: 2026-11-05
  - id: t1-li-capi-doc
    title: "Conversions API (LinkedIn Marketing API)"
    url: https://learn.microsoft.com/en-us/linkedin/marketing/integrations/ads-reporting/conversions-api
    tier: T1
    accessed_on: 2026-11-05
  - id: t1-li-usecase
    title: "Conversions API use cases (LinkedIn Marketing API)"
    url: https://learn.microsoft.com/en-us/linkedin/marketing/conversions/conversions-usecase
    tier: T1
    accessed_on: 2026-11-05
  - id: t1-li-schema
    title: "Conversions API schema (LinkedIn Marketing API)"
    url: https://learn.microsoft.com/en-us/linkedin/marketing/integrations/ads-reporting/conversions-api-schema
    tier: T1
    accessed_on: 2026-11-05
  - id: t1-hs-google
    title: "Create and sync ad conversion events with your Google Ads account (HubSpot)"
    url: https://knowledge.hubspot.com/ads/create-and-sync-ad-conversion-events-with-your-google-ads-account
    tier: T1
    accessed_on: 2026-11-05
  - id: t1-hs-meta
    title: "Create and sync ad conversion events with your Meta Ads accounts using Meta’s Conversion API (HubSpot)"
    url: https://knowledge.hubspot.com/ads/create-and-sync-ad-conversion-events-with-your-meta-ads-accounts-using-metas-conversion-api
    tier: T1
    accessed_on: 2026-11-05
  - id: t1-hs-linkedin
    title: "Create and sync ad conversion events with your LinkedIn Ads account (HubSpot)"
    url: https://knowledge.hubspot.com/ads/create-and-sync-ad-conversion-events-with-your-linkedin-ads-account
    tier: T1
    accessed_on: 2026-11-05
  - id: t1-g-oci-about
    title: "About offline conversion imports"
    url: https://support.google.com/google-ads/answer/2998031
    tier: T1
    accessed_on: 2026-11-06
  - id: t1-g-dm-hubspot
    title: "HubSpot (Google Ads Data Manager)"
    url: https://support.google.com/google-ads/answer/15293735
    tier: T1
    accessed_on: 2026-11-06
  - id: t1-li-goal
    title: "Qualified leads optimization goal"
    url: https://www.linkedin.com/help/lms/answer/a6553958
    tier: T1
    accessed_on: 2026-11-06
  - id: t1-m-prohibited
    title: "About prohibited information (Meta Business Help Center)"
    url: https://www.facebook.com/business/help/361948878201809
    tier: T1
    accessed_on: 2026-11-10
  - id: t1-m-dsc
    title: "Understand data sharing restrictions based on data source categories (Meta Business Help Center)"
    url: https://www.facebook.com/business/help/511197658391698
    tier: T1
    accessed_on: 2026-11-10
  - id: t1-m-dsc-about
    title: "About data source categories in Meta Events Manager"
    url: https://www.facebook.com/business/help/1402913027039332
    tier: T1
    accessed_on: 2026-11-10
  - id: t1-m-core
    title: "About core setup (Meta Business Help Center)"
    url: https://www.facebook.com/business/help/124742407297678
    tier: T1
    accessed_on: 2026-11-10
---

> **How to use this file:** attach it to ChatGPT, Claude, Gemini or Copilot, replace every [PLACEHOLDER] with your details, and add any data or Deepstory evidence files the method needs.

**Best with:** A chat AI for the plan; your CRM admin or a developer for the connection. Attach a CRM export with stages and dates. Rule of thumb: remove names, emails, phone numbers, company names, free-text notes and any column that reveals health, treatment, debt or other sensitive details, and replace click IDs and lead IDs with yes or no columns. For value, keep only the amount, date and source.

## Quick start

1. Write down what "qualified" and "won" mean, and make sure your CRM (customer list tool) saves the date each lead reaches them.
2. Give each stage a money value (rule of thumb): what a new customer is worth, times the share of that stage that ends up buying.
3. For Google Ads, unless your business is in a sensitive category (step 7), turn on enhanced conversions (the setting that matches your CRM results to ad clicks using email or phone) and send each stage as its own conversion, counted once per lead. Add the new stages as Secondary and leave your current Primary action (usually the form fill) as it is, so bidding always has a Primary action. Only when you switch (step 8), make the stage you bid on Primary, set the others, including form fills, to Secondary, and take them out of any custom goal, because a custom goal bids on everything in it. Only the Primary stage’s value reaches bidding.
4. Google also needs the click ID (GCLID) saved on each lead, or a Google tag collecting email or phone on your form. If your account sits under a manager account (MCC), send one test event first and check it appears in Google Ads.
5. Send results every day. Google takes them up to 63 days after the click (90 with the click ID), Meta wants the stage within 28 days, LinkedIn within 30 days.
6. Meta’s qualified-lead goal is built for at least 200 instant-form leads a month. Below that, keep your current goal and track qualified leads in the CRM. Above that, select the earliest stage that happens within 28 days and converts 1% to 40% of leads.
7. Before the first upload, check consent and your privacy notice, and never send health, debt or other sensitive data. If your business is in one of those areas, send nothing until a privacy adviser has reviewed it, and judge campaigns on your own CRM numbers (rule of thumb).
8. Wait at least 4 weeks (rule of thumb) of steady daily uploads, and longer if leads usually take more than a month to reach that stage, before switching bidding to the deeper stage. When you switch, review your target cost per result, then check the numbers every week.

## Before you start

- You have not set up conversion tracking yet: the Google tag, GA4, the Meta Pixel, a consent banner, or hidden click-ID fields on your forms. Do that first. See: Set up conversion tracking with GA4, Consent Mode and Meta CAPI (https://deepstoryresearch.com/method/conversion-tracking-ga4-consent-capi)
- Your problem is the lead form itself: form type, qualifying questions or follow-up speed. See: Run lead form ads that bring real leads (https://deepstoryresearch.com/method/lead-form-ads-lead-quality)
- You have not agreed what a "qualified" lead is with sales. Define it first, or the platforms will learn the wrong thing. See: Build a lead qualification scorecard (https://deepstoryresearch.com/method/lead-qualification-scorecard)
- Your CRM has no stages, or does not record the date a lead changes stage. See: Set up a CRM and sales pipeline (https://deepstoryresearch.com/method/crm-pipeline-setup)
- Your leads are about health or medical matters, debt, a low credit rating or another negative financial situation, crime or criminal records, divorce or separation, religion, political affiliation, trade union membership, race or ethnicity, sexual behaviour or orientation, adult activities such as gambling, sexual dating or sexual entertainment, or children under 13. Google does not allow conversion data in these categories, and Meta’s terms also ban sharing any health, financial or consumer report information (rule of thumb: treat loan, mortgage and insurance leads as financial information until a privacy adviser says otherwise). Get privacy advice instead. See: Check data-privacy compliance gaps (https://deepstoryresearch.com/method/data-privacy-gap-check)
- You sell through an online checkout and the sale happens on your website; normal purchase tracking covers that. See: Set up conversion tracking with GA4, Consent Mode and Meta CAPI (https://deepstoryresearch.com/method/conversion-tracking-ga4-consent-capi)
- Most of your leads start on WhatsApp or a phone call. Those leads carry no Google click ID and no form, so there is little to match them to an ad unless the person also filled in a tagged form (rule of thumb). Track where those leads come from first. See: Track WhatsApp and phone-call leads from your ads (UAE and India) (https://deepstoryresearch.com/method/whatsapp-call-lead-tracking)

## Intake questions

Ask me these first:

1. **What exactly makes a lead "qualified" and "won", who marks it in the CRM, and is the date of each change saved?**
   Why: Each upload needs a clear stage name and the time it happened. Google rejects a conversion time before the click, and Meta discards events timed before the lead.
   If unknown, assume: Qualified = sales confirms need, budget and timing (for example a meeting or site visit booked); won = signed contract. Ask before planning any upload.
2. **For each platform, how many leads, qualified leads and customers came in each month over the last 3 months, and how many of the Meta leads came from instant forms rather than website forms? What share of leads start on a form, a phone call or WhatsApp?**
   Why: Meta’s CRM optimisation is built for at least 200 leads a month, and Meta’s payload specification says it supports only instant forms; LinkedIn wants five or more qualified leads within two weeks; Google needs steady daily uploads before a stage is used for bidding.
   If unknown, assume: Ask for at least lead and customer counts and label estimates as ASSUMPTION. Keep each platform bidding on leads until real counts exist. Rule of thumb: count each source separately from the CRM and say whether totals overlap; do not use GA4 key events or platform-reported leads as lead counts, since they may include clicks or duplicates.
3. **How many days pass from the ad click or lead to qualified, and to won?**
   Why: Google accepts outcomes up to 90 days after the click with the click ID (GCLID) and 63 days when matched on email or phone; Meta’s optimisation stage must happen within 28 days; LinkedIn uses qualified leads shared within 30 days.
   If unknown, assume: Assume won takes longer than 28 days and plan to bid on the qualified stage.
4. **What is a won customer worth on average, is that revenue or profit, first year or lifetime, and which bid strategy and target (Target CPA or Target ROAS) does each campaign use today?**
   Why: Values record what each stage is worth, and Target ROAS or Maximise conversion value need them. Bidding reads the value only of the stage it bids on, so a value on a Secondary stage is for reporting. A target set for form fills has to be reviewed when bidding moves to a deeper stage.
   If unknown, assume: Use first-year revenue averaged over the last 10 to 20 won deals, labelled ASSUMPTION. Ask for each campaign’s bid strategy and target before planning the switch. Rule of thumb: do not divide annual revenue by monthly leads or bookings, because that includes returning customers; use amounts from first deals or first visits only, and say how new customers were told apart.
5. **Which CRM and plan do you use, what does each lead record store (Google click ID (GCLID, gbraid or wbraid), email, phone, Meta lead ID, LinkedIn lead or click ID (li_fat_id)), and does a Google tag with enhanced conversions collect email or phone on your lead form?**
   Why: Each platform matches on different keys. Without them, uploads are accepted but not matched to ads. Google requires the GCLID if no tag collects email or phone on the form. A platform can only get back outcomes for leads the CRM holds, so also say whether LinkedIn Lead Gen Form and Meta instant-form leads reach the CRM automatically, by hand download, or not at all.
   If unknown, assume: Assume email and phone only, and no tag collecting them. Google needs either the GCLID or a tag that collects email or phone on the form, so confirm the tag or start saving the GCLID before planning uploads (see "Set up conversion tracking with GA4, Consent Mode and Meta CAPI", https://deepstoryresearch.com/method/conversion-tracking-ga4-consent-capi). Check whether instant-form leads arrive with their Meta lead ID. Rule of thumb: if lead-form leads are downloaded by hand, get them into the CRM first (or, for LinkedIn, use its CSV upload); do not plan a CRM sync for leads the CRM does not hold.
6. **Where are your leads based, and does each lead record show whether the person agreed to their data being shared with ad platforms?**
   Why: Google’s EU user consent policy covers the EEA, the UK and Switzerland, and Google says uploads without the consent field may not be attributable.
   If unknown, assume: Assume some leads are in the UK or EU and no consent is stored. Add a consent field before the first upload and ask your privacy adviser about the wording.
7. **Do your leads or services relate to health, debt or credit problems, other financial information (for example loans, mortgages or insurance), crime, divorce, religion, politics, trade unions, race or ethnicity, sexual behaviour or orientation, gambling or other adult activities, or children under 13?**
   Why: Google does not allow conversions in its listed sensitive categories for enhanced conversions, and Meta’s terms ban sharing health, financial, consumer report and other sensitive information. Meta may also restrict data sharing from data sources in certain categories, such as Health and wellness or Financial service.
   If unknown, assume: Ask. If yes, stop: no uploads to Google, Meta or LinkedIn, and do not turn on enhanced conversions, until a privacy adviser has reviewed it. Google’s customer data policy also covers enhanced conversions for web, so check Goals > Settings > Customer data use: if enhanced conversions is already on, raise it with your adviser now. Google’s page does not say how a click-ID-only import is treated; treat it as not allowed until your adviser confirms. Rule of thumb (safe path meanwhile): keep CRM outcomes internal, make lead source a required CRM field, and judge campaigns each month on qualified leads and won deals from the CRM, not on platform-reported leads.
8. **Who is admin on Google Ads, Meta Business and LinkedIn Campaign Manager, is the Google Ads account run under a manager account (MCC), and does anything already upload offline conversions (an old Google import, a developer script, Zapier)?**
   Why: Turning on enhanced conversions and connecting a CRM mean accepting data terms, and since 15 June 2026 Google Ads API uploads are blocked for any developer token that sent no request between January and June 2026. Google says offline conversions should be tracked at the same level (manager or client account) as your other conversions, and HubSpot says form and conversion events for accounts under an MCC cannot sync through Google’s enhanced conversions, so under an MCC, test one event before relying on that route.
   If unknown, assume: Assume nothing is connected, and that the account may sit under a manager account until the admin confirms it does not. The account admin accepts terms and connects tools; check for old API scripts before building anything.

## Decision rules

| If | Then | Threshold | Type | Source |
|---|---|---|---|---|
| You start sending CRM outcomes to Google Ads, or you still use the older offline conversion import. | Use enhanced conversions for leads, which Google recommends over offline conversion import (a "legacy feature"). Connect through Google Ads Data Manager (CRM connectors, SFTP or file), a partner such as HubSpot or Zapier, or the Data Manager API. Recommended setup: save the GCLID on every lead you can, and use a Google tag with enhanced conversions to collect email or phone on the form. Google says the GCLID is "Required if you are not implementing a tag to collect user-provided data", so email or phone alone is not enough when no tag collects them. If you have neither, fix that before planning uploads. Developers: since 15 June 2026 these uploads go through the Data Manager API and are blocked in the Google Ads API, except for developer tokens that already sent requests between January and June 2026 (as of November 2026). | - | Platform rule | [t1-g-ecl-upgrade], [t1-g-oci-faq], [t1-g-ec-settings], [t1-g-oci-about] |
| You choose which CRM stages to send to Google Ads. | Create a separate conversion action for each stage (for example "Qualified lead" and "Won contract") and set its goal to Qualified lead or Converted lead. Google says "Usually, you would only want to bid to one stage of the lead funnel", and this method recommends one: see the next rule. Optional: Google Ads’ Lead Journey Mapping lets you map these stages visually; Google says it does not directly change campaign performance in the short term and suggests enhanced conversions for leads or offline import to close tracking gaps, so keep the uploads (its help page did not call it a beta as of November 2026). Rule of thumb: do not send "lost" or "disqualified" as a conversion; retract a stage you sent by mistake. | - | Platform rule | [t1-g-oci-faq], [t1-g-qual-conv], [t1-g-ljm] |
| You decide which Google stage bidding learns from, and when. | Recommended setup: keep only the bidding stage as Primary; set the others, including any deeper stage you keep for reporting (often Won) and the website form-fill action (for example "Submit lead form"), to Secondary (observation only, shown in "All conversions"). A Primary action is used for bidding only when the goal it belongs to is used for bidding, so check that each campaign bids on the Qualified lead or Converted lead goal that holds it. Custom goals are the exception: an action in a custom goal is used for bidding whether it is set to Primary or Secondary, so Secondary does nothing there. Remove the form-fill action, and any stage you do not bid on, from any custom goal a campaign uses, or move the campaign to the standard goal that holds the Primary stage. Upload at least daily, or on a fixed regular schedule, for one to two conversion cycles (roughly, the usual time from ad click to that stage) before making a new stage primary. When replacing an old offline import action, swap after the longer of 1 to 2 conversion cycles or 4 weeks. After a big change in what bidding optimises for, Google says to give Smart Bidding 1 to 2 conversion cycles to adapt, and that you "may consider" changing your Target CPA or ROAS. | - | Platform rule | [t1-g-primary], [t1-g-oci-faq], [t1-g-ecl-upgrade] |
| The time from click to the stage you upload is long. | Google keeps the GCLID for 90 days and accepts outcomes matched on email or phone for 63 days. Set the action’s click-through conversion window to cover your cycle (up to 90 days for imports; the default is 30). If the won stage usually comes later than that, bid on an earlier stage that happens inside the window. | - | Platform rule | [t1-g-oci-faq], [t1-g-window] |
| You create an imported lead-stage conversion action in Google Ads. | Change Count from "Every" (the default for import actions) to "One", which counts one conversion per ad click and suits leads. Send a unique transaction (order) ID per lead and stage: Google keeps the first event with that ID and treats later ones as adjustments. | - | Platform rule | [t1-g-counting], [t1-g-dm-send] |
| You set values on your Google conversion actions. | Upload every conversion with a value and currency; Google’s FAQ says to "Upload all conversions and assign values to use Target CPA, Target ROAS or Max conversion value bid types", and that Smart Bidding optimises for whichever conversions are in the "Conversions" column. So in the recommended setup only the Primary stage’s value reaches bidding. A Secondary action is for observation only, so its value shows in "All conversions" and does not steer bids: if qualified is Primary and won is Secondary, bidding sees the qualified value and never the won value. Keep the won value for reporting and for working out the qualified value. If you want bidding to learn from won deals, make won the Primary stage instead, which needs it to fit the time limit and have the volume. A custom goal holding both stages would bid on both, which goes against bidding on one stage. With HubSpot’s native Google events, each stage has one fixed value. If you move to Target ROAS, Google suggests waiting 6 weeks for values to build and being comfortable with spend up to 2 times the average daily budget. | - | Platform rule | [t1-g-oci-faq], [t1-g-primary], [t1-hs-google] |
| A lead you sent as qualified turns out to be junk, or a deal’s value changes. | Retract or restate it with a conversion adjustment, using the order ID (or GCLID plus conversion time). Bidding reads adjustments made within 7 days of the conversion being recorded; adjustments overall work within 54 days (Google’s FAQ says 55). A retracted conversion cannot be adjusted again, and new conversions and adjustments go in separate files. If a manager account tracks your conversions, upload adjustments from the manager account. | - | Platform rule | [t1-g-adjust] |
| Your CRM is HubSpot and you use its native ad conversion events. | Only stage changes after you create the event are sent. For Google, the value is a fixed amount per stage (HubSpot removed "Use the Deal amount"), and a contact needs a GCLID or contact data to sync. That is what HubSpot needs to sync; Google’s own requirement still applies (the GCLID, unless a tag collects email or phone on the form). HubSpot recommends syncing all contacts who reach the stage. Its "Set the event as a primary action in Google" box uses the event for bidding, so tick it only for the stage you bid on, and only when you switch. For LinkedIn, HubSpot maps Marketing Qualified Lead and Sales Qualified Lead to QUALIFIED_LEAD and Customer to PURCHASE, and only events within the last 90 days are taken. For Meta, HubSpot’s lifecycle events work only for Conversion Leads campaigns. If the Google Ads account sits under a manager account (MCC), HubSpot says form submission and conversion events cannot sync through Google’s enhanced conversions, may show as sent in HubSpot without registering as conversions in Google Ads, and that connecting the ad account directly does not avoid this; see the manager-account rule below. HubSpot’s Meta sync also needs a Meta pixel in HubSpot: "Add pixel" adds it to every tracked page and starts sending page views at once, even with no conversion event, so sort out consent first. HubSpot limits ad conversion events by plan (Starter 5, Professional 50, Enterprise 100). LinkedIn’s help names only Professional and Enterprise for this connection while HubSpot also lists Starter, so check on your plan. HubSpot’s Google steps still say to choose "Google Ads API" as the method; Google says those method selections go away from June 2026, so if you do not see that menu, just turn on enhanced conversions. | - | Platform rule | [t1-hs-google], [t1-li-hubspot], [t1-hs-linkedin], [t1-hs-meta], [t1-g-ec-settings] |
| Your Google Ads account sits under a manager account (MCC) and you want to use HubSpot’s Google sync or Data Manager’s HubSpot connection. | Rule of thumb: HubSpot’s limit names "form submission and conversion events" and then "form data", so whether it also covers lifecycle-stage events is not confirmed: test with one event. Google’s Data Manager lists a HubSpot connection for offline conversion import and enhanced conversions for leads, but neither Google’s nor HubSpot’s page says how it behaves under an MCC, so that is not confirmed either: test with one event. After the consent check, send one event through the route. It passes only if it appears as a conversion in Google Ads, not just as sent in HubSpot. Do not plan bidding on a route until it passes. If neither passes, use a Data Manager file or SFTP upload, tracked at the same level (manager or client) as your other conversions, and test that too. | - | Heuristic (rule of thumb) | [t1-hs-google], [t1-g-dm-hubspot], [t1-g-oci-faq] |
| Your CRM is Salesforce and you send outcomes to Google Ads. | The legacy Salesforce integration ended on 31 May 2025; use the Data Manager Salesforce connection, importing from the Lead, Opportunity or Order object (sandboxes are not supported). Schedule it daily. If you use cross-account conversion tracking on a manager account, link Salesforce to the manager account. The first run looks back only 14 days, failed events are not retried automatically, and a new conversion action needs 4 to 6 hours before its first import. | - | Platform rule | [t1-g-sf], [t1-g-dm-sf] |
| You upload lead or customer data to Google (enhanced conversions for leads or offline imports). | Follow Google’s customer data policies: upload first-party data only; tell customers you share their information with third parties for ad measurement; get consent where the law requires it; follow the EU user consent policy; never upload data about children under 13 or conversions in sensitive categories (for example health, negative financial status, crime, divorce). The policy applies to "enhanced conversions for web, enhanced conversions for leads, store sales uploads, or Google-engaged audiences", and says "Conversions related to sensitive categories can’t be used for measurement in enhanced conversions or store sales (uploads)"; it does not mention a click-ID-only import, so ask your adviser before using one. If an agency or tool uploads for you, confirm in writing that it follows these policies. Turning on enhanced conversions means agreeing that the Google Ads Data Processing Terms apply. | - | Platform rule | [t1-g-cust-data], [t1-g-ec-settings] |
| Some leads are in the EEA, the UK or Switzerland. | Google’s EU user consent policy covers all three: you need legally valid consent to use personal data for ad personalisation, and must keep records of it. Store each lead’s choice in the CRM and send it with the upload (the Data Manager consent field has adUserData and adPersonalization). Google highly recommends filling the consent field because conversions without it may not be attributable. Rule of thumb: leave "Turn on conversion-based customer lists" unticked unless your privacy adviser confirms you may use the data to build ad audiences. | - | Platform rule | [t1-g-eu-ucp], [t1-g-ecl-upgrade], [t1-g-dm-send], [t1-g-eea-consent], [t1-g-ec-settings] |
| Some leads are outside the EEA, the UK and Switzerland (for example the UAE or India). | Google’s EU user consent policy does not name these places, but its customer data policies still apply: tell customers you share their information for ad measurement, get consent where the law requires it, and follow applicable data protection law. Do not read this as "no consent needed": check local law with "Check data-privacy compliance gaps" (https://deepstoryresearch.com/method/data-privacy-gap-check) and your privacy adviser. Not legal advice. | - | Platform rule | [t1-g-cust-data], [t1-g-eu-ucp] |
| You consider Meta’s qualified-lead optimisation (the Conversion Leads goal, "Maximize number of qualified leads"). | Meta’s CRM guide says it fits when you use lead ads with instant forms, get at least 200 leads a month, can upload at least daily, the stage you optimise for happens within 28 days of the lead, and that stage converts 1% to 40% of leads. Since April 2026 new campaigns cannot use the qualified leads goal without a Conversions API for CRM integration, and existing campaigns have been affected since August 2026 (Meta’s Help Center; Meta’s older developer getting-started page still says the integration is "not a requirement to begin running campaigns with the Conversion Leads performance goal", so follow the Help Center and check Ads Manager). Meta’s Help Center and its developer FAQ say the goal also works with website forms, but the developer overview and payload specification say the CRM optimisation supports instant forms only, and HubSpot’s Meta sync needs instant forms: check Ads Manager before building. Rule of thumb: below 200 leads a month, stay on "Maximize number of leads" and report cost per qualified lead from the CRM. | 200 leads a month; 28 days; 1% to 40% | Platform rule | [t1-m-cli], [t1-m-perf-goals], [t1-m-cli-payload], [t1-m-cli-faq], [t1-hs-meta], [t1-m-cli-start] |
| You build or configure the Meta Conversions API for CRM. | Use a CRM dataset (Events Manager > Connect data sources > CRM). Send every stage as it changes, including the first "lead" stage, with event_name set to your stage name, action_source "system_generated", and custom_data event_source "crm" and lead_event_source set to your CRM’s name. Include the Meta lead ID (15 to 17 digits) where you have it; otherwise send the click ID, hashed email or hashed phone. event_time must be no more than 7 days old and after the lead was created. Batches hold up to 1,000 events, and one error discards the whole batch. | - | Platform rule | [t1-m-cli-payload], [t1-m-cli-faq], [t1-m-cli-start] |
| Meta’s CRM integration is waiting for data, or you are setting up the sales funnel. | Meta checks for at least 7 days of data (not necessarily in a row), at least 60% of leads with matching events, and at least two stages (three recommended), with a lead campaign running at 200 leads a month. Then order your positive stages and choose the earliest stage to optimise for; Meta may optimise a different stage if it performs better. Do not switch the dataset or Pixel afterwards; that restarts training. Expect a 2 to 4 week learning phase after funnel analysis, and up to 1 to 2 months before full gains. | - | Platform rule | [t1-m-cli-verify], [t1-m-cli-faq], [t1-m-cli-funnel], [t1-m-cli-follow] |
| You send CRM data to Meta. | Under Meta’s Business Tools Terms (effective 3 November 2025) you must hash contact information as Meta specifies, never share data about children under 13 or health, financial, consumer report or other sensitive information, and not name events or conversions in a way that implies those categories. You also confirm you have a lawful basis and the rights to share the data. Meta may keep event data for up to two years. | - | Platform rule | [t1-m-bt-terms] |
| Your business is in health, finance or another sensitive area, or Meta has sent you a prohibited information or data restriction notice. | Meta’s "About prohibited information" page lists examples it does not allow, including "Diseases, medical conditions and injuries", "Medical procedures, treatments and testing", physical locations that identify a health condition or places of treatment, and "Debt status (including student loans, health/medical bills, mortgages, or other debts or liens)"; the names and criteria you set for events and conversions must not reflect, imply or be based on such information either. Meta may assign a data source, including an offline one, to a category such as Health and wellness or Financial service, and may then apply core setup (no custom parameters or anything in a URL after the domain), restrict certain mid and lower funnel standard events, or fully restrict all events; custom events are blocked until you review and confirm them. You cannot change a category Meta assigned, but you can ask Meta to review it. Check your data source categories and the dataset’s Diagnostics tab in Events Manager. If events are restricted, Meta suggests more upper-funnel events, or, under full restrictions, objectives that do not rely on Business Tools data (Awareness, Engagement or Traffic). Rule of thumb: do not build a Conversions API for CRM integration or send stage events until a privacy adviser has reviewed it. | - | Platform rule | [t1-m-prohibited], [t1-m-dsc], [t1-m-dsc-about], [t1-m-core] |
| You want LinkedIn to optimise for qualified leads. | Use the Lead generation objective with the "Qualified leads" optimisation goal (maximum delivery bidding only; single image, carousel, video, event and document ads). Send qualified leads to a conversion rule of type QUALIFIED_LEAD (from API version 202608, MARKETING_QUALIFIED_LEAD and SALES_QUALIFIED_LEAD rules are also used by Qualified leads campaigns) through the Conversions API, a partner, LinkedIn’s CRM Sync (connected in Business Manager), or a CSV upload. Use one source only for an ad set, because selecting events from both the Conversions API and CRM Sync can double count. LinkedIn’s goal page lists only the Conversions API and CRM Sync, while its CSV and objective pages allow uploads, so if you use CSV, confirm the conversion is offered in the ad set’s Qualified lead tracking section. These ad sets report only the qualified lead conversion type, so track won deals in the CRM. Cost per lead may rise; judge cost per qualified lead instead. HubSpot maps both Marketing Qualified Lead and Sales Qualified Lead to QUALIFIED_LEAD; rule of thumb: create a HubSpot event for only one of them, or the same lead may be sent twice. LinkedIn uses qualified leads shared within 30 days and recommends five or more within two weeks for its two-week learning phase. | 30 days; five qualified leads in two weeks | Platform rule | [t1-li-usecase], [t1-li-goal], [t1-li-leadgen-obj], [t1-li-csv], [t1-li-schema], [t1-li-hubspot] |
| You send CRM outcomes to LinkedIn by API or CSV. | Each event needs at least one identifier: SHA-256 hashed email, LinkedIn’s first-party click ID (li_fat_id), the Lead Gen Form response (lead), or first and last name, among others; send every one you have, since only matched events count. Conversion times must be within the past 90 days, and API batches hold up to 5,000 events. Check each conversion rule’s post-click window: the API default is 30 days and HubSpot-created rules default to 90 (change it in Campaign Manager); 180 or 365 days are allowed for QUALIFIED_LEAD, MARKETING_QUALIFIED_LEAD, SALES_QUALIFIED_LEAD, LEAD, PURCHASE and a few other types, so set it to cover the time from click to that stage. For CSV, copy the template exactly, use the ad account’s currency, upload daily or weekly, and allow up to 24 hours. | - | Platform rule | [t1-li-capi-doc], [t1-li-csv], [t1-li-schema], [t1-hs-linkedin] |
| You send CRM data to LinkedIn. | LinkedIn says you are responsible for getting any permissions needed before sharing customer data, and suggests involving your legal counsel early. Conversions API data is covered by LinkedIn’s Data Processing Agreement, emails are hashed with SHA-256, and event data is deleted after 180 days. | - | Platform rule | [t1-li-capi-help] |
| You set the value for each stage. | Value per stage = average value of a won customer x the share of that stage that becomes won (for example 24% of qualified leads win, so a qualified lead is worth 24% of a won deal). Use the same value on every platform, and say whether it is revenue or profit. | - | Heuristic (rule of thumb) | - |
| You pick the stage Google and LinkedIn work from. | Google: choose the deepest stage that happens inside Google’s time limit (63 or 90 days) and has enough volume after consent filtering and matching (about 30 a month). Otherwise bid on the stage above it and keep the deeper stage for reporting. LinkedIn: the goal optimises for qualified leads, so send them within 30 days and aim for about five matched qualified leads in two weeks. LinkedIn does not say what its 30 days run from, so count from the lead and send as soon as the lead qualifies. Meta works differently: see the next rule. | about 30 a month on Google (rule of thumb) | Heuristic (rule of thumb) | - |
| You pick the stage Meta optimises for. | Do not use a "deepest stage" rule on Meta. Meta says to "select the earliest lead stage to optimize for", that the selected stage "does not need to be the last stage of the funnel", and that "The system optimizes for all down-funnel stages as well". The stage must also pass Meta’s checks: it happens within 28 days of the lead and has a conversion rate between 1% and 40%, on at least 200 leads a month. So select the earliest stage that passes; a stage more than 40% of leads reach fails, so move to the next one. | 28 days; 1% to 40%; 200 leads a month | Platform rule | [t1-m-cli-funnel], [t1-m-cli], [t1-m-cli-faq] |
| Your volume is below the switch points on every platform (about 30 qualified leads a month on Google, 200 leads a month on Meta, about five matched qualified leads in two weeks on LinkedIn). | Rule of thumb: unless your business is in a sensitive category (then send nothing until a privacy adviser has reviewed it), keep sending each stage every day (as Secondary on Google), and each month compare campaigns on qualified leads and won deals from the CRM (and the Secondary columns in "All conversions" where they are attributed). Cut or fix campaigns that bring leads but no qualified leads, and fix the form itself with "Run lead form ads that bring real leads" (https://deepstoryresearch.com/method/lead-form-ads-lead-quality). Recount monthly; switch bidding only when the thresholds are met. | - | Heuristic (rule of thumb) | - |
| You wonder whether Journey Aware Bidding changes this setup. | Rule of thumb: Google’s Lead Journey Mapping page says clean conversion hygiene leaves your account "positioned to benefit from Journey Aware Bidding and future automated bidding guidance". Google’s announcement (as of November 2026) says Search campaigns with Target CPA or Maximize conversions "now learn from every goal", biddable or not, that the upgrade "is now available in beta for Search campaigns with Target CPA and Maximize conversions", and that "To enable it, all you have to do is give Google AI enough visibility into your lead journey by importing the necessary conversion actions". It names no setting to turn on. Google’s primary and secondary help page adds: "Primary conversion actions not used for optimization may be used to enhance predictions." Neither page says whether Secondary actions are read or how to tell that your account is in the beta, so this method does not change: import every stage as its own action, keep one Primary stage for bidding, treat the others as reporting, and do not set targets expecting beta gains. | - | Heuristic (rule of thumb) | [t1-g-ljm], [t1-g-jab], [t1-g-primary] |
| You are not sure you may share lead details with ad platforms at all (lawful basis, privacy notice wording, consent text). | This method does not decide that. Before the first upload, review your privacy notice with "Check your website’s privacy policy, cookies, terms and refund policy" (https://deepstoryresearch.com/method/website-privacy-terms) and your lawful basis with "Check data-privacy compliance gaps" (https://deepstoryresearch.com/method/data-privacy-gap-check), and confirm with your privacy adviser. Not legal advice. | - | Heuristic (rule of thumb) | - |

## Procedure

Copyable checklist:

- [ ] Define stages and values: Write one line each for lead, qualified, opportunity (if used) and won, who sets it and when. Value each stage: average won value x stage-to-won rate. Revenue or profit, stated.
- [ ] Check the lead records: With a CRM export (contact details removed, and identifiers replaced by yes or no columns), count leads by source, then count how many of each source’s leads hold that platform’s identifier (GCLID, gbraid or wbraid for Google; Meta lead ID for Meta instant forms; LinkedIn lead or li_fat_id for LinkedIn), plus email, phone, consent status and a date for each stage. A missing GCLID matters only on Google-sourced leads. Also check whether a Google tag with enhanced conversions collects email or phone on the form. If identifiers are missing, fix capture first with "Set up conversion tracking with GA4, Consent Mode and Meta CAPI" (https://deepstoryresearch.com/method/conversion-tracking-ga4-consent-capi).
- [ ] Check platform fit: Per platform: monthly volume per stage and days to each stage against the limits (Google 63 or 90 days, Meta 28 days and 200 leads a month, LinkedIn 30 days). Pick the stage per platform: on Google the deepest that fits, on Meta the earliest that passes its checks, on LinkedIn qualified leads.
- [ ] Plan Google Ads: The admin turns on enhanced conversions (this accepts the data terms). One imported action per stage, goal Qualified lead or Converted lead, Count "One", click-through window to cover the cycle, values, all Secondary at first. Confirm the GCLID or the Google tag first. Connect through Data Manager, HubSpot, Salesforce or a file, scheduled daily. If the account sits under a manager account (MCC), send one test event through that route after the consent check and see that it appears as a conversion in Google Ads before relying on it. Developers use the Data Manager API.
- [ ] Plan Meta: Only if the fit check passes: CRM dataset, partner or developer integration, every stage sent with the lead ID, daily or faster. Wait for verification and configure the funnel, removing events that indicate a negative lead and selecting the earliest stage that passes Meta’s checks. A published campaign’s goal cannot be changed, so duplicate it and change the goal on the copy. With HubSpot, create an event for each lifecycle stage, including Others. Otherwise report cost per qualified lead from the CRM.
- [ ] Plan LinkedIn: QUALIFIED_LEAD conversion rule through one source only (a partner such as HubSpot, the Conversions API, CRM Sync or CSV), linked to Lead generation ad sets; rule of thumb: switch the goal to Qualified leads once about five matched qualified leads arrive every two weeks (count them in Campaign Manager, not the CRM). LinkedIn recommends five or more within two weeks to speed up its two-week learning phase; its help pages state this as a recommendation, not a minimum.
- [ ] Check data and consent: No sensitive categories; first-party data only; privacy notice mentions sharing for ad measurement; consent stored and sent for EEA, UK and Swiss leads, and checked against local law for leads elsewhere; written terms with any agency or tool that uploads. Lawful basis checked with the privacy methods.
- [ ] Test, then switch: Send a few test rows and read Google’s offline data diagnostics, Meta’s Diagnostics tab and LinkedIn’s conversion status. After 1 to 2 conversion cycles of daily uploads, or 4 weeks if that is longer (rule of thumb; Google sets the 4-week floor only for replacing an old import action), make the chosen stage Primary on Google, set the form-fill action to Secondary, check each campaign bids on the goal that holds it and has no custom goal still containing the form-fill action, and review its Target CPA or ROAS. Reconcile weekly: CRM counts against what each platform received and matched.

## Output template

```
## Lead outcome loop: [BUSINESS]

### Stages and values
Stage | Definition | Who sets it | CRM date field | Stage-to-won rate | Value (revenue or profit)

### Lead record check (counts, no contact details)
Platform | Leads | With GCLID / gbraid / wbraid | With email or phone | With Meta lead ID | With LinkedIn lead or li_fat_id | Consent stored

### Platform fit
Platform | Leads a month | Qualified a month | Days to qualified | Days to won | Time limit | Bidding stage | Ready? (yes / not yet, why)

### Google Ads
Connection: [Data Manager / HubSpot / Salesforce / file / Data Manager API] | Enhanced conversions: [on, terms accepted by ..]
GCLID saved: [yes / no] | Google tag collecting email or phone: [yes / no] | Manager account (MCC): [yes / no; one-event test result] | Custom goals checked: [yes / no]
Action | Goal (Qualified / Converted lead) | Count | Window | Value | Primary or Secondary | Switch date

### Meta
Fit: [leads a month vs 200; stage within 28 days; rate 1% to 40%] | CRM dataset: [ ] | Integration: [partner / developer / not yet] | Stages sent: [ ] | Funnel target (earliest stage that passes): [ ]

### LinkedIn
Route (one source only): [HubSpot / partner / API / CRM Sync / CSV] | Conversion type: QUALIFIED_LEAD | Matched qualified leads every two weeks: [ ] | Goal: [Leads / Qualified leads]

### Data and consent
[ ] First-party data only | [ ] No sensitive categories | [ ] Privacy notice mentions ad measurement sharing | [ ] Consent stored and sent (EEA, UK, Switzerland) | [ ] Other countries: privacy notice and consent checked against local law ([COUNTRIES]) | [ ] Written terms with uploaders | [ ] Lawful basis reviewed ("Check data-privacy compliance gaps", https://deepstoryresearch.com/method/data-privacy-gap-check). Not legal advice.

### Schedule and checks
Upload: [daily] | Test rows sent: [date] | Switch bidding: [date] | Weekly reconciliation:
Week | Stage | CRM count | Sent | Matched or attributed | Notes
```

## Failure modes

| Mistake | Symptom | Fix |
|---|---|---|
| Uploading only "won" when contracts close months after the click. | Google rejects rows with "This click is too old", or few rows match. | Send an earlier stage (qualified) that happens within 63 or 90 days; keep won for reporting. |
| Leaving an imported lead action on Count "Every". | The same lead is counted several times when it is re-synced or changes stage twice. | Set Count to "One" and send a unique order ID per lead and stage. |
| Making every stage Primary. | One customer counts as a lead, a qualified lead and a sale; bidding overpays. | One Primary stage on Google; the rest Secondary. On Meta, select the earliest stage that passes its checks. |
| Switching bidding to the new stage on day one. | Spend and cost per lead swing for weeks. | Upload daily for 1 to 2 conversion cycles, or 4 weeks if that is longer (rule of thumb), then switch. |
| Switching the Primary action to qualified leads but keeping the Target CPA set for form fills. | Spend and impressions drop sharply, because a qualified lead costs much more than a form fill (GBP 200 against GBP 50 on Google in the worked example). | Google says only that you "may consider" changing the CPA or ROAS target, and to give bidding 1 to 2 conversion cycles to adapt. Rule of thumb: set Target CPA near the recent cost per qualified lead from the CRM (or Target ROAS from the stage values), then judge after 1 to 2 conversion cycles. |
| Wrong time zone or conversion time on uploads. | "Conversion date precedes click date" on Google, or Meta discards events timed before the lead. | Send the real stage-change time with its time zone; never backdate Meta events more than 7 days. |
| Sending only the final "Sale" stage to Meta, or switching the Meta dataset later. | Stuck at "Wait for 7 days of CRM events", or training starts again. | Send every stage from the first lead onwards to one CRM dataset and keep it. |
| Uploading EEA, UK or Swiss leads without consent signals. | Uploads accepted but conversions not attributed; possible policy breach. | Store consent at the form and send it in the consent field or HubSpot’s consent property. |
| Event or stage names that reveal sensitive details (for example "debt_advice_qualified"). | Breach of Meta’s Business Tools Terms and Google’s customer data policies. | Use neutral stage names, and do not upload at all for sensitive services without privacy advice. |
| Expecting HubSpot to send each deal’s real amount to Google. | Every won conversion shows the same value. | Set a representative fixed value per stage, or have a developer build a custom Data Manager upload. |
| Keeping an old Google Ads API upload script. | Uploads fail from 15 June 2026, unless the developer token sent requests between January and June 2026 and kept legacy access. | Move to Data Manager, a native connector or the Data Manager API, even if the old script still runs. |
| Relying on HubSpot’s Google sync on an account under a manager account (MCC) without testing it. | Events show as sent in HubSpot, but no conversions appear in Google Ads. | Test one event first. If it does not appear, try another route and test that too: Data Manager’s HubSpot connection under an MCC is not confirmed, so a file upload at the same level as your other conversions is the fallback. |
| Uploading email or phone with no GCLID and no Google tag collecting them on the form. | Rows may upload, but few or none are attributed to ads. | Add the tag or save the GCLID on the form, then check offline data diagnostics. |
| Setting the form-fill action to Secondary while it is still in a campaign’s custom goal. | Bidding keeps chasing form fills, and qualified leads do not improve. | Remove it from the custom goal, or move the campaign to the Qualified lead goal. |
| Selecting LinkedIn qualified-lead events from both the Conversions API and CRM Sync. | Reported qualified leads are inflated, and cost per qualified lead looks too good. | Use one source. CRM Sync conversions carry an auto-created label, so check all selected events match. |
| Judging a LinkedIn Qualified leads ad set on cost per lead. | Cost per lead rises, and the ad set gets switched off during learning. | Judge cost per qualified lead after the two-week learning phase, allowing for reporting delay. |

## Verification

- [ ] Each stage has a written definition, a date field in the CRM and a value with its formula.
- [ ] Google has exactly one Primary stage inside its time limit; Meta’s target is the earliest stage that happens within 28 days and converts 1% to 40% of leads; LinkedIn gets qualified leads within 30 days.
- [ ] Google imported actions show Count "One", the right goal, a window that covers the cycle, and the planned Primary or Secondary status.
- [ ] No custom goal a campaign uses holds the form-fill action or a stage you do not bid on.
- [ ] Leads carry the GCLID, or a Google tag collects email or phone on the form. Under a manager account (MCC), one test event has appeared as a conversion in Google Ads, not just as sent in HubSpot.
- [ ] Diagnostics show recent successful imports: Google offline data diagnostics, Meta Diagnostics tab and lead coverage, LinkedIn conversion status.
- [ ] A weekly table compares CRM counts per stage with the counts each platform received and matched.
- [ ] Consent is stored and sent for EEA, UK and Swiss leads, no sensitive categories are involved, and the lawful basis has been reviewed.

## Agent mode

If an AI agent is operating a browser or API on your behalf:

**May do without asking:**
- Draft stage definitions, values and the platform fit table.
- Design the upload column map using column names or fake sample rows.
- Read diagnostics, import histories or upload result files that the user exports and attaches.
- Calculate rates, values and cost per qualified lead from counts with contact details removed.

**Must stop before (the user decides and does these):**
- Uploading, syncing or importing any lead, CRM or customer data to Google, Meta or LinkedIn, by file, connector, Zapier or API.
- Turning on enhanced conversions or conversion-based customer lists, or accepting customer data terms, Business Tools Terms or any data processing terms.
- Creating, editing or removing conversion actions, conversion rules or datasets, or changing Primary or Secondary, counting, windows or values, which changes bidding and spend.
- Connecting, authorising or removing a CRM, Data Manager, HubSpot, Salesforce or partner integration; adding, installing or switching a Meta Pixel, dataset or other tag (HubSpot’s "Add pixel" adds it to every tracked page and starts sending page views at once; set tags up with "Set up conversion tracking with GA4, Consent Mode and Meta CAPI", https://deepstoryresearch.com/method/conversion-tracking-ga4-consent-capi); or publishing changes to website forms, consent fields or the privacy notice.
- Changing a campaign goal, bid strategy or budget, or publishing campaign changes.
- Retracting or restating conversions, which cannot be undone.
- Changing billing, or deleting anything.

**Setup advice:**
- Never paste real names, emails or phone numbers into the chat; share counts and column names.
- Give the agent a read-only user role; the account admin accepts terms and connects tools.
- Test with a handful of rows before a full sync, and keep the upload result files.

## Worked example

The figures below are illustrative. Never reuse them: use only the user’s own numbers and facts, and label anything they have not given as an ASSUMPTION.

**Scenario:** A UK commercial cleaning company (offices and warehouses) using HubSpot Marketing Hub Professional, with leads from a Google Ads quote form, LinkedIn Lead Gen Forms and Meta instant forms.

**Input:** Monthly: Google GBP 6,000 spend, 120 leads, 30 site surveys booked (qualified), 8 contracts won. LinkedIn GBP 3,000, 40 leads, 10 qualified, 2 won. Meta GBP 1,200, 40 leads, 10 qualified, 2 won. Average first-year contract GBP 14,400. Survey about 5 days after the lead; contract 30 to 45 days after. Leads in the UK and Ireland. HubSpot stores GCLID, email and phone; no consent property yet. A Google tag with enhanced conversions collects email and phone on the quote form. The Google Ads account is not under a manager account.

**Output excerpt:** Funnel (all platforms): 200 leads, 50 qualified (25%), 12 won (24% of qualified, 6% of leads). Values: won GBP 14,400; qualified 14,400 x 0.24 = GBP 3,456; lead 14,400 x 0.06 = GBP 864. Cost per lead on Google today: 6,000 / 120 = GBP 50. Cost per qualified lead: Google 6,000 / 30 = GBP 200, LinkedIn 3,000 / 10 = GBP 300, Meta 1,200 / 10 = GBP 120. Cost per won: Google GBP 750, LinkedIn GBP 1,500, Meta GBP 600 (only 2 won a month on Meta and LinkedIn: too few to judge). Google: the account is not under a manager account and a tag collects email and phone, so HubSpot’s Google route fits. HubSpot conversion events for Sales Qualified Lead (fixed value GBP 3,456) and Customer (GBP 14,400), both Secondary at first (leave HubSpot’s "Set the event as a primary action in Google" box unticked). Then, in Google Ads, open each new conversion action, check its goal (Qualified lead or Converted lead), and set Count to "One" (import actions default to "Every") and the click-through window to 90 days. If HubSpot syncs all contacts who reach each stage, as it recommends, about 62 rows a month go to Google (50 + 12), synced as stages change; about 38 of them (30 + 8) came from Google ads, so expect roughly that many to be attributed. Contracts land 30 to 45 days after the lead, inside the 63-day limit from the click for email matches. After 4 weeks of steady syncing (rule of thumb), and if about 30 qualified leads a month are still attributed in Google Ads after consent filtering (rule of thumb), make Qualified lead Primary. Only 30 a month come from Google before any filtering or matching, so expect fewer. Won stays Secondary, so its GBP 14,400 value shows in "All conversions" and does not steer bids; bidding sees the GBP 3,456 qualified value. The quote-form action moves to Secondary and comes out of any custom goal. Review the Target CPA: a GBP 50 target set for form fills is far below the GBP 200 cost per qualified lead (rule of thumb: start near GBP 200). Rule of thumb: if fewer than about 30 qualified leads a month are attributed, do not switch yet: keep the quote-form action Primary with its current Target CPA, keep both HubSpot events Secondary and syncing, report cost per qualified lead from HubSpot, and recount each month. LinkedIn: HubSpot maps Sales Qualified Lead to QUALIFIED_LEAD; 10 a month is about 4.6 every two weeks, just under LinkedIn’s five, and the survey happens well inside 30 days. Once the consent property is live, recount, because only contacts with consent are used. Rule of thumb: switch Lead Gen ad sets to the Qualified leads goal only if about five matched qualified leads still arrive every two weeks; otherwise stay on Leads and report cost per qualified lead from HubSpot. Meta: 40 leads a month is far below 200, so no Conversions API for CRM build yet; stay on "Maximize number of leads" and report the GBP 120 cost per qualified lead from HubSpot. Before the first sync: add a "consent to share with ad platforms" property to every form and map it in HubSpot, update the privacy notice to say leads are shared for ad measurement, and check the lawful basis with "Check data-privacy compliance gaps" (https://deepstoryresearch.com/method/data-privacy-gap-check) (UK leads fall under Google’s EU user consent policy).

## References

### Platform settings

| Platform | Path | Setting | Note | Source |
|---|---|---|---|---|
| Google Ads | Goals > Settings > Customer data use | Turn on enhanced conversions; Turn on conversion-based customer lists | Turning it on requires agreeing to the data terms. Web and leads are one on/off setting since June 2026. | [t1-g-ec-settings] |
| Google Ads | Goals > Conversions > Summary > + Create conversion action > Import > CRMs, files, or other data sources | Goal and action optimization: Qualified lead or Converted lead | Converted lead is the default when importing from Salesforce or a CRM. | [t1-g-qual-conv] |
| Google Ads | Goals > Conversions > Summary > conversion action > Edit settings > Count | One or Every | Import actions default to Every; One suits leads. | [t1-g-counting] |
| Google Ads | Goals > Conversions > Summary > conversion action > Edit settings > Click-through conversion window | 1 to 90 days, depending on the conversion source | Default 30 days; changes apply only to future conversions. | [t1-g-window] |
| Google Ads | Goals > Conversions > Summary > goal > Edit goal > Conversion action optimization | Primary or Secondary (observe only) | An action in a custom goal is used for bidding either way. | [t1-g-primary] |
| Google Ads | Goals > Conversions > Uploads > + > View templates | Conversions adjustments template (RETRACT or RESTATE) | Bidding reads adjustments within 7 days; overall within 54 days. | [t1-g-adjust] |
| Google Ads Data Manager | Conversion action > Data integration > Manage > Edit schedule / Edit mapping | Salesforce connection: Lead, Opportunity or Order object; daily schedule; value field mapping | First import looks back 14 days; failed events are not retried. | [t1-g-sf], [t1-g-dm-sf] |
| Meta Events Manager | Connect data sources > CRM > Connect | Create a new CRM dataset or convert an existing one | Meta suggests a new dataset; do not switch datasets after the integration is complete. | [t1-m-cli-start], [t1-m-crm-setup] |
| Meta Events Manager | CRM dataset > Overview > Configure sales funnel > Optimization target | Order positive stages; choose the earliest stage to optimise for | - | [t1-m-cli-funnel] |
| Meta Ads Manager | Leads campaign > Ad set > Conversions > Leads dropdown | Qualified leads (Maximize number of qualified leads) | Needs a Conversions API for CRM integration for new campaigns since April 2026. | [t1-m-crm-setup], [t1-m-perf-goals] |
| LinkedIn Campaign Manager | Measure > Conversion tracking > Create conversion > CSV conversion | Upload a CSV list against a conversion rule | Template format and ad account currency must match. | [t1-li-csv] |
| LinkedIn Campaign Manager | Lead generation objective > Ad set > Optimization goal | Qualified leads | Maximum delivery bidding only. Chosen by default when a Conversions API integration exists. | [t1-li-leadgen-obj] |
| HubSpot | Marketing > Ads > Create > Conversion event | Lifecycle stage change, Value, Consent to share data, Data sharing, Choose contacts to share, Set as primary action in Google | Google values are fixed per stage. The primary box uses the event for bidding, so tick it only for the stage you bid on. | [t1-hs-google] |

### Sources

| ID | Title | Tier | Accessed on | URL |
|---|---|---|---|---|
| t1-g-ecl-upgrade | Upgrade offline conversion import to enhanced conversion for leads | T1 | 2026-11-05 | https://support.google.com/google-ads/answer/14274408 |
| t1-g-ec-settings | Updates to your enhanced conversions settings | T1 | 2026-11-05 | https://support.google.com/google-ads/answer/16884284 |
| t1-g-oci-faq | Offline conversion imports FAQs | T1 | 2026-11-05 | https://support.google.com/google-ads/answer/10029210 |
| t1-g-qual-conv | About qualified leads and converted leads | T1 | 2026-11-05 | https://support.google.com/google-ads/answer/11459091 |
| t1-g-ljm | About Lead Journey Mapping in Google Ads | T1 | 2026-11-06 | https://support.google.com/google-ads/answer/17233846 |
| t1-g-jab | Journey-aware bidding (Accelerate with Google announcement) | T1 | 2026-11-10 | https://business.google.com/us/accelerate/announcements/journey-aware-bidding/ |
| t1-g-primary | About primary and secondary conversion actions | T1 | 2026-11-10 | https://support.google.com/google-ads/answer/11461796 |
| t1-g-counting | About conversion counting options | T1 | 2026-11-05 | https://support.google.com/google-ads/answer/3438531 |
| t1-g-window | About conversion windows | T1 | 2026-11-05 | https://support.google.com/google-ads/answer/3123169 |
| t1-g-adjust | How to adjust your conversions | T1 | 2026-11-05 | https://support.google.com/google-ads/answer/7686280 |
| t1-g-sf | How to set up a Salesforce integration | T1 | 2026-11-05 | https://support.google.com/google-ads/answer/13548778 |
| t1-g-dm-sf | Salesforce (Google Ads Data Manager) | T1 | 2026-11-05 | https://support.google.com/google-ads/answer/14006189 |
| t1-g-cust-data | Customer data policies | T1 | 2026-11-10 | https://support.google.com/adspolicy/answer/7475709 |
| t1-g-eu-ucp | EU user consent policy | T1 | 2026-11-05 | https://www.google.com/about/company/user-consent-policy/ |
| t1-g-eea-consent | Updates to consent mode for traffic in European Economic Area (EEA) | T1 | 2026-11-05 | https://support.google.com/google-ads/answer/13695607 |
| t1-g-dm-send | Send events: Google Ads offline conversions (Data Manager API) | T1 | 2026-11-05 | https://developers.google.com/data-manager/api/devguides/events/google-ads/offline/send-events |
| t1-m-cli | Conversions API for CRM integration | T1 | 2026-11-05 | https://developers.facebook.com/documentation/ads-commerce/conversions-api/conversion-leads-integration |
| t1-m-cli-start | 2: Getting started with the CRM integration | T1 | 2026-11-10 | https://developers.facebook.com/documentation/ads-commerce/conversions-api/conversion-leads-integration/crm-integration/2-getting-started-with-integration |
| t1-m-cli-verify | 4: Verify your data | T1 | 2026-11-05 | https://developers.facebook.com/documentation/ads-commerce/conversions-api/conversion-leads-integration/crm-integration/4-verify-your-data |
| t1-m-cli-funnel | 5: Configure your sales funnel | T1 | 2026-11-05 | https://developers.facebook.com/documentation/ads-commerce/conversions-api/conversion-leads-integration/crm-integration/5-configure-your-sales-funnel |
| t1-m-cli-follow | 6: Follow-up steps after CRM integration | T1 | 2026-11-05 | https://developers.facebook.com/documentation/ads-commerce/conversions-api/conversion-leads-integration/crm-integration/6-follow-up-steps |
| t1-m-cli-payload | Conversion Leads payload specification | T1 | 2026-11-05 | https://developers.facebook.com/documentation/ads-commerce/conversions-api/conversion-leads-integration/payload-specification |
| t1-m-cli-faq | Conversions API for CRM FAQ | T1 | 2026-11-05 | https://developers.facebook.com/documentation/ads-commerce/conversions-api/conversion-leads-integration/faq |
| t1-m-perf-goals | About performance goals for lead ads | T1 | 2026-11-05 | https://www.facebook.com/business/help/782657799338685 |
| t1-m-crm-setup | Set up your CRM for qualified leads | T1 | 2026-11-05 | https://www.facebook.com/business/help/279369167153556 |
| t1-m-bt-terms | Meta Business Tools Terms | T1 | 2026-11-05 | https://www.facebook.com/legal/businesstech |
| t1-li-capi-help | LinkedIn Conversions API | T1 | 2026-11-05 | https://www.linkedin.com/help/lms/answer/a1655394 |
| t1-li-csv | Manually upload a conversion data CSV file to Campaign Manager | T1 | 2026-11-05 | https://www.linkedin.com/help/lms/answer/a796520 |
| t1-li-leadgen-obj | Lead generation ad objective | T1 | 2026-11-05 | https://www.linkedin.com/help/lms/answer/a422440 |
| t1-li-hubspot | Set up HubSpot integration to send conversion data to Campaign Manager | T1 | 2026-11-05 | https://www.linkedin.com/help/lms/answer/a6888207 |
| t1-li-capi-doc | Conversions API (LinkedIn Marketing API) | T1 | 2026-11-05 | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/ads-reporting/conversions-api |
| t1-li-usecase | Conversions API use cases (LinkedIn Marketing API) | T1 | 2026-11-05 | https://learn.microsoft.com/en-us/linkedin/marketing/conversions/conversions-usecase |
| t1-li-schema | Conversions API schema (LinkedIn Marketing API) | T1 | 2026-11-05 | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/ads-reporting/conversions-api-schema |
| t1-hs-google | Create and sync ad conversion events with your Google Ads account (HubSpot) | T1 | 2026-11-05 | https://knowledge.hubspot.com/ads/create-and-sync-ad-conversion-events-with-your-google-ads-account |
| t1-hs-meta | Create and sync ad conversion events with your Meta Ads accounts using Meta’s Conversion API (HubSpot) | T1 | 2026-11-05 | https://knowledge.hubspot.com/ads/create-and-sync-ad-conversion-events-with-your-meta-ads-accounts-using-metas-conversion-api |
| t1-hs-linkedin | Create and sync ad conversion events with your LinkedIn Ads account (HubSpot) | T1 | 2026-11-05 | https://knowledge.hubspot.com/ads/create-and-sync-ad-conversion-events-with-your-linkedin-ads-account |
| t1-g-oci-about | About offline conversion imports | T1 | 2026-11-06 | https://support.google.com/google-ads/answer/2998031 |
| t1-g-dm-hubspot | HubSpot (Google Ads Data Manager) | T1 | 2026-11-06 | https://support.google.com/google-ads/answer/15293735 |
| t1-li-goal | Qualified leads optimization goal | T1 | 2026-11-06 | https://www.linkedin.com/help/lms/answer/a6553958 |
| t1-m-prohibited | About prohibited information (Meta Business Help Center) | T1 | 2026-11-10 | https://www.facebook.com/business/help/361948878201809 |
| t1-m-dsc | Understand data sharing restrictions based on data source categories (Meta Business Help Center) | T1 | 2026-11-10 | https://www.facebook.com/business/help/511197658391698 |
| t1-m-dsc-about | About data source categories in Meta Events Manager | T1 | 2026-11-10 | https://www.facebook.com/business/help/1402913027039332 |
| t1-m-core | About core setup (Meta Business Help Center) | T1 | 2026-11-10 | https://www.facebook.com/business/help/124742407297678 |

---
Deepstory methods are process guidance for AI tools. Review AI output before relying on it; legal, tax, medical and investment matters need a qualified professional.
