Conversion tracking glossary
The terms that come up when you fix tracking for clients, defined plainly and checked against Google's and Meta's own documentation.
A
- action_source (Meta Conversions API)
- A required Conversions API field that tells Meta where a conversion happened, such as
website,phone_call,physical_storeorsystem_generated. - Attribution model (data-driven attribution)
- The rule Google Ads uses to split credit for a conversion across the ad interactions before it; only data-driven and last click are still supported.
C
- Consent Mode v2 (ad_user_data, ad_personalization)
- Google's API for passing a visitor's consent choices to Google tags, with v2 adding
ad_user_dataandad_personalizationalongsidead_storageandanalytics_storage. - Conversion action (Google Ads)
- A specific customer activity you tell Google Ads to count, such as a purchase, form lead or call, each with its own source, value, counting and attribution settings.
- Conversion value rules
- Google Ads rules that adjust a conversion's value by audience, location or device, changing both reported value and Smart Bidding without touching the tags.
- Conversion window
- The period after an ad click or view during which Google Ads will credit a conversion to that interaction; conversions after it closes are not recorded.
- Cross-domain measurement
- A GA4 setting that keeps one visitor as one user and one session when they move between your own domains, by passing IDs in a
_glURL parameter.
D
- Data layer (dataLayer)
- A JavaScript array that the site pushes events and values into so Google Tag Manager and gtag.js can read them, instead of scraping the page.
E
- Enhanced conversions
- A Google Ads feature that supplements conversion tags with SHA256-hashed first-party data, such as email or phone, to match conversions to signed-in Google accounts.
- Enhanced conversions for leads
- Google's upgraded offline conversion import: hashed email or phone captured at the form is later uploaded with the closed sale, so CRM outcomes are credited to the ad.
- Event Match Quality (EMQ)
- Meta's score out of 10 for how well the customer information sent with your Conversions API web events can be matched to Meta accounts.
- event_id and deduplication
- Meta drops a duplicate when a Pixel event and a Conversions API event share the same event name and event ID and arrive within 48 hours of each other.
F
- fbp and fbc
- Meta's first-party browser ID (
_fbp) and click ID (_fbc) cookies; passing both to the Conversions API, unhashed, helps match server events to ad clicks. - First-party data
- Customer information shared directly with a business by the customer, such as the email on a lead form or a purchase record in the CRM.
G
- GA4 measurement ID vs Google tag ID
- The
G-measurement ID identifies a GA4 web data stream; a Google tag ID is whatever ID loads a Google tag, which may beG-,AW-orGT-. - GBRAID and WBRAID
- Google Ads click parameters for iOS traffic covered by Apple's ATT rules:
wbraidfor app-to-web clicks,gbraidfor web-to-app clicks. - GCLID (Google Click Identifier)
- A unique ID that Google Ads auto-tagging adds to ad click URLs as
gclid, used to tie website and offline conversions back to the click.
K
- Key event (GA4)
- An event you mark in GA4 as important to the business, such as
generate_lead; GA4 now reserves the word conversion for what is used in Google Ads.
M
- Meta Conversions API (CAPI)
- Meta's server-to-server connection for sending web, app, offline and messaging events from your server or CRM directly to a Meta dataset.
- Meta Pixel
- A JavaScript snippet on your website that records visits and actions such as leads and purchases and sends them to Meta for measurement and ad optimization.
O
- Offline conversion import
- Uploading sales or qualified leads that happen off the website, such as by phone or in a CRM, to Google Ads so they are credited to the ad click.
P
- Primary vs secondary conversions
- Primary conversion actions appear in the Conversions column and drive bidding; secondary actions are for observation only and appear in All conversions.
S
- Server-side tagging (sGTM)
- Running a Google Tag Manager server container on infrastructure you control, so the browser sends data to your server and your server forwards it to vendors.
U
- UTM parameters
- Query parameters such as
utm_source,utm_mediumandutm_campaignadded to links so analytics tools can tell where a visit came from.
Got an account that doesn't add up?
Send us one account. We review it for free and send a short video of what's working and what isn't.