Articles on: Omega Facebook Multi Pixels

Protect your ad data with Bot & Fraud Protection

Not every visit to your store is a real shopper. Bots, crawlers and fake orders can trigger the same events as real customers, and if those events reach Meta, you end up paying to optimize your ads on numbers that aren't real.


💡Omega can keep that traffic out of your Meta data with Bot & Fraud Protection


This guide explains what this feature does, how to turn it on, and how to review and resend events.


Why this matters

Meta's ad delivery learns from the events your store sends. When bot traffic is mixed in, two things can go wrong:

  • Inflated numbers. Bot visits show up as Page view or View content events, so your traffic looks bigger than it really is.
  • Misleading optimization. Fake purchases with made-up values teach Meta the wrong idea of what a good customer looks like, so your budget can end up in the wrong places.

Cleaner data gives Meta a truer signal and gives you reports you can trust.


Layer 1: Verified bot filtering

Some bots visit your store all the time: Google scanning your pages for search, social platforms building link previews, AI tools like ChatGPT reading content. They aren't shoppers, but some can still trigger events.


👉 Verified bot filtering automatically excludes visits from these known bots, so your numbers stay accurate. It's always on, so there's nothing to set up.




This filter only targets crawlers that identify themselves. Real visitors are not affected.


Layer 2: Suspicious bot blocking

This setting goes further. It blocks events identified as bot or suspicious activity so your ad spend goes toward real customers.


👉 To turn it on, go to Settings > Bot & Fraud Protection and switch on Suspicious bot blocking.


Review blocked events


Go to Tracking analytics and open the Bot & fraud tab. It lists the events that were held back.



For each event, click to Details cutton and you can see:

  • The reason it was held, so you know why it scored low.
  • A Need review column, which points out the events worth a second look before you decide what to do.
  • The page where it happened
  • IP address and country
  • Device
  • Meta cookie
  • A link to the matching order in Shopify, when the event is an order


These details help you judge whether the event is really a bot or fake order, or a genuine customer that was held by mistake.


Resend an event

If you review a held event and decide it's real, you can send it to Meta yourself.


Updated on: 05/10/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!