Quick Event can report the registration funnel of your event pages to your own analytics and advertising accounts. You enter IDs – no code, no pixel installation – and the platform sends the events on your behalf, only after the participant has consented.
What is sent where
Google Analytics 4, Google Ads and Meta receive events server-side through Quick Event's own tagging server. The browser only talks to the event page's domain, so ad blockers and Safari's tracking prevention do not interfere, and the Meta pixel is not loaded in the browser at all. Microsoft Ads (UET), a Google Tag Manager container and Matomo are loaded in the browser after consent.
Values are the ticket cart of your event – Quick Event's fees are never included.
Events and parameters
All events carry an event_id for deduplication. GA4 receives them under these names; Meta receives ViewContent, InitiateCheckout, AddToCart, Purchase and CompleteRegistration; a GTM container receives them as data layer events of the same name.
| Event | When | Parameters |
|---|---|---|
view_event | Event page viewed (once per visit) | event_id |
begin_registration | Registration started | event_id |
registration_step | Participant form shown | step (participant number), event_id |
begin_checkout | Checkout started (paid events) | value (cart total), currency, items[] with item_id (ticket type), item_name, price, quantity, event_id |
purchase | Payment confirmed | transaction_id (booking ID), value, currency, items[], event_id (= transaction_id) |
registration_completed | Free registration completed | transaction_id (booking ID), event_id |
Mark purchase and registration_completed as key events in GA4 to use them for Google Ads bidding.
Platform notes
- GA4: events appear in DebugView within seconds; add the event page domain as a data stream.
- Google Ads: create a conversion action of type purchase and enter its label, or import the GA4 key events.
- Meta: use the same Pixel ID for the token; test with a test event code in Events Manager. The booking ID is sent as
event_id, so a pixel you run yourself in a GTM container is deduplicated. - Microsoft Ads: UET is loaded in the browser; Microsoft's server-side API is still in pilot.
- Matomo: only the host name is configurable;
matomo.jsis loaded from there without cookies.
Setup
- Open Event → Tracking in the studio.
- Enter the IDs you have: GA4 Measurement ID (
G-…), Google Ads conversion ID (AW-…) and purchase label, Meta Pixel ID plus a Conversions API access token (Events Manager → Settings → Conversions API), UET tag ID, GTM container ID (GTM-…) or Matomo host and site ID. - Each field saves when you leave it. Invalid IDs are rejected and shown.
- Configure the domain your event runs on in each platform (your custom domain, or
quick-event.com).
The Meta token is stored encrypted and never displayed again. Google Ads conversions can alternatively be imported from GA4 – then the label field stays empty.
Consent
Nothing fires before the participant accepts marketing cookies in the consent dialog (Matomo: analytics cookies). Participants who decline are not tracked at all – expect a gap between bookings and measured conversions; that gap is real and legally required. You are the data controller for the services you connect; Quick Event forwards the events as your processor and does not use them itself.