For everyone

Track visitors from an ad to an event RSVP or ticket

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 an RSVP or native ticket order on the gigiii 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; both Analytics and Marketing consent are needed for your Meta Pixel. Website consent does not replace gigiii consent.

What gigiii reports

Gigiii also emits older gigiii_* events for existing reports and GTM mappings. A standard event and its older counterpart can describe the same action. Do not count both as separate conversions. GA4, GTM and Meta page-view or conversion tags that you add yourself can also duplicate direct events from a saved GA4 or Meta ID. Review your GTM triggers and any automatic Pixel events before using counts for ads. 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 RSVP 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. The widget strips _gl and advertising click IDs from its links, so it does not provide cross-domain session stitching. For Google Ads reporting, enable auto-tagging, link the Ads and Analytics accounts, mark your chosen GA4 event as 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 CompleteRegistration or Purchase 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 RSVP 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. Advertising click IDs such as gclid, fbclid, and ttclid, and the _gl linker are stripped. 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

1. 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.
2. In your website's GTM Preview or browser dataLayer, check for one gigiii_embed_event with the expected event ID and action. It is an interaction, not a sale.
3. On the gigiii event page, check the URL for gigiii_source=widget and, if website Marketing consent was granted, the validated UTM labels. Confirm that advertising click IDs and _gl are absent. Make the separate gigiii cookie choice.
4. Complete a test RSVP or an authorized test 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.
5. 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.