Check your pixel is firing — see it with your own eyes

Event Tracker lists every event the server sent or kept, newest first. Open any row for the full story, and resend failed ones right from here.

1. 1
   Events Total events recorded.
2. 2
   Sent How many reached the platform successfully.
3. 3
   Failed How many didn’t go — red means you should take a look.
4. 4
   Waiting to send In the queue to be sent.
5. 5
   Purchases How many Purchase events.
6. 6
   Kept only Kept only for your own records, not sent anywhere (e.g. PageView).
7. 7
   By status All, Sent, Failed, Waiting, Kept only.
8. 8
   Event and platform Which event (PageView, ViewContent, AddToCart, InitiateCheckout, AddPaymentInfo, Purchase) and which platform (Facebook, Google or both).
9. 9
   Search By order number, event, pixel or response.
10. 10
    Refresh · Clear log Reload, or delete the whole log.
11. 11
    Dates Today, yesterday, more ranges or your own dates.

One line tells you what went, where it went, and what Meta replied.

1. 1
   Event The event name and which product or order.
2. 2
   Sent to Which platform and which pixel ID.
3. 3
   Value How much money and how many items.
4. 4
   Match How many customer details (phone, name, area…) went with it — the more, the better Facebook can recognize the person.
5. 5
   Status Sent/Failed and the platform’s reply — e.g. “Meta received 1 event.”
6. 6
   When When it happened and when it was sent.
7. 7
   Funnel tag Which eFunnel page it came from.
8. 8
   Details · Delete See full details or delete.

Click Details and it opens on the side — exactly what was sent.

1. 1
   Event and order Name, order number, status and platform.
2. 2
   Summary Value, items, number of match fields and how many attempts.
3. 3
   Delivery Which pixel, the shop’s or the funnel’s pixel, the platform’s reply (HTTP 200), when it was created and sent, event id, page and transaction id.
4. 4
   Identity sent Phone, name, area and so on — all hashed — plus browser ID (fbp), click ID (fbc), IP and browser.
5. 5
   Hashed Personal information is hashed with SHA-256 before it leaves the site; the platform only matches hashes.
6. 6
   Open Order Desk Open this order directly in Order Desk.

The product list and exactly what was sent.

1. 1
   Why hash The more information goes, the better the match — but the real information never leaves your site.
2. 2
   Products Which products, how many, at what price.
3. 3
   Exactly what was sent Expand to see the full data sent to the platform — handy to show your developer or ad agency.

If an event doesn’t go through for some reason, it isn’t lost.

1. 1
   Failed filter Only the ones that didn’t go.
2. 2
   Failed ×4 Failed, and how many attempts — it retries on its own after 1 minute, 10 minutes and 1 hour, then waits for you.
3. 3
   Reason What the platform said — e.g. “HTTP 400 — Invalid parameter”. Use this to fix the problem.
4. 4
   Send again Once fixed, resend in one click.

Event Tracker → Campaigns. Not what Ads Manager says — what actually happened on your own site, calculated on delivered orders.

1. 1
   Events kept Total events.
2. 2
   Browsers How many different people (browsers).
3. 3
   Purchases How many orders.
4. 4
   View → purchase What % of people who viewed actually bought.
5. 5
   Value of purchases Total order value.
6. 6
   Ad spend (imported) Spend brought in from Ads Manager.
7. 7
   Delivered orders How many were actually delivered.
8. 8
   ROAS on delivered ROAS based on delivered orders — for a COD business, this is the real ROAS.
9. 9
   Profit after ads & returns Profit or loss after ad spend and returns.

Split the same way Ads Manager does — campaign, ad set, ad.

1. 1
   Pixel · Dates · Search Which pixel, which period, and search by name.
2. 2
   Which level you’re on Campaigns → campaign → ad set — the path shows at the top.
3. 3
   Funnel steps Browsers, Page view, View content, Add to cart, Checkout, Payment info, Purchase, CVR and Value.
4. 4
   Based on delivery Delivered, Cost / delivered (spend per delivered order), ROAS and Profit after ads.
5. 5
   TOP REVENUE The row that brought in the most order value on this screen.
6. 6
   Spend How much was spent on this campaign.
7. 7
   Details Split by product, device, country and page (section 9).
8. 8
   Red profit It’s losing money — time to rethink this campaign.

Click a campaign name to see its ad sets; click an ad set to see its ads.

1. 1
   Path Where you are — click Campaigns to go back.
2. 2
   TOP REVENUE · BEST RATE BEST RATE means the highest view-to-purchase rate (only with at least 30 page views, so one lucky sale doesn’t win).

What’s behind a campaign or ad set.

1. 1
   Events How many events at each step — shows where people stop.
2. 2
   Products Which products people from this ad viewed/bought.
3. 3
   Devices Mobile or computer.
4. 4
   Countries Which countries — catches foreign traffic.
5. 5
   Pages How many times each page was visited.

Bring in spend from Ads Manager and each row shows spend, cost per delivered order, ROAS and profit after ads and returns.

1. 1
   BEST RATE badge The best purchase rate.
2. 2
   What the colors mean Green rates are above average, grey below.
3. 3
   What’s been imported How much for which dates — if it’s wrong, use “Remove the spend for these days”.
4. 4
   How In Ads Manager, pick the dates and level, then Export → CSV. For accurate daily numbers, use Breakdown → By time → Day. Adding Campaign/Ad set/Ad ID columns keeps things matched even if names change.
5. 5
   CSV FILE · Import spend Choose the file and import.

eSP Theme → Tracking. Pixel in the browser, Conversions API from the server — both carry the same ID, so Meta counts it only once.

1. 1
   Tabs Facebook, Google (GA4 + Tag Manager, Purchase from the server too), Clarity (recordings and heatmaps), Rules, Catalog & feed (Facebook/Google/TikTok product feeds), Storage (how many days to keep records).
2. 2
   Pixel + Conversions API Add a token and events also go from the server, with the customer’s phone, name and address hashed — this improves match quality.
3. 3
   Pixels You can add several pixels. With a test code, “Send a test” goes to Test Events — remove it when you go live.
4. 4
   What else goes from the server Purchase always goes. For the rest — ViewContent, AddToCart, InitiateCheckout, AddPaymentInfo — choose. PageView fires on every page, so it’s a lot of traffic for little gain.
5. 5
   Check it works After saving, test with Send a test Purchase.
6. 6
   Help Step-by-step instructions for setting up Facebook tracking.

The same rules for Facebook, Google and Clarity.

1. 1
   When Purchase is sent Usually Placed (as soon as the order comes in). Choose Confirmed, Delivered or Completed and fake or cancelled orders won’t teach the ad platform to find the wrong customers — a big advantage for a COD business. These are sent from the server, since the customer isn’t on the page by then.
2. 2
   Four options Placed · Confirmed · Delivered · Completed.
3. 3
   #order button = Add to cart Clicking the funnel’s “Order now” button means the customer is saying “I want this” — so it’s counted as Add to cart.
4. 4
   Ignore staff People who can edit the site aren’t customers; blocked visitors are excluded too.
5. 5
   Currency Only the 3-letter code — BDT. Write ৳ or Taka and Meta and Google drop the value.