Connect Your Meta Pixel

If you run ads on Facebook or Instagram, you can connect your own Meta Pixel to your Esora page. Once it’s connected, every paid order you sell on Esora is reported to your own ad account.

What you get

• Purchases in your own Ads Manager — each completed paid order shows up as a Purchase, with the order total as its value.
• Cost per purchase per campaign — you see what each campaign, ad set and ad actually cost you per sale, next to the money it brought in.
• Campaigns that optimize for sales — with purchases arriving, you can run campaigns that optimize toward purchases instead of clicks or landing page views.

This covers the events you sell on Esora. Your pixel runs on your Esora event pages and sales are reported from our server.

What you need from Meta

Two things, both from Meta Events Manager (business.facebook.com → Events Manager). You need to be an admin of the dataset (pixel) you want to use.

1. Your Pixel ID

1. Open Events Manager and go to Data sources.
2. Select your dataset (your pixel).
3. Copy the number shown under the dataset name. It’s a plain number, usually 15–16 digits.

Don’t have one yet? Create a dataset in Events Manager first, then come back for the ID.

2. A Conversions API access token

1. In Events Manager, open the same dataset and go to its Settings tab.
2. Scroll to the Conversions API part of the page.
3. Choose Generate access token and copy the token.

Copy it right away — Meta shows the full token once. If you lose it, generate a new one; that’s fine, and you can paste the new one over the old one in Esora.

The token is a credential

Anyone holding it can send events to your pixel. Send it over a private channel only, and never post it publicly.

Add them in Esora

You do this once per page, and you need manager access to that page.

In the web console

1. Open esora.app/manage and pick your page.
2. Go to Settings → Integrations.
3. Under Meta Pixel & Conversions API, paste your number into Pixel ID.
4. Paste your token into Conversions API access token.
5. Press Save.

In the Esora Organizer app

1. Open the Profile tab.
2. Under Manage, tap Meta Pixel.
3. Fill in Pixel ID and Conversions API token.
4. Tap Save changes.

Both places write to the same settings — use whichever you have open.

What happens after you save

Esora saves what you typed, then checks the pair with Meta right away. You get one of three answers:

• Connected — Meta accepted your pixel and token. Nothing more to do.
• Saved, but Meta did not accept these credentials — your values are stored, and Meta’s own explanation is shown. Fix the pixel ID or the token in Meta and save again.
• Saved, but we couldn’t reach Meta to check — this says nothing about your credentials. It only means the check itself didn’t get an answer. Save again later if you want a confirmation.

Your values are always saved, whatever the check says. The check never blocks the save.

From then on:

• Your pixel runs on your Esora event pages and records a page view when somebody opens one of them. It never sees another organizer’s traffic.
• Every completed paid order is reported from our server, not from the buyer’s browser, so ad blockers don’t drop it.
• Each paid order counts once, however many tickets are on it. So “cost per purchase” in Ads Manager is your cost per order, not per ticket.
• Free orders are not reported. Free registrations and zero-price orders carry no revenue, so nothing is sent for them.

What Esora sends

The purchase report carries the order total and currency, the number of tickets, the event’s ID, and the buyer’s email and phone in hashed form so Meta can match the sale to a person who saw your ad. It never carries your event’s title, description, or ticket type names.

Replacing or removing the token

Esora never shows a saved token again — not in the console, not in the app. That shapes two things:

• To keep your token, leave the token field empty when you save something else. An empty field means “keep the one you have”.
• To replace it, paste the new token over the empty field and save.
• To remove it, use Revoke token in the web console or Remove token in the app. Purchases stop being reported immediately. Your Pixel ID stays, so the pixel keeps running on your pages — paste a new token whenever you want reporting back.

If something doesn’t work

• A token that only sends events is fine. The token generated in Events Manager under Conversions API can send events but can’t read your pixel’s settings. Our check is built for exactly that kind of token and accepts it.
• A wrong pixel ID or a wrong token shows up at save time, with Meta’s own wording. You don’t have to wait for a sale to find out.
• Pixel ID saved without a token? Nothing is checked and nothing is reported yet — the pair only works with both. You’ll see a plain “Saved”.
• Saving over and over is limited. Each save calls Meta, so a burst of saves in a few minutes is rate limited. Wait a few minutes and save again.
• No purchases in Ads Manager yet? Purchases only appear after a real paid order on Esora. Free orders never produce one, and Meta needs some time to show a fresh event.

Related

• Tracking Links — see which placement sold, without any ad account
• Selling Tickets on Esora — getting set up to sell
• Orders, Guests & Refunds — the orders behind these purchases

Stuck on a step? Get in touch.