Meta, TikTok & Google Pixels for Event Organisers: The Complete A–Z Guide

You've boosted a post on Facebook, run a TikTok ad, maybe put a few thousand rupees behind an Instagram campaign, and you have no real idea whether any of it actually sold a ticket. If that sounds familiar, this guide is for you. "Pixels," "Conversions API," "access tokens", the words sound technical, but the ideas behind them are simple, and once they're set up they quietly do some of your hardest marketing work for you. On TicketsMinistry it's all built into your event pages, no code required, so as an organiser you get it out of the box. No coding required, and no prior knowledge assumed.

By the end you'll understand what a pixel is, why the Conversions API now matters just as much, and exactly how to create a Meta (Facebook & Instagram) Pixel, a TikTok Pixel, and a Google Analytics 4 property, generate their access tokens, and add them to your TicketsMinistry event so tracking starts the moment your listing goes live. You'll also learn how to build tagged links that tell you exactly which influencer, campaign, or promoter drove each ticket sale.

The big picture: what "tracking" actually means

Think of a pixel as a doorbell camera on your event page. Every time someone visits, views ticket prices, starts checkout, or buys, the camera quietly tells the advertising platform (Meta, TikTok, or Google) what happened. That feedback is the whole point: once the platform knows who actually buys tickets, it can stop wasting your budget on people who never will and start showing your ads to more people who look like your real buyers. Better data in means cheaper tickets sold out.

Without tracking, the ad platform is guessing. With it, every rupee you spend teaches the system to spend the next rupee smarter. That's the single most important thing to understand, everything below is just the how.

The jargon, decoded in one list

• Pixel: a tiny piece of tracking code that lives on your event page and reports visitor actions back to an ad platform. "Meta Pixel," "TikTok Pixel", same idea, different platform.
• Event (in tracking terms): a single tracked action, a page view, an add-to-cart, a checkout, a purchase. Don't confuse it with your actual event; here it just means "a thing a visitor did."
• Conversion: the action you care about most, almost always a completed ticket purchase.
• Conversions API (CAPI): a way for the tracking to be sent from a server instead of only from the visitor's browser, so you don't lose data to ad blockers and privacy settings. Meta calls it the Conversions API, TikTok the Events API, Google the Measurement Protocol.
• Access token: a secret password that authorises server-to-server tracking (the Conversions API). You generate it once inside the ad platform.
• Audience: a group of people the platform builds for you, e.g. "everyone who started checkout but didn't buy."
• Retargeting: showing ads specifically to people who already visited your event page, your warmest, most likely buyers.
• Lookalike / similar audience: new people the platform finds who resemble your existing ticket buyers.
• ROAS (return on ad spend): revenue divided by ad spend, the number tracking finally lets you measure honestly.

What a pixel is, really

A pixel is just a short snippet of code the ad platform gives you, identified by a number called a Pixel ID (or a Dataset ID). On a normal website you'd paste that code into your pages yourself. On TicketsMinistry you don't touch code at all, you paste only the ID into your event, and the platform fires the tracking for you.

Once it's live, the pixel reports a standard set of shopping actions as buyers move through your event page. On TicketsMinistry these fire automatically:

• Page View: someone opened your event page.
• View Content: someone looked at your event and its ticket prices.
• Add to Cart: someone selected tickets.
• Begin Checkout: someone started the payment process.
• Purchase: someone completed the booking, the conversion that matters most, reported with the order value so the platform knows exactly how much revenue that ad produced.

Why a pixel alone isn't enough anymore, and what the Conversions API fixes

A browser pixel is fragile. Apple's iOS privacy changes, ad blockers, cookie restrictions, and people clearing their history all mean a chunk of purchases never make it back to the ad platform. When that happens, the platform undercounts your sales, thinks your ads are performing worse than they are, and gets worse at finding buyers, a quiet tax on your budget.

The Conversions API (CAPI) solves this by sending the same events from a server directly to the platform, bypassing the browser entirely. The best practice is to run both together: the browser pixel and the server-side API report each purchase, and a shared order ID lets the platform recognise them as the same sale and count it only once (this is called deduplication). More complete data, no double-counting.

