Marketing Tracking

Add tracking pixels and analytics to your public event pages so ad platforms (e.g. Meta, Google) can attribute traffic and measure a full funnel: page view → add to cart → checkout → purchase.

This is separate from UTM Short Links, which record campaign parameters on links. Use both: UTMs for “which link they clicked,” marketing tracking for “what they did on Quicket.”

Where to find it

• Location: Event dashboard → Marketing Tracking (under Marketing & sales).

---

How it works (end to end)

1. You create active trackers for an event (type + code). They are stored on that event only.
2. When someone opens your event on Quicket’s public site (/events/your-event-slug), the storefront loads event details from the API. Active trackers are included in that payload.
3. The browser injects your trackers (after Quicket’s own analytics base is ready), then keeps your Meta Pixel ID(s) and GA4 measurement ID(s) in memory for that visit.
4. As the buyer moves through add to cart → cart → checkout → confirmation, Quicket fires standard e‑commerce events to your Meta pixel(s) and GA4 property/properties—so you can build custom conversions and audiences in Ads Manager and GA4.

flowchart TB
  subgraph org [Organizer]
    Dash[Marketing Tracking]
  end
  subgraph api [Quicket]
    Store[Public event API]
  end
  subgraph buyer [Buyer browser]
    EP[Event page]
    ATC[Add to cart]
    Cart[Cart]
    Pay[Payment]
    Conf[Confirmation]
  end
  subgraph ads [Your platforms]
    Meta[Meta Pixel]
    GA4[Google Analytics 4]
  end
  Dash --> Store
  Store --> EP
  EP --> Meta
  EP --> GA4
  EP --> ATC
  ATC --> Meta
  ATC --> GA4
  Cart --> Meta
  Cart --> GA4
  Conf --> Meta
  Conf --> GA4

Where events run

Area	Organizer trackers applied?	Funnel events (Meta / GA4)
Public event page (/events/{slug}) and same-site checkout	Yes, when the buyer has loaded the event page in this browser session	As described below
Embedded widget	Not loaded via this flow	Do not rely on organizer Marketing Tracking inside the embed for funnel duplication

---

Tracker types

Types in the dashboard map to how the storefront runs them:

Type in Quicket	Use for	What to put in Tracking code
Analytics	Google Analytics 4	Your GA4 Measurement ID (format G-XXXXXXXXXX). The site calls gtag('config', …) with page views enabled.
Pixel	Meta (Facebook) Pixel	Your Pixel ID (numeric string). The site runs fbq('init', …) and a PageView, then sends funnel events with trackSingle so each pixel only receives its own data.
Script	Custom snippets	Full script tag or raw JavaScript from a trusted vendor. Injected into the page on the event URL only (same scope as above). Automatic funnel events are not duplicated into arbitrary scripts—only Analytics and Pixel types receive the standard add_to_cart, begin_checkout, and purchase signals described below.

Paste only code from sources you trust.

---

Automatic funnel events (Meta & GA4)

These fire on Quicket’s main storefront when the buyer has already opened the event page in the same tab/session (so your IDs are registered). Names align with what Meta and GA4 expect for ads and conversion modeling.

Buyer action	Meta Pixel (standard event)	GA4 (recommended event)
Opens the event page	PageView (after init)	page_view (via gtag config)
Adds tickets, seated seats, or addons to cart (not registration-only flows)	AddToCart	add_to_cart
Continues from Cart to checkout / payment	InitiateCheckout	begin_checkout
Payment succeeds and confirmation loads	Purchase (includes transaction_id when available)	purchase

Payload details (high level):

• Currency is sent in ISO 4217 form (e.g. BDT, THB, USD), aligned with the event/cart currency Quicket uses.
• Items include stable IDs (category id, addon id, or line id), names, quantities, and unit prices where the API provides them.
• Purchase uses your order reference when the confirmation API exposes it; otherwise a cart-based identifier may be used.

Edge cases:

• Registration-only categories (no cart) do not fire Add to cart.
• Free orders with no line items and zero total may not emit a Purchase to organizer destinations (nothing to value).
• If a buyer never visits the public event page and goes straight to cart/checkout via a bookmark, organizer Pixel / GA4 funnel events may not fire for that session, because those destinations were never initialized for that visit.

---

Creating a tracker

1. Go to Marketing Tracking.
2. Click Add Tracker (or equivalent).
3. Enter:
   • Name (required) — e.g. “Meta – spring campaign”, “GA4 – events property”.
   • Type — Pixel, Script, or Analytics (see table above).
   • Tracking code (required) — Measurement ID, Pixel ID, or full script snippet.
4. Set Active to enable the tracker for the public event page.
5. Save / create.

---

Managing trackers

• Edit — Change name, type, or code.
• Enable / Disable — Toggle without deleting.
• Delete — Remove the tracker.

---

Using this in Meta Ads & GA4

• Meta: In Events Manager, select your pixel and verify PageView, AddToCart, InitiateCheckout, and Purchase. Create custom conversions or optimize for Purchase / Add to Cart as your campaign goal allows.
• GA4: In Admin → Events, mark purchase (and others if needed) as key events for reporting and Ads links. add_to_cart, begin_checkout, and purchase are sent with send_to scoped to your measurement ID so they don’t mix with Quicket’s own GA setup.

---

UTM vs Marketing Tracking

Feature	UTM Short Links	Marketing Tracking
Purpose	Track which link/campaign drove traffic	Measure behavior and conversions on Quicket pages
Mechanism	URL parameters on shared links	Injected pixels / GA4 config + automatic events
Use for	Reporting by campaign in Quicket analytics	Attribution and optimization in Meta / Google

Use both: UTMs for source tagging, Marketing Tracking for platform-side funnels.

---

See UTM Short Links, Event Analytics (Quicket-side metrics), and Event Dashboard for where Marketing Tracking lives in the sidebar.