Articles on: Omega Facebook Multi Pixels
This article is also available in:

⚙️ App Checklist

Ensure everything is set up for success


1. Required App Embed


Your events won’t fire unless the App Embed is toggled ON in your theme editor.

What is Theme App Extension?

Theme App Extension (TAE) is Shopify’s new, safer, and easier way to connect third-party apps (like Omega) to your Online Store.

Instead of manually inserting code or snippets, you can now enable the integration directly through the theme editor — no coding needed.

Previously, Omega had to inject scripts/snippets into your theme (sometimes manually). With Theme App Extensions:

  • You just toggle it ON or OFF.
  • It ensures full compatibility with Shopify OS 2.0.
  • The app automatically stops tracking when uninstalled (no leftover code or “ghost” snippets).

💡We try our best to explain this to non-tech people, but if you are more tech-savvy and would like to learn more, just ask us.


Integrate Two Owls with your Online Store via Theme app extension


💡 FAQ: Why is this necessary?

There are multiple benefits:

  • Keeps the app fully compatible with Shopify Online Store 2.0.
  • Reduces manual theme access requests.
  • Automatically cleans up code upon uninstallation (no leftover snippets).
  • Ensures you’re always using the latest version of the app embed.



2. Define a timezone

To prevent data mismatches in Facebook Events Manager, define your timezone in the app.

This tells Two Owls to record events using the same timezone Facebook uses to report — so both speak the same “time language”.


How to define timezone

  1. Open the app → Settings → General section.
  2. Select your timezone (e.g., Ho Chi Minh, Asia (GMT +07:00)).
  3. Click Save.

✅ Result: Event timestamps match between Omega and Facebook.

What happens if I don’t set this up?

If your app records events in a different timezone, mismatches may occur:

  • Events appear in the past:

If your Facebook Ad Account uses UTC+5 and a purchase happens at 1 a.m. (UTC+5) on June 26,

Two Owls (by default) might record it as 8 p.m. on June 25 (UTC).

Facebook won’t convert the timezone — so it looks like the purchase happened the day before.

  • Events appear from the future:

Similarly, events recorded ahead of your Ads timezone might be rejected by Facebook.

❌ These mismatches can cause inaccurate reports and confusion in attribution.



3. Choose the right pixel

Avoid duplication or triple-counting by ensuring that you don't put the same pixel ID in Two Owls and some other pixel installation methods!

Avoid accidental mess: for data accuracy's sake, carefully ensure that you don't put the same pixel ID in Two Owls and some other pixel installation methods!

This is because the Two Owls app’s code already does the necessary thing to capture & send events upon an event instance, and other apps would probably do the same thing to your pixel.


Why this matters

The Two Owls app already handles all required event tracking and sending.

If another app or script also fires the same Pixel, you’ll end up with duplicate or inflated events in your Meta Events Manager.


Common places users forget to remove the pixel from:

  • Facebook Sales Channel
  • Shopify → Settings → Preferences → Facebook Pixel
  • Google Tag Manager
  • Theme code (previously hardcoded pixel snippets)


How to disconnect a pixel from the original Facebook Sales Channel?



Not sure if your setup is clean?

If you still see:

  • Over-reporting,
  • Duplicate events, or
  • Unusual purchase counts in Events Manager,

then you may still have leftover code or another app firing the pixel.

👉 Don’t worry — contact us via in-app chat or [[email protected]](), and we’ll help you verify.

Updated on: 11/11/2025

Was this article helpful?

Share your feedback

Cancel

Thank you!