"Can you add my Meta pixel to the event page?" We get that question regularly from organisers who advertise, and the answer is always: no. MijnEvent's event pages and checkout run no tracking pixels whatsoever — no Meta, no Google Tag Manager, no Google Ads, no TikTok. Not because it's technically hard, but because we don't want to: our pages are free of tracking cookies, and they'll stay that way. At the same time, we fully understand you want to know whether your ads actually sell tickets. You can — on your own website, under your own cookie consent. In this article we explain why we draw this line, and how two building blocks (the embed widget and a custom thank-you URL per event) let you measure your campaigns from click to conversion.
Why we don't take part in tracking
A tracking pixel is never "just a tiny pixel". Whoever places such a tag on a page gives an ad platform a look at every visitor: which pages someone views, what they buy and — combined with the same pixels on thousands of other sites — a profile of who they are. The GDPR and the European ePrivacy rules are clear about this: it's only allowed with prior, freely given consent. Hence all those cookie banners.
We built MijnEvent privacy-first, and this simply doesn't fit in. Someone buying a ticket for your event didn't ask to be followed around the internet afterwards. That's why we place no marketing cookies, never sell visitor data, and why our ticket pages don't need a cookie banner sliding into view: there's nothing to accept. This line doesn't stand on its own, by the way — at checkout we also ask for as little data as possible.
That makes tracking, as far as we're concerned, not a platform feature but a marketing choice. And that choice belongs to you as the organiser — on your own website, under your own responsibility and your own consent prompt. We won't take part in it on our pages; what we do is make sure you can set it up properly on yours.
What you do get: cookie-free visitor statistics
No pixels doesn't mean flying blind. Your event pages are counted by a cookie-free analytics service, hosted entirely in the EU, that collects no personal data. In your admin, under Visitors, you'll find the page views and unique visitors of your event pages — per day, per event, over the last 7, 30 or 90 days. That's plenty to see whether your promotion is working: does traffic spike after your newsletter, is the Instagram announcement doing its job? Together with the sales statistics and CSV export you have the funnel from visit to sale in view.
What you won't see here is which ad delivered a specific buyer. For that you need conversion measurement — and you set that up on your own domain, with the following two building blocks.
Building block 1: the widget on your own website
With the embed widget you sell tickets directly on your own site: one script line and one div (the code is ready in your admin under Integrations), and ticket sales appear on a page of your own domain. And on your page, you decide what runs: your Google Tag Manager container, your Meta pixel, your TikTok tag — behind your own cookie banner.
So don't send your ads to your MijnEvent subdomain; send them to this page, with UTM parameters in the URL. Every click then arrives on your domain, where your ad platform and your own analytics register it as usual.
To be clear: the widget itself is an iframe loaded from your MijnEvent subdomain. Your pixels can't look inside it, and we don't load any pixels into it — what a visitor clicks inside the widget stays private. You measure the landing (this building block) and the outcome (the next one); the step in between is exactly the part where the visitor is left alone.
Building block 2: a custom thank-you URL per event
In your admin, you set the custom thank-you URL after payment per event, for example https://yoursite.com/thank-you. After a successful payment we then send the buyer not to our standard thank-you page, but to that page on your website. And there — on your domain, behind your consent — you fire your conversion event: Purchase for Meta, a conversion action for Google Ads, CompletePayment for TikTok, or a purchase event in your own analytics.
The redirect itself deliberately carries no order or personal data: you count a conversion, not a person. And this building block also works without the widget — buyers who purchase directly on your MijnEvent event page land on your thank-you page after payment too.
From click to conversion in five steps
- Create a thank-you page on your own website, for example
yoursite.com/thank-you. - Place your tags there (and on your landing page) — Meta, Google, TikTok — behind your cookie consent.
- In MijnEvent, set the custom thank-you URL for your event to that page.
- Point your ads at the page with the widget, with UTM parameters.
- In your ad platform, define a conversion on visits to
/thank-you.
The result: ad → your landing page (click measured) → picking tickets and paying (private) → your thank-you page (conversion measured). The ad platform ties click and purchase together using its first-party cookies on your domain — without a single pixel ever sitting on a MijnEvent page.
On your own website, you're in charge
Fair is fair: whatever you place on your own site is your responsibility. Ask for consent before marketing tags fire, list them in your privacy policy, and honour a "decline" click just as neatly as an accept. The GDPR applies to you as an organiser as much as it does to us as a platform.
Measuring where it belongs
Privacy first doesn't mean you're not allowed to know anything — it means measuring happens where it belongs: on your own website, under your own consent prompt, in your own organisation's name. The ticket pages themselves stay clean, with no banner and no onlookers. That way we keep our part tidy, and you keep a grip on your marketing. Questions about your setup? We're happy to think along.
