For everyone
Track visitors from an ad to a ticket order
Connect event analytics, understand which actions gigiii reports, and test an ad-to-event journey.
If an ad sends visitors to your website, you can measure a visit and widget click there, then measure a visit to your gigiii public profile or event page and a free or paid native ticket order on the event page. These are separate browser events. A widget click does not prove that a guest registered or paid.
Before you start
Open the gear icon on the Meta Pixel card to save your Pixel ID. The card shows On after the ID is saved. Switching it off removes the saved ID; to reconnect, switch it on and enter the ID again.
You need a published gigiii event, the current Events → Embed snippet on your website, and a Premium account with access to external analytics. An account owner or admin can save a GA4 measurement ID (G-…), a Google Tag Manager container ID (GTM-…), or a Meta Pixel ID in Business → Integrations. These connections are independent. A GTM ID alone does not create GA4 or Google Ads conversions: your container needs the appropriate tags and triggers.
The current widget reads saved consent from supported website managers (Electric Social's ESConsent and Cookiebot) without an extra setup step. If your manager is unsupported, optional campaign forwarding and website interaction events stay off; a developer can connect it through GigiiiEmbed.setConsent({ analytics, marketing }). The widget still passes its own widget-origin information when clicked. The visitor also makes a separate cookie choice on gigiii. Analytics consent there enables your GA4 and GTM connections on public profile and event pages; both Analytics and Marketing consent are needed for your Meta Pixel on event pages. Website consent does not replace gigiii consent.
What gigiii reports
| Action | Where to check | Meaning |
|---|---|---|
| Ad landing and website page view | Your website's own tags | The visitor reached your page. |
gigiii_embed_event with event_selected or primary_cta_clicked | Your website's dataLayer | The visitor clicked an event link or button in the widget. |
| Event page view | GA4/GTM and Meta on gigiii, subject to consent | The hosted event page loaded. |
| Public profile page view | GA4/GTM on gigiii, subject to consent | Your EPK or place page loaded. |
view_item / Meta ViewContent | Your connected GA4 / Meta Pixel | The visitor viewed the event details. Normal page views remain separate. |
begin_checkout / Meta InitiateCheckout | Your connected GA4 / Meta Pixel | The visitor submitted a valid free or paid ticket form. Creating the order or payment may still fail. |
purchase / Meta Purchase | Your connected GA4 / Meta Pixel | A free or paid native ticket order reached a server-verified confirmed state. |
ticket_link_clicked | GA4 / GTM | The visitor clicked an external ticket link. This is not a checkout or purchase signal. |
A confirmed order counts as one conversion, regardless of whether its tickets are free or paid. Three tickets in one order are one purchase with quantity three. Free orders send a value of zero; paid orders send their ticket subtotal and currency. Pending, failed, cancelled and refunded orders do not send a purchase. The stable transaction reference without guest details helps prevent duplicate purchases; browser-session deduplication cannot guarantee complete or exact accounting.
If you deliver events through GTM, use Custom Event triggers named view_item,
begin_checkout, purchase and ticket_link_clicked. For ecommerce tags, choose
Send ecommerce data → Data Layer. Mark only purchase as the completed-order
GA4 key event / Google Ads conversion. Gigiii uses this contract directly and does
not send older event aliases or separate free-ticket registration conversions.
When a GA4 or Meta ID is saved, disable GTM tags that send the same events to that
property or Pixel. Check automatic Pixel events as well. A content view and normal
page view describe different steps; do not add a second page-view tag for
view_item. The Integrations page lets you remove an ID or turn off GTM; it does
not offer a switch for each event name.
First-party counts in Events → Guests come from gigiii records and may differ from browser analytics. Consent denial, browser blocking, ad blockers, delayed tags and repeat visits can make platform counts lower or different. External ticket and free ticket registration providers do not send a confirmed conversion through this connection.
Platform prerequisites
- GA4 and Google Ads: Use the same GA4 web stream on your website and gigiii event pages. Configure GA4 cross-domain measurement for both domains and test a real click through the widget. With both Analytics and Marketing allowed on your website, an ordinary click to a native gigiii event can obtain
_glfrom your installed Google linker. Keep the current embed loader and use the same stream on both domains. Modifier clicks and external providers keep their original links; blockers or an unavailable linker can prevent session continuity. For Google Ads reporting, enable auto-tagging, link the Ads and Analytics accounts, markpurchaseas a key event, and create a conversion from it. Gigiii does not create a Google Ads conversion action for you. - Meta Ads: Save the Pixel ID that belongs to the campaign, and verify
Purchasefor both free and paid orders in Meta Events Manager after the gigiii consent choice. Do not configure a second GTM tag for the same confirmed action. Gigiii does not provide a customer Conversions API connection. - TikTok and other ad platforms: Gigiii has no direct TikTok Pixel or Events API connection. A campaign can still drive visitors to your site, and your own consented tags can measure website and widget interactions. A completed free ticket registration or purchase on gigiii is not automatically sent to TikTok. If you use your GTM container for another platform, you must configure, consent-gate and test that platform's tags yourself. See TikTok's GTM setup guide.
With website Marketing consent, the current embed passes validated utm_source, utm_medium, utm_campaign, utm_id, utm_content, and utm_term labels from the current website URL to the gigiii event link. The iframe URL and rendered links strip advertising click IDs and _gl. With both website grants, a normal click to a native gigiii event can add the Google-generated _gl and validated Google/Meta click IDs to the new event-page URL. These identifiers are not sent to external providers or stored by the widget. ttclid is not forwarded. Do not put personal data in campaign labels. Tagged links describe campaign context; they do not guarantee ad-platform attribution or create a TikTok conversion.
Check one journey
- Open the real ad landing page with a test campaign URL. Confirm the expected UTM label is present in that page's address bar. Apply the website consent choice and click one widget event link.
- In your website's GTM Preview or browser
dataLayer, check for onegigiii_embed_eventwith the expected event ID and action. It is an interaction, not a sale. - On the gigiii event page, check the URL for
gigiii_source=widgetand, if website Marketing consent was granted, the validated UTM labels. With both website grants and an active Google linker, verify_glin the resulting native event-page URL and compare the GA4 client and session IDs across domains. With consent denied, identifiers must remain absent. Tagged URLs alone do not prove Ads attribution. Make the separate gigiii cookie choice. - Complete an authorized test free or paid ticket order. Check GA4 DebugView, Meta Test Events, or your GTM Preview for the relevant confirmed event. Check Google Ads conversion status separately after its conversion action is configured. Repeat with consent denied to verify that the expected browser tags stay off.
- Compare against Events → Guests. If a browser event is absent, first check the two consent choices, the saved ID and GTM enabled state, your container's triggers, browser blocking, and whether the order actually reached a confirmed state.
Inspect the event link inside the widget during setup: it should contain gigiii_source=widget even without a campaign. A campaign parameter on the iframe URL alone does not prove it reaches the gigiii event page. If UTM labels are missing, check the current website URL and whether the widget recognized a Marketing grant; an unsupported consent manager needs the optional bridge.
For the widget event schema and a consent bridge example, see the technical embed tracking guide and embed consent guide.