Conversion Tracking for GA4, Google Ads & Meta
Registrations and ticket purchases land in your own analytics accounts. Server-side, ad-blocker-proof and only after cookie consent.
10 use cases to tick off
Everything this area covers. Missing something? Ask us.
- ✓Server-side relay for GA4, Google Ads and Meta – ad blockers do not see it
- ✓Six funnel events with cart value, ticket types and booking ID
- ✓Fires only after the participant accepts marketing cookies
- ✓Measure the registration funnel
- ✓Your own analytics account
- ✓Measured first-party through your own domain
- ✓Registration steps passed to the GTM or Matomo on your own website
- ✓No cookie banner unless you set up tracking yourself
- ✓Fonts and map from our own servers, videos only after a click
- ✓On request: free events without any provider that has a US parent company
Registration embedded on your website
Where people book decides how they are measured. Both ways can run side by side without counting a booking twice.
Embedded on your website: your own tags
The embed code passes every registration step to your page. If Google Tag Manager is installed there, the events land in its dataLayer automatically, and Matomo receives them as events. Connect GA4, Google Ads and the Meta pixel to them – under your own cookie banner and with the click IDs of your ads, which arrive on your page and not in the embedded form.
On the Quick Event booking page: server-side
Enter your IDs under Event → Tracking, and GA4, Google Ads and Meta receive the events through our tagging server. This covers everyone who books directly on the booking page. It does not apply inside the embedded form: browsers do not store cookie consent there, and without consent nothing is sent.
Which tracking events are sent?
The code passes these events to Google Tag Manager (dataLayer) and Matomo if they are installed on your page. Otherwise listen for window message events with type "qe:track". No personal data is sent.
| Event | When | Data |
|---|---|---|
view_event | The registration is shown | — |
begin_registration | Registration started | — |
registration_step | Each participant form step | step |
begin_checkout | Before payment | value, currency |
purchase | Paid booking completed | value, currency, transaction_id |
registration_completed | Free registration completed | transaction_id |
step counts the participant forms (1, 2, …), value is the basket total in currency, transaction_id is the booking ID.
dataLayer: { event, step, ecommerce: { transaction_id, value, currency } } · Matomo: trackEvent("Registration", event, step, value), on purchase also trackEcommerceOrder(transaction_id, value)
Using Google Tag Manager? Our template connects GA4, Google Ads and the Meta pixel to these events. In GTM, open Admin → Import container, choose the file and select Merge and Rename conflicting. Then enter your IDs in the variables starting with “QE –” and delete the tags you do not need. The Meta tags only fire once ad_storage consent is granted.
Download Google Tag Manager template (JSON)
No Google Tag Manager? Listen for the messages yourself – the origin is the address of your registration:
window.addEventListener('message', (e) => {
if (e.origin !== 'https://your-event.quick-event.com') return;
if (e.data?.type !== 'qe:track') return;
// e.data.event, e.data.step, e.data.value, e.data.currency, e.data.transaction_id
});You will find the embed code in the studio under Registration → Settings.
Common questions
Values are the amounts the participant paid, as shown in the cart, in the event's currency.
Yes: open your event page, accept marketing cookies and walk through the registration up to the summary. GA4 DebugView and Meta's test events show the funnel live; only purchase needs a real (or test-mode) payment.
Events are only sent for participants who accepted marketing cookies. The difference between bookings and measured conversions is the share that declined – typically 20–40 %.
Not on the event page: enter your IDs under Event → Tracking in the studio. GA4, Google Ads and Meta are relayed through our tagging server; Microsoft Ads (UET) is loaded in the browser after consent. If you embed the registration on your own website, connect your tags there instead: the embed code passes every registration step to Google Tag Manager or Matomo on your page.
More areas in Event basics
Your First Event in 30 Seconds
The AI generates the event page, registration form, email templates and ticket categories in one step. No setup, no credit card, no technical knowledge.
12 use cases ›Events, Team & Live Dashboard
From creation to watching check-ins on event day: one Studio workspace with team roles, live dashboard and export.
14 use cases ›Multilingual Events – Event Page, Registration & Emails in Several Languages
One event, several languages: event page, registration and emails – drafted by AI, checked by you, shown in each guest’s own language.
13 use cases ›