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.
6 use cases to tick off
Everything this area covers. Missing something? Ask us.
- ✓Server-side forwarding to GA4, Google Ads and Meta, invisible to ad blockers
- ✓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
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 %.
No. Enter your IDs under Event → Tracking in the studio. GA4, Google Ads and Meta are relayed through our tagging server; a Google Tag Manager container or Matomo is loaded in the browser after consent.
Yes. Enter the container ID; all six funnel events are pushed into the data layer with their parameters, so you can add any tag (TikTok, Pinterest, LinkedIn, …) yourself.
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.
12 use cases ›Your Own Domain, Without Our Branding
Event pages under your domain, automatic SSL, your own sender address. No Quick Event branding visible to participants.
7 use cases ›