Attribution
Deciding which ad, email or search gets credit for a sale. Last-click gives it all to the final touch; data-driven splits it based on what actually moved people. Different models, different numbers, same sale.
49 terms, defined in plain language. Where one of the free tools checks a term on a live site, the entry links to it.
Deciding which ad, email or search gets credit for a sale. Last-click gives it all to the final touch; data-driven splits it based on what actually moved people. Different models, different numbers, same sale.
Groups of users defined by what they did: viewed a product, abandoned a cart, bought twice. GA4 audiences can be shared with Google Ads for remarketing.
GA4 can copy every raw event into Google BigQuery daily, for free. The GA4 interface shows summaries; BigQuery gives you the rows, so you can query anything with SQL.
In Universal Analytics, the share of visits that saw one page and left. GA4 flipped it: bounce rate is now simply the opposite of engagement rate.
Sending conversions to an ad platform from your server instead of the visitor's browser. Ad blockers and iOS privacy settings cannot stop it, so the platform sees more of your real sales.
Clicks divided by impressions. If 1,000 people saw the ad and 20 clicked, CTR is 2%. A measure of whether the ad is interesting, not whether it makes money.
The cookie banner and the logic behind it: it records what each visitor agreed to and tells your tags. Cookiebot, CookieYes and OneTrust are CMPs.
Google's way of letting tags react to the cookie banner. If a visitor declines, the tags still run but without cookies, and Google models the gaps. Required in Europe for Google Ads to work properly.
Everything in one GTM setup: the tags, triggers and variables for one site, with an ID like GTM-XXXXXX. We sell a pre-made one so you do not build it from scratch.
An action worth money to you that a visitor takes: a purchase, a form, a sign-up, a call. Ad platforms optimise toward whatever you tell them counts as a conversion, so the definition matters.
Conversions divided by visitors (or clicks). 1,000 visits and 25 orders is a 2.5% conversion rate. The number every landing-page test is trying to move.
Measurement that keeps working when cookies are blocked or declined: server-side events, enhanced conversions, consent-mode modelling, first-party identifiers.
Ad spend divided by conversions: what one customer (or lead) cost you to get. Only as accurate as the conversion count underneath it.
Keeping one session when a visitor moves between domains you own, such as shop.example.com to checkout.example.net. Without it the checkout looks like a brand-new visitor who came from your own site.
Your own fields in GA4 reports, built from event parameters or user properties: member tier, content category, A/B variant. You register them in GA4 after sending them.
A JavaScript list on the page where the site drops facts (order total, product name, user type) for GTM to read. Tags read from it instead of scraping the page, so tracking survives design changes.
The live screen in GA4 that shows events as they arrive from your own browser. Turn on debug mode (GTM preview does it for you), click around your site, watch the events land.
Making sure a sale sent twice (once by the browser pixel, once by the server) is counted once. Both copies carry the same event_id and the platform keeps one.
The share of GA4 sessions that lasted over 10 seconds, had a conversion, or viewed two or more pages. Higher is better.
A Google Ads feature that sends hashed customer details (email, phone) with each conversion so Google can match it to a signed-in user even when cookies fail. Recovers conversions that would otherwise go missing.
GA4 settings that track scrolls, outbound clicks, site search, video plays and file downloads with no extra code. On by default for new properties; worth checking rather than assuming.
In GA4, anything that happens: page_view, scroll, add_to_cart, purchase. Each event can carry parameters (value, currency, items). Some are collected automatically, some you have to send.
Extra detail attached to an event. A purchase event without transaction_id, value and currency is just a counter; with them it is revenue you can report on.
Cookies set by the site you are on. Browsers trust them more than third-party cookies, which is why server-side setups put the important cookies on your own domain.
Information your customers gave you directly: emails, orders, account details. Ad platforms match it to their users, which is what enhanced conversions and CAPI rely on.
The current Google Analytics. Everything is an event (a page view, a click, a purchase), it works across web and apps, and it replaced Universal Analytics in 2023.
The EU privacy law. For tracking it means: no analytics or ad cookies before the visitor says yes, a real way to say no, and a record of the choice.
Google's free tool for putting tracking code on a website without editing the site itself. You install one GTM snippet, then add tags (GA4, Meta, Google Ads) inside GTM and decide when each one fires.
An audience the ad platform builds to resemble your customers. You give it a seed list (buyers, pixel visitors); it finds people who look like them.
The ID of a GA4 web data stream, shaped like G-XXXXXXXXXX. Your tag sends data to it. Universal Analytics used UA-XXXXXX IDs, which no longer work.
A way to send events to GA4 with a plain HTTP request, no browser involved. Used for offline sales, refunds from a back office, or anything a server knows and the page does not.
Any attribution model that splits credit across several touchpoints instead of giving it all to one. Linear, time-decay, position-based and data-driven are all multi-touch.
A small script from an ad platform (Meta, TikTok, LinkedIn, Pinterest) that reports what visitors do back to that platform, so it can count conversions and build audiences.
GTM's test mode. It opens your site with a panel that shows which tags fired on each click and page, and what the data layer held at the time, before you publish anything.
Domains GA4 should never count as a traffic source: your payment provider, your own subdomains. Otherwise a sale via PayPal gets credited to paypal.com.
Showing ads to people who already visited your site or did something on it. Needs a pixel or GA4 audience to build the list.
Revenue from ads divided by what you spent on them. A ROAS of 4 means $4 back for every $1 in. Platforms report their own ROAS, each counting the same sale, so blended ROAS (all revenue over all spend) is the honest one.
A GTM container that runs on a server (usually Google Cloud) instead of in the browser. The page sends one request to your server, and the server forwards events to GA4, Meta and the rest.
Tracking that runs on a server you control rather than in the visitor's browser. Fewer lost events, faster pages, and you decide what each platform receives.
One visit. In GA4 it starts when someone arrives and ends after 30 minutes without activity. Cross-domain and referral problems show up as sessions that split in two.
A piece of code GTM runs to send data somewhere: a GA4 event, a Meta Pixel event, a Google Ads conversion. Each tag has one or more triggers.
How long each tracking script takes to download and run. Every pixel adds weight; a slow tag can delay the page and the events it was meant to send.
Cookies set by a domain other than the one you are visiting, typically an ad network. Safari and Firefox block them and Chrome limits them, which breaks old-style cross-site tracking.
The rule that tells a GTM tag when to run: on every page, on a click, when a form submits, when a custom event lands in the data layer. No matching trigger, no tag.
The old Google Analytics, built around sessions and page views. It stopped collecting data on 1 July 2023. Anything still sending to a UA- ID is sending to nowhere.
Facts about a person rather than an action, such as plan level or language, that stick to every event they send afterwards.
Tags on the end of a link (utm_source, utm_medium, utm_campaign, utm_term, utm_content) that tell analytics where a visitor came from. Redirects that drop them are a common reason attribution goes blank.
A named value GTM can read: a data layer field, a URL parameter, a cookie, the text of a clicked button. Tags and triggers use variables so you do not hard-code anything.
A draft area inside a GTM container. You make changes in a workspace, preview them, then publish. Several people can work in separate workspaces without stepping on each other.
Knowing the terms is one thing. Seeing which of them apply to your site is another. The free tools read the live page and answer in seconds.
Check your site