• Recovers purchases the browser pixel would have missed, often 10–30% more measured conversions.
• More accurate ROAS, so you can trust the numbers when deciding where to spend next.
• Better ad optimisation, because the platform learns from complete data, not a partial picture.
• More resilient to future privacy changes, since server-side tracking doesn't depend on cookies.

Meta (Facebook & Instagram) Pixel: what and why

Meta is the default channel for most lifestyle, music, and public events in Sri Lanka, and its pixel is the most mature of the three. Set it up and you unlock retargeting people who viewed your event, building lookalike audiences from past buyers, and letting Meta automatically optimise delivery toward purchases rather than just clicks.

How to create your Meta Pixel (step by step)

• Go to business.facebook.com and create a free Meta Business Portfolio (Business Manager) if you don't have one, this is the account that owns your pixel and ad account.
• Open Events Manager from the menu (business.facebook.com/events_manager).
• Click "Connect data sources," choose "Web," and click Connect.
• Name your dataset/pixel (e.g. your brand or venue name, not the individual event, you reuse one pixel across all your events) and click Create.
• When asked how to install it, you can skip the code installation, on TicketsMinistry you only need the ID.
• Copy your Pixel ID (also shown as "Dataset ID"), a 15–16 digit number like 123456789012345. That's the value you'll paste into TicketsMinistry.

How to generate a Meta Conversions API access token

• In Events Manager, select your dataset/pixel.
• Open the Settings tab for that dataset.
• Scroll to the "Conversions API" section and find "Generate access token" (under Set up manually / directly).
• Click Generate access token and copy the long string it produces, treat it like a password and never post it publicly.
• Store it somewhere safe. This token is what any server-side integration uses to send purchases straight to Meta.

TikTok Pixel: what and why

TikTok is where younger, high-energy audiences for concerts, festivals, and nightlife live, and short creator-style ads there can massively outperform polished banners. The TikTok Pixel does the same job as Meta's: it tracks who views and buys, so TikTok can optimise toward ticket sales and let you retarget engaged viewers.

How to create your TikTok Pixel (step by step)

• Go to ads.tiktok.com and create a free TikTok Ads Manager account (or a TikTok Business Center account) if you don't have one.
• Open the menu and go to Tools (or Assets) → Events.
• Under "Web Events," click "Manage" then "Set up Web Events."
• Choose the "TikTok Pixel" connection method, then "Manually install the code" / Developer Mode, again, you don't actually install code on TicketsMinistry, this just creates the pixel.
• Name your pixel and finish setup.
• Copy your Pixel ID, a long alphanumeric string. That's what goes into TicketsMinistry.

How to generate a TikTok Events API access token

• In Events Manager, open the web pixel you just created.
• Go to its Settings tab.
• Find the "Events API" section and click "Generate Access Token."
• Copy and safely store the token, this is what authorises server-side purchase tracking to TikTok.

One Sri-Lanka-specific heads-up: TikTok does not accept LKR as a currency in its tracking. If your tickets are priced in rupees, TikTok will still record that a purchase happened (great for building audiences and optimisation), but it won't show a rupee revenue figure or ROAS against it. Meta and Google both handle LKR fine, so treat TikTok's value reporting as a known blind spot, not a setup mistake on your end.

Google Analytics 4: the odd one out (and why you still want it)

Google Analytics 4 (GA4) isn't strictly an advertising pixel, it's a measurement tool. Where Meta and TikTok pixels exist mainly to feed their own ad systems, GA4 tells you the fuller story of your traffic: where visitors came from, which channels drive the most buyers, how far people get before dropping off. Link it to a Google Ads account and it also powers conversion tracking for Google and YouTube ads.

• See which source, Instagram, TikTok, Google search, a WhatsApp share, actually sends buyers, not just clicks.
• Spot where people abandon (e.g. lots of Begin Checkout but few Purchases points to a checkout or pricing issue).
• Free, and the closest thing to a neutral referee across all your channels.
• Feeds Google Ads conversion tracking if you ever run search or YouTube campaigns.

How to create a GA4 property and get your Measurement ID

• Go to analytics.google.com and sign in with a Google account.
• Click Admin (the gear icon), then "Create" → "Property." Name it after your brand, set the country to Sri Lanka and the currency (LKR is supported here).
• When prompted for a platform, choose "Web" and create a "Web data stream" (you can enter ticketsministry.com or your own site as the URL).
• Copy your Measurement ID, it starts with "G-" followed by letters and numbers, e.g. G-XXXXXXXXXX. That's the value TicketsMinistry asks for.

The GA4 server-side equivalent: the Measurement Protocol API secret

• In GA4, go to Admin → Data Streams and open your web stream.
• Scroll to "Measurement Protocol API secrets" and click "Create."
• Give it a nickname and copy the generated secret, this is GA4's version of a Conversions API token for server-side tracking.

Adding your IDs to your TicketsMinistry event

This is the easy part, and where a lot of the complexity above disappears. TicketsMinistry handles the code, the event firing, and browser-plus-server deduplication for you. You just supply the IDs.

• When you list or edit your event, go to the "Analytics Tracking IDs" step.
• Meta Pixel ID: paste your 15–16 digit Meta Pixel/Dataset ID (e.g. 123456789012345).
• Google Analytics ID: paste your GA4 Measurement ID (e.g. G-XXXXXXXXXX).
• TikTok Pixel ID: paste your TikTok Pixel ID.
• Save, and that's it. From then on, every View Content, Add to Cart, Begin Checkout, and Purchase on your event page is reported to your pixels automatically, with the purchase value attached.

You only need the Pixel IDs to get tracking live on TicketsMinistry, the access tokens you generated are for server-side setups and for tracking on channels you control directly (like your own website or a dedicated ad integration). Keep them safe; if you later want to discuss advanced server-side conversion tracking for your campaigns, have them ready to share with our team.

What stays private: your buyers' data and your event's numbers

A fair question before you switch on any tracking: does this hand you, or anyone else, your buyers' personal details? The short answer is no. Here's exactly what the integration does and doesn't share:

• Your buyers' raw personal data, name, email, and phone number, is never shared with you (or any other organiser) through the pixel or Conversions API. The ad platforms only ever receive it in a hashed, anonymised form, used purely to match a sale back to an ad they showed.
• In your ad account you see aggregated performance only, conversion counts, audience sizes, and ROAS, never a downloadable list of who bought a ticket.
• Your tracking is sealed to your own event. Your pixel only ever receives activity from your event's pages, so it never picks up traffic from other organisers' events, and they never see yours.
• The same isolation applies in your dashboard: event insights are private to your own events. One organiser can never view another organiser's numbers.

Tracking influencers, campaigns, and promoters with tagged links (UTMs)

Your pixels tell you what happened on your event page, but not reliably which influencer, ad, or promoter sent that visitor. That's the job of a tagged link, better known as a UTM link. It's simply your normal event link with a few labels added to the end. When someone clicks it, Google Analytics records where they came from, so you can see which source actually drove page views and ticket sales, right down to the rupee.

There's nothing extra to install for this. GA4 reads these labels automatically (Meta and TikTok pick them up too). You just make a differently-tagged version of your event link for each source, hand each one out, and let the reports do the rest.

The four labels you'll use

• utm_source, WHO sent the traffic: the specific origin, an influencer's handle, a promoter's name, or a platform. Examples: nimal_ig, dj_promotions, facebook, whatsapp.
• utm_medium, the TYPE of channel: how they're reaching people. Examples: influencer, paid_social, email, sms, affiliate.
• utm_campaign, WHICH push it belongs to: the event or promotion, so you can compare campaigns against each other. Examples: pulzex-launch, earlybird-2026, final-week.
• utm_term (optional), an extra detail, usually the audience, ticket tier, or paid keyword. Examples: vip, colombo, students. There's also a fifth, utm_content, handy if you want to A/B two versions of the same post (story-a vs story-b).

How to build one

Take your normal event link, add a question mark, then the labels joined by ampersands. For an event page it looks like this: https://ticketsministry.com/concerts/pulze-x/abc123?utm_source=nimal_ig&utm_medium=influencer&utm_campaign=pulzex-launch&utm_term=vip. If you'd rather not type parameters by hand, Google's free "Campaign URL Builder" (search that exact name) assembles the whole link for you, you just fill in the boxes and copy the result.

Worked examples for three common sources

• Influencer: an Instagram creator posting your event in their Stories, utm_source=nimal_ig, utm_medium=influencer, utm_campaign=pulzex-launch. Now you can see precisely how many tickets Nimal's post drove, not just how many likes it got.
• Paid campaign: a boosted Facebook ad, utm_source=facebook, utm_medium=paid_social, utm_campaign=earlybird-2026, utm_term=colombo. Compare it side by side with your other paid pushes.
• Third-party promoter: an outlet or agent selling on your behalf, utm_source=dj_promotions, utm_medium=affiliate, utm_campaign=pulzex-launch. Give every promoter their own utm_source and you can rank them by tickets actually sold, and settle commissions on real numbers.

Naming rules that keep your reports clean

• Always use lowercase, GA4 treats Facebook and facebook as two separate sources, which quietly splits your data in half.
• No spaces, join words with a hyphen or underscore (early-bird, not "early bird").
• Be consistent, pick influencer OR creator and use the same word every time; mixing them fragments your reports.
• Keep a simple spreadsheet of every link you create and who it went to, so six weeks later you still remember what dj_promotions was.
• Never tag links that point between pages of your own, an internal UTM link overwrites the visitor's real source and corrupts your attribution.

Reading it back in GA4

In Google Analytics, open Reports → Acquisition → Traffic acquisition. You'll see sessions and conversions broken down by source and medium; add "Session campaign" as a secondary dimension to compare specific pushes. Because purchase value flows through as well, you can see not just which influencer or promoter sent the most clicks, but which one sent the most rupees, and that's the number that tells you who's worth working with again.

Practical suggestions to get real value out of this

• Set up your pixels before you spend a single rupee on ads, tracking only counts actions that happen after it's live, so a pixel added mid-campaign misses everything before it.
• Use one pixel per platform for your whole brand, not a fresh pixel for every event. A single pixel that accumulates history across events learns faster and builds bigger audiences.
• Warm up, then retarget: run cheap reach/traffic ads first to fill your pixel with visitors, then retarget the people who viewed but didn't buy, they're your cheapest conversions.
• Build a lookalike/similar audience from your past purchasers once you have enough of them, it's the single highest-leverage targeting move for a new event.
• Give the platform room to learn: ad systems optimise best after roughly 50 conversions per week, so don't panic-edit a campaign after two days of data.
• Always run the browser pixel and the Conversions API together for the fullest, most accurate data, not one or the other.
• Verify it's working: install the free "Meta Pixel Helper" and "TikTok Pixel Helper" Chrome extensions and use GA4's DebugView, then walk through your own event page and confirm the events fire.
• Respect privacy and consent, show a cookie/consent notice where required and never treat tracking data as a licence to spam.

Common mistakes to avoid

• Creating a brand-new pixel for every single event, it resets the learning every time.
• Adding the Pixel ID but forgetting to actually run ads on that platform, the pixel only pays off when paired with campaigns.
• Pasting the wrong ID in the wrong field (a GA4 "G-" ID into the Meta box, for instance), double-check each one before saving.
• Expecting TikTok to report rupee revenue, it won't, because it doesn't accept LKR; judge TikTok on conversions and audience growth instead.
• Ignoring the data once it's flowing, tracking is only useful if you actually read it and shift budget toward what's converting.

Pixels and the Conversions API sound intimidating, but stripped of the jargon they're just a feedback loop: tell the ad platforms who buys, and they'll help you find more people like them for less. Set them up once, add the IDs to your event, read the numbers, and every campaign you run from then on gets a little smarter, and a little cheaper, than the last.