Marketing
The Marketing tab lets you manage tracking codes. Connect Facebook Pixel, Google Analytics, or Google Tag Manager to measure ad performance.
Accessing marketing
Go to Settings → Marketing.
Auto-Marketing welcome popup
When Auto-Marketing is enabled, Fanz can display a welcome popup to visitors on your event pages to grow your subscriber list. The popup collects two pieces of information from visitors:
- Email — required to subscribe the visitor
- Birthdate — used for birthday-based campaigns
The popup does not ask for a first name. This keeps the subscription flow short and reduces friction for visitors.
Tracking codes
Supported integrations
| Integration | Use case |
|---|---|
| Facebook Pixel | Track conversions from Facebook/Instagram ads |
| Google Analytics | Measure traffic and user behavior |
| Google Tag Manager | Centralized tag management |
Creating a tracking code
- Click Create tracking code
- Fill in the form:
- Type: Facebook Pixel, Google Analytics, or Google Tag Manager
- Code: Your pixel ID, GA measurement ID, or GTM container ID
- Reference name: A name for easy identification (e.g., "Main FB Pixel")
- Click Create
The code is saved to your brand and can now be assigned to events.
Tracking codes table
All your tracking codes appear in a table with:
| Column | Information |
|---|---|
| Type | Facebook Pixel, GA, or GTM |
| Code | The tracking ID |
| Reference name | Your custom name |
| Events | Which events use this code |
| Actions | Delete |
A green checkmark labeled CAPI token connected is shown next to a Facebook Pixel entry when a Meta Conversions API access token has been configured for it. This means server-side purchase event reporting is active for that pixel.
Assigning tracking codes to events
Tracking codes must be connected to each event individually. They don't apply site-wide automatically.
To assign a tracking code:
- Go to Events menu
- Select the event
- Click Edit
- Navigate to the Pixels & analytics section
- Select your tracking codes from the dropdowns (one per integration type)
- Save the event
You can also create a new tracking code directly from this screen if needed.
Site-wide pixel or per-event pixel?
Fanz has no "global" site pixel that fires on its own across every page. The model has two levels:
| Level | Where to configure | What it does |
|---|---|---|
| Brand tracking code | Settings → Marketing | Your brand's "catalog": you store the Pixel, GA or GTM ID once, with a reference name. On its own it fires nothing. |
| Event assignment | Events → [event] → Edit → Pixels & analytics (or from the code's own card in Settings → Marketing, with Assign to events) | Activates that code on the public event page. Each event supports one code per type (one Facebook Pixel, one Google Analytics and one Google Tag Manager). The purchase is reported on /checkout by Google Analytics and by Facebook Pixel. |
To make one pixel behave like a "site pixel", create the code once and assign it to all your events. When duplicating an event you can copy its tracking codes along with the rest of the configuration, so new events start with the pixel in place. Events without the code assigned report nothing to that pixel.
Facebook Pixel: events and Conversions API
Standard events fired
When a Facebook Pixel is assigned to an event, Fanz automatically fires the following standard Meta events as buyers move through the purchase flow:
| Event | When it fires |
|---|---|
| PageView | Buyer opens the event page |
| ViewContent | Buyer views event details |
| AddToCart | Buyer adds tickets to their cart |
| InitiateCheckout | Buyer begins checkout |
| Purchase | Buyer completes a ticket purchase |
All events are tied to the Pixel ID assigned to that specific event.
Meta Conversions API (CAPI)
What is CAPI?
The Meta Conversions API (CAPI) is a server-side integration that sends purchase events directly from Fanz's servers to Meta, independently of the browser pixel. This means conversions are reported even when a buyer's browser blocks tracking scripts via an ad blocker or browser privacy restrictions.
Why it improves accuracy
Browser pixels can be blocked or restricted, which means some purchases never show up in your Meta Ads reporting. CAPI solves this by:
- Reducing data loss — purchase events are sent server-side regardless of browser restrictions
- Deduplicating events — when both the browser pixel and CAPI fire for the same purchase, Meta automatically deduplicates them so conversions are not double-counted
- The result is a more complete and accurate picture of your return on ad spend (ROAS)
Configuring CAPI for a Facebook Pixel
When creating or editing a Facebook Pixel tracking code, you'll see a section titled Improve Purchase accuracy with Conversions API. The Meta Conversions API access token field is optional — leave it empty if you only want browser pixel tracking.
To enable CAPI:
- Open Meta Events Manager and navigate to your Pixel
- Go to Settings → Conversions API and generate an access token
- In Fanz, open the tracking code form for your Facebook Pixel
- Paste the token into the Meta Conversions API access token field
- Save — Fanz verifies the Pixel ID and token before saving
Note: The help text in the form reads: "In Meta Events Manager, open your Pixel, go to Settings > Conversions API, and generate an access token. Fanz verifies the Pixel ID and token before saving. Leave this empty if you only want browser Pixel tracking."
If a token is already saved, the field shows the placeholder "Token already saved. Paste a new one to replace it." You can also click Remove token to disable CAPI, or Keep token to leave the existing one in place. If you click Remove token, the form will show a notice that the saved CAPI token will be removed when you save changes.
Once saved, a green CAPI token connected indicator appears next to that pixel in the tracking codes list.
Google Analytics and Google Tag Manager
Google Analytics and Google Tag Manager are assigned the same way as the pixel: one per event, from Events → [event] → Edit → Pixels & analytics. They do not cover the whole site.
They do not do the same job. Google Analytics sends the purchase event. Google Tag Manager only loads your container on the event page.
Where each code loads
| Code | Where it loads |
|---|---|
| Google Analytics | On the event page, and again on the purchase confirmation page (/checkout) |
| Google Tag Manager | Only on the public event page. The container is not loaded again on /checkout |
Events Google Analytics fires
The event needs an assigned GA4 measurement ID. A GTM container on its own does not send these events.
| Event | When it fires |
|---|---|
| page_view | The buyer opens the event page |
| add_to_cart | The buyer submits checkout and a reservation is created |
| begin_checkout | The purchase is paid and the buyer continues to the payment provider |
| purchase | The confirmation page shows the purchase |
add_to_cart and begin_checkout include currency, value, and items. That items entry is a single item for the event (id, name, and function date), not each ticket or add-on.
The purchase event
Page. It fires on the purchase confirmation page, path /checkout. That is the page the buyer returns to after paying with Mercado Pago, Stripe, or another provider. It is not the event page, and it is not the form where they enter their details.
A rejected payment does not fire it. If the confirmation page shows the purchase, it does, including a purchase that is still pending settlement.
A free ticket that is confirmed without leaving the event page fires purchase there on a new site. On a classic site, that confirmation does not send purchase. To measure it, use a paid purchase and watch /checkout.
It does not fire when:
- The event has no Google Analytics code assigned. A GTM container alone does not send
purchase. - The buyer opens
/checkoutwithout having visited that event's page in the last 4 hours. That visit is where Fanz remembers which GA property belongs to the event. - That purchase was already reported. Each purchase is sent once.
Parameters
| Parameter | Sent? | What it contains |
|---|---|---|
| transaction_id | Yes | The purchase id, as text. For a Ticket Combo it identifies the combo order, not each component event. |
| value | Yes | The order's gross total: tickets plus the service charge, before discounts. With no discount, it is what the buyer paid. |
| currency | Yes | The purchase currency, for example ARS. |
| items | No | Fanz does not send an item list on purchase. |
Google Tag Manager
Fanz loads your container (GTM-…) on the event page you assigned it to. From there you can run the tags you configure in Google.
Fanz does not push a purchase event onto the dataLayer with transaction_id, value, currency, and items. To measure purchases in Google, also assign the Google Analytics measurement ID to that event. The GTM container is not on /checkout, so a GTM trigger does not see the paid purchase.
Marketing AI defaults
When configuring Marketing AI (auto-marketing) preferences for an event, you can save those settings as the brand-level default for future events. Check the option to save as default within the event's auto-marketing configuration, and all new events created through the event wizard will be pre-filled with those saved preferences — reducing repetitive setup across your calendar.
For full details on configuring Marketing AI flows and automation preferences, see the Marketing flows article.
Why use tracking codes
Facebook Pixel
- Track ticket purchases from Facebook/Instagram ads
- Build custom audiences of buyers
- Optimize ad campaigns for conversions
- Measure return on ad spend (ROAS)
- Add CAPI for more complete purchase reporting
Best for: Events with paid social media advertising
Google Analytics
- Understand visitor behavior on event pages
- Track traffic sources
- Analyze conversion funnels
- Compare event performance
Best for: Understanding audience and optimizing event pages
Google Tag Manager
- Load your container on the event page
- Manage your own tags from Google, without a code change in Fanz
Best for: Teams that already build their tags in Google Tag Manager
Fanz does not send the purchase event through GTM. Purchases are measured with Google Analytics. The detail is above, in Google Analytics and Google Tag Manager.
Best practices
One code per integration type — Most organizers have one Facebook Pixel, one GA property, and one GTM container. Create them once, reuse across events.
Enable CAPI for Facebook Pixel — If you run paid Facebook or Instagram ads, adding a Meta Conversions API token significantly improves the accuracy of purchase reporting. It's especially valuable if your audience tends to use ad blockers.
Only track events with paid ads — If you're not running paid ads for an event, you probably don't need tracking codes on it.
Test your tracking — After assigning codes, use Facebook Pixel Helper or Google Tag Assistant browser extensions to verify they're firing correctly.
Save Marketing AI defaults — Once you've tuned your auto-marketing preferences for one event, save them as the brand default so future events start pre-configured.
The popup collects only the visitor's email and birthdate. No first name is requested, keeping the form short and easy to complete.
Tracking codes are connected per event, not to your entire website. Go to Events → Select event → Edit → Tracking IDs to assign your codes.
Yes. Create the code once in Settings → Marketing, then assign it to as many events as you want.
Make sure: 1) The code is assigned to the specific event, 2) The code value is correct, 3) Use a browser extension to debug. Tracking only fires on event pages with assigned codes. The Google Analytics purchase fires on the confirmation page, /checkout.
Google Tag Manager does not fire that event. Google Analytics 4 does, on the confirmation page /checkout, when the paid purchase is shown there. The parameters are transaction_id (the purchase id), value (gross total: tickets plus the service charge, before discounts), and currency (the currency, for example ARS). It does not include items. The event needs Google Analytics assigned to it: the GTM container only loads on the event page and does not send purchase. The detail is in Google Analytics and Google Tag Manager.
CAPI is a server-side integration that sends purchase events directly from Fanz's servers to Meta. It's optional, but recommended if you run paid Facebook or Instagram ads — especially if your audience uses ad blockers. Without CAPI, some purchases may not appear in your Meta Ads reporting because the browser pixel was blocked.
No. When both the browser pixel and CAPI fire for the same purchase, Meta automatically deduplicates them. You won't see inflated conversion numbers.
In Meta Events Manager, open your Pixel, go to Settings → Conversions API, and generate an access token. Paste it into the Meta Conversions API access token field in the tracking code form.
No. Fanz tracking integrations work per-event. This gives you more control over which events trigger your tracking pixels.
Minimally. Tracking scripts load asynchronously and shouldn't noticeably impact page load times.
When setting up auto-marketing for an event, you can check an option to save those preferences as the brand-level default. Any new event you create through the wizard will then be pre-filled with those settings automatically. See the Marketing flows article for details.