Skip to content
Blog

How to Set Up Meta Pixel for Shopify Before Measuring Video ROI

Install Meta Pixel on Shopify the right way before you measure shoppable video ROI. Native channel, CAPI, event verification, and attribution notes.

How to Set Up Meta Pixel for Shopify Before Measuring Video ROI
IdeasHow to Set Up Meta Pixel for Shopify Before Measuring Video ROI

Set up Meta Pixel properly before you spend a rupee measuring video ROI. Without a clean pixel, your carousel widget will drive sales that Ads Manager credits to the wrong campaign, or to nothing at all. The fix is straightforward: install the pixel through Shopify's native Facebook & Instagram channel, verify events in Meta Events Manager, and only then wire beyondRegular attribution on top. Measurement is a plumbing job first, a marketing job second.

Install through the Facebook & Instagram channel, not a custom snippet

Skip the Additional Scripts box in theme.liquid. Shopify's Facebook & Instagram sales channel installs the pixel plus Conversions API in one flow, which is what you want. Custom snippets miss the checkout events on the Shopify-hosted gateway, and you end up debugging why Purchase never fires.

Connect the channel, pick the pixel ID, turn on Maximum data sharing so Conversions API is active, and accept the customer data terms. Now PageView, ViewContent, AddToCart, InitiateCheckout, and Purchase fire without you writing a line of code. If you already have a hand-rolled pixel from an agency two years ago, remove it before adding the native one, otherwise you get double-counted Purchase events and inflated ROAS.

Verify events in Events Manager before trusting any dashboard

Open Events Manager, pick your pixel, and use Test Events with your live store URL. Walk the funnel yourself on desktop and mobile: land on a collection, view a product, add to cart, hit checkout, complete a test order with Shopify's Bogus Gateway or a real Razorpay payment refunded after.

You are looking for two things. First, each event fires once, not twice. Second, Purchase carries value, currency (INR for India shoppers), and content_ids that match the SKUs. If Purchase shows up without value, your catalogue feed is broken and every ROAS number downstream is fiction. Fix the feed in the Facebook channel settings before moving on.

Layer beyondRegular attribution on top, not underneath

Once the base pixel is clean, install the beyondRegular script and drop your widget preset. On Pro plan we ship a Shopify web pixel that emits our own view, tag_click, and add_to_cart events tied to the video that drove the interaction. These sit alongside Meta's events, they do not replace them.

The reason this order matters: if you install our pixel first and Meta's pixel is misconfigured, you will see beyondRegular reporting 40 add-to-carts from the floating bubble while Ads Manager reports 12. Then you spend a week arguing about which number is right. Both are right. They measure different things. Get Meta's plumbing correct first, then our overlay tells you which video, which product tag, which format did the work.

What to actually measure once the plumbing is done

Start with three numbers per widget preset over a 14-day window: view-through rate on the carousel, tagged product click-through rate, and assisted revenue where a shopper touched a video within the session that led to Purchase. Ignore last-click for shoppable video, it will always undersell the format.

Compare against your baseline product page conversion rate for the same SKUs without the widget. On Indian stores we typically see the vertical reel feed lift AOV on apparel and beauty because shoppers add a second tagged product from the same video. Do not chase a universal number. Measure your store, your catalogue, your traffic mix. That is the only ROI figure that matters.

Common questions

Do I still need Meta Pixel if I run Conversions API through Shopify?

Yes, run both. The Facebook & Instagram channel sets up browser pixel plus Conversions API together, and Meta uses event deduplication to avoid double counting. Browser pixel catches signals CAPI misses when a shopper bounces before checkout, and CAPI catches the Purchase event when iOS blocks the browser pixel. Turn on Maximum data sharing in the channel settings so both fire. If you only run CAPI, you lose upper-funnel signal like ViewContent from your beyondRegular widget interactions.

Will installing beyondRegular break my existing Meta Pixel setup?

No. Our embed.js loads async and does not touch your existing pixel code or the Shopify Facebook channel. On Pro we register a separate Shopify web pixel with its own namespace, so Meta's events and ours run in parallel without collision. If you see double Purchase events after adding beyondRegular, the cause is almost always an old hand-installed pixel snippet still sitting in theme.liquid from a previous setup. Remove that, keep the native channel plus our widget, and events line up cleanly.

How long before I can trust the ROI numbers?

Give it 14 days minimum after the pixel is verified clean. Meta's attribution window is 7-day click 1-day view by default, and you need at least two full windows to filter noise from weekend traffic spikes or a single influencer post. For beyondRegular specifically, wait until each widget preset has 500 plus views before reading conversion rate, because small numbers on shoppable video swing hard. Indian D2C stores usually hit that in a week on a homepage bubble, longer on a product page carousel.

Put shoppable video on your store.

7-day free trial. No card needed.

Start free trial