Skip to content

Google Ads — Frequently Asked Questions

Does CustomerLabs support Google Ads conversion tracking?

Section titled “Does CustomerLabs support Google Ads conversion tracking?”

Yes. CustomerLabs sends conversion events to Google Ads via the Google Ads API (server-side). You create a conversion action in Google Ads, map it to a CustomerLabs event (e.g., cl_purchase), and CustomerLabs forwards matching events as conversions.

See the Google Ads destination documentation for the full setup.

Why do my conversions appear as “Offline” in Google Ads?

Section titled “Why do my conversions appear as “Offline” in Google Ads?”

This is expected. CustomerLabs forwards conversions via the Google Ads API rather than through a browser-side tag, so Google classifies them as offline or server-side conversions. This is the correct and intended behaviour.

Should I set my conversion action to Primary or Secondary?

Section titled “Should I set my conversion action to Primary or Secondary?”

Set the conversion action to Secondary while validating. Switch it to Primary once you have confirmed that conversions are being received correctly in Google Ads.

What counting option should I use — “Every” or “One”?

Section titled “What counting option should I use — “Every” or “One”?”
  • Use Every for purchase events — counts each transaction.
  • Use One for lead events — counts only the first conversion per click.

GCLID (Google Click ID) is a parameter appended to URLs when a user clicks a Google Ad. CustomerLabs captures it automatically and includes it in conversion payloads to improve attribution accuracy. If GCLID is not present, Google falls back to enhanced conversion parameters (hashed email or phone).


Enhanced Conversions supplement standard conversion data by sending hashed customer identifiers (email, phone) alongside the conversion event. This improves conversion matching rates, particularly for users who don’t complete a purchase in the same session or on the same device.

Enable it in two places:

  1. Google Ads: Navigate to Goals → Settings → Customer data terms, accept the terms, and enable Enhanced Conversions.
  2. CustomerLabs: In the Google Ads destination, open Advanced Settings and enable the Enhanced Conversions toggle.

CustomerLabs automatically maps and hashes email and phone data before transmission.


Section titled “Does CustomerLabs support Google Consent Mode V2?”

Yes. CustomerLabs supports Consent Mode V2 for EU compliance. You can configure default consent values for ad_storage, ad_user_data, and ad_personalization, and update consent status dynamically using _cl.trackConsent() when a user interacts with your consent banner.

See the Google Ads destination documentation for implementation details.


  1. Create an audience in CustomerLabs and open it.
  2. Add the required fields in the Schema tab.
  3. Go to the List Sync tab, locate Google Ads, and click Map Schema.
  4. Select or create a Google Ads customer list.
  5. Map CustomerLabs fields to the Google Ads schema.
  6. Save, enable the toggle, and click Instant Sync.

See the Google Ads audience sync documentation for the full steps.

What audience types does Google Ads support for audience sync?

Section titled “What audience types does Google Ads support for audience sync?”
TypeDescription
Contact InfoEmail, phone, name — matched against Google account data
CRM IDCustomer IDs from your CRM
Mobile Advertising IDIDFA (iOS) or GAID (Android)

How long does it take for a synced audience to appear in Google Ads?

Section titled “How long does it take for a synced audience to appear in Google Ads?”

Allow up to 10–15 minutes after running Instant Sync for the audience to appear in Google Ads.

I see “Error Fetching Data” in the audience sync — how do I fix it?

Section titled “I see “Error Fetching Data” in the audience sync — how do I fix it?”

This typically means the Google authentication has expired. Navigate to Destinations → Google Ads → Configuration Settings and re-authenticate your Google account.

What identifiers are used for audience matching in Google Ads?

Section titled “What identifiers are used for audience matching in Google Ads?”

Email is the primary matching identifier. Phone number and customer IDs can be used as supplementary identifiers. Including the lead_id as an external ID when importing Google Ads leads improves match rates when syncing those leads back as an audience.


Can I import leads from Google Ads lead forms into CustomerLabs?

Section titled “Can I import leads from Google Ads lead forms into CustomerLabs?”

Yes. CustomerLabs supports Google Ads lead form imports via a webhook source. You create a source URL in CustomerLabs and configure it as a webhook endpoint in your Google Ads lead form asset. Incoming lead data is processed through a CustomerLabs workflow where you map identity fields and user traits.

See the Google Ads lead form source documentation for setup instructions.

How long before the workflow starts receiving Google Ads lead data?

Section titled “How long before the workflow starts receiving Google Ads lead data?”

Wait 30–40 minutes after creating and activating the workflow before testing with live lead submissions.