Meta
Registrations and ticket purchases flow into your Meta Ads Manager, so ads optimize for conversions, not clicks.
AOA Plus
Meta Pixel and the Conversions API in your own ad account. You paste your Pixel ID and see how many registrations and sales each campaign brought in. AOA keeps nothing for itself: the events go to your account.
- Registrations and ticket purchases as conversions in your account
- Server events get through even with ad blockers
- One registration is one conversion, with no double counting
- The event city is sent separately so Meta understands it is an offline event
Why server-side conversions matter
A browser pixel loses some events: ad blockers and iOS restrictions cut it off silently. So besides the pixel, we send conversions from the server, and they get through. Meta merges both sources into one event, so your stats are not doubled.
What reaches your account
- Event page view
- Confirmed registration, including guests without an account
- Ticket purchase with the amount in hryvnia
Funnel remarketing
Since views and registrations arrive as separate events, you get an audience of people who viewed the event but did not register. It is the cheapest audience for filling the last seats a few days before the date.
What we do not do
We do not connect to your ad account through a login and we do not see your campaigns: you just paste your own IDs. Check ad reports in Meta Ads Manager. AOA has its own event analytics inside, and those are different things.
How to connect
- Organization management > Settings > Tracking
- Paste your Pixel ID and Conversions API token
- Click "Send test event": success shows up as "Connected"