The cheapest audience in any event campaign is the group of people who visited your ticket page and did not buy. They know what the event is. They were interested enough to click. Reaching them again costs a fraction of finding somebody new.
That audience only exists if the pixel was installed before the traffic arrived. A pixel added afterwards cannot see the past. This is the single most expensive mistake we see in event advertising, and it is completely avoidable.
Order of operations
Install tracking before the campaign, not with it. Concretely:
- Create the pixel in Meta Events Manager
- Install it on every page of the site, including the ticket flow if you control it
- Set up the conversion event for a completed purchase or registration
- Verify events are arriving using the Test Events tool
- Only then start spending
Steps four and five are where the discipline is. It is tempting to launch and check tracking later, particularly when an event date is close. Resist it. A week of untracked spend is a week you cannot learn anything from and cannot retarget against.
Standard events and custom conversions
Meta provides standard events like ViewContent, InitiateCheckout and Purchase. These are useful and you should use them. They are also generic: if you run several events from the same site, a Purchase event alone does not tell you which one sold.
A custom conversion narrows a standard event by URL. If the confirmation page for one event lives at a distinct URL, you can define a conversion that fires only for that event and optimise a campaign directly against it. In our own account we run named conversions per event for exactly this reason, and it is the difference between knowing your campaigns worked and knowing which campaign worked.
Verify, do not assume
Open Events Manager, go to Test Events, and walk through your own ticket flow. You should see each event arrive in real time. If Purchase does not fire, the confirmation page is not tagged, which is common when the checkout lives on a ticketing platform you do not control.
Where the confirmation page is outside your control, use the platform's own tracking integration. Most ticketing platforms have a field for a Meta pixel ID. It is less flexible than doing it yourself, and considerably better than nothing.
What you get for the effort
Three things, all of which compound.
Retargeting. Visitors who did not convert become an audience you can reach again, usually at a much lower cost per registration than cold traffic.
Lookalikes. Once enough people have converted, Meta can find more people who resemble them. This works better than any manual interest targeting you can construct, and it needs conversion data to exist at all.
Honest reporting. Without conversion tracking, a campaign report shows reach and clicks. Those numbers can look excellent while selling nothing. With tracking, you can see cost per registration, which is the only number that matters.
Set it up once, keep it forever
The pixel data lives in your ad account, not ours and not any agency's. Audiences built during one event are available for the next one. An organiser running four events a year who installed tracking properly at the start of year one is, by year two, working with something a first-time advertiser cannot buy at any price.
Related.
The last 72 hours: capturing the registration surge
Most event registrations arrive in the final three days. Here is the sequence that catches them instead of missing them.
Promoting a webinar with a small list
What to do when you have 200 subscribers and need 100 attendees, and why paid social is not always the first answer.
Tell us the date. We'll tell you what to do first.
Send the event name, the date, and who you're trying to reach. You'll get a prioritised plan back. No pitch deck, and no retainer conversation until you want one.