New format
Sales funnel via GTM: events and checkout drop-offs
A sales funnel in analytics isn’t a “magic GTM button” — it’s an agreed chain of purchase steps and events that show where people drop off.
Below: why the funnel matters, how to choose steps, how to send events to GA4 via GTM, and how to read drop-offs. Basic GTM (container, tags, Preview) is a separate article; here the focus is checkout. We don’t copy Universal Analytics screenshots or hard “virtual page” recipes from old guides.
Why tag the funnel
Without steps you see visits and occasional purchases, but not where the path breaks: product page, cart, shipping, payment, or contact form.
The funnel answers practical questions: how many reached the cart, where the biggest drop is, whether shipping and button fixes helped. It’s a base for UX and offer hypotheses — not a substitute for marketing strategy.
Typical jobs:
- track interest in catalog and product pages
- see add_to_cart and begin_checkout share
- catch exits before payment
- link drop-off to a specific page or error
- check the effect of A/B tests and releases
Path steps: from catalog to order
First describe your site’s real checkout — not an “ideal” textbook flow. A one-page landing has fewer steps; a store with variants and shipping has more.
Common frame: category or product view → add to cart → cart → checkout (contacts, shipping, payment) → success page. Keep event names close to GA4 ecommerce recommendations so reports and ad pixels align.
Example chain:
- view_item / product view
- add_to_cart
- view_cart
- begin_checkout
- add_shipping_info / add_payment_info (if present)
- purchase / generate_lead on thank-you page
Events via GTM instead of UA virtual pages
In Universal Analytics, people often faked steps with virtual pageviews. In GA4 it’s cleaner to send events with parameters (item_id, value, currency) and build the funnel from them.
In GTM: trigger on click/submit/dataLayer.push → GA4 Event tag (or Google tag) → Preview → publish. If the CMS already pushes ecommerce into the dataLayer — reuse those fields; don’t invent a second layer of “fake URLs.”
Container minimum:
- GA4 / Google tag config without a theme duplicate
- triggers on key steps
- stable event names across releases
- check in Preview and DebugView
- cookie consent accounted for in tag conditions
How to read the funnel in reports
In GA4 you usually build the funnel in Explorations (Funnel exploration) or watch ecommerce reports if the recommended scheme is in place. In Metrika — composite goals and step reports.
Dashboard UI changes: what matters is the meaning (“event sequence,” “step drop-off”), not a 2019 account screenshot. Compare periods before and after fixes and segments (mobile vs. desktop, traffic source).
What to watch first:
- share reaching each step
- the step with the biggest drop
- device differences
- payment or form validation errors
- time on step (if available)
What to do with bottlenecks
Drop-off on shipping and payment often needs transparent pricing, timelines, and working payment methods — not “one more pixel.” Drop-off on contact fields — form length and trust (details, policy, phone).
Catch broken buttons and redirects separately: an event that didn’t fire doesn’t mean the user “didn’t want to buy.” Match DebugView with a real session.
Working hypotheses:
- simplify checkout and cut extra exits
- show shipping and payment earlier
- fix broken buttons and validation
- speed up the mobile cart
- don’t treat retargeting as a substitute for decent UX
What to remember
A funnel narrows at each step — that’s normal. The job is to find abnormal drop-offs and test hypotheses, not “flatten the chart at any cost.”
GTM is event transport. Meaning comes from an agreed step map, clean names, and the habit of reading the report after every checkout release.
Short takeaway:
- describe the site’s real steps
- send GA4 events via GTM
- don’t duplicate counters
- read drop-offs and fix UX
- don’t copy UA-era pageview guides
FAQ
Does GTM build the funnel by itself?
No. GTM delivers tags and events. You view the funnel in GA4 (Explorations / Funnel) or in Metrika via goals — after correct tagging.
Do I still need virtual pages like in UA?
In GA4, rely on events (view_item, add_to_cart, begin_checkout, purchase, and your own). Virtual pageview is a UA legacy — not a required path.
Is a thank-you URL enough?
For a rough goal — sometimes. For a step funnel you need events on intermediate actions, or you only see “reached / didn’t.”
Can I duplicate the tag in the theme and in GTM?
No — you’ll get double hits. One delivery channel: either the template or GTM.
Does this replace a marketing automation funnel?
No. An automation funnel is a touch sequence (ads, bot, email). Here — measuring the path on the site.
Purchases are rare — and you only see visits, not where checkout breaks?
We’ll map real checkout steps, ship GA4 events via one GTM container, and read Funnel drop-offs before more pixels.
Discuss the task
