Getting started

Set up the Vibel pixel

How the Vibel pixel installs on each Shopify store, what it collects, and how to confirm it is working - in orders, not percentages.

What it is, and what it is not

The Vibel pixel is first-party. It runs on your own storefront and reports to Vibel, not to an ad platform. Installing it does not send anything to Meta, Google or Pinterest - that is a separate switch, covered in its own guide, and it is off until you turn it on.

It exists to answer one question no ad platform can answer for you: of the orders you actually got, how many did tracking see? Meta can tell you what Meta saw. It cannot tell you what it missed, because it does not know your order count. Vibel holds both sides.

Good to know

Nothing here changes your storefront's appearance or speed in any way a shopper would notice.
The pixel respects the shopper's consent choice in regions where consent is required.

The two halves, and why both are needed

There are two pieces, and a store can have one without the other. This is the single most common source of confusion, so it is worth understanding before you start.

The THEME pixel reports pageviews and captures the visitor id that links a shopper's sessions together. It is a theme app embed, switched on in your theme editor.

The WEB PIXEL reports add-to-cart, checkout started and purchase. Shopify runs it in its own sandbox, which is the only place that can see the checkout and thank-you pages. A theme embed cannot see checkout at all - that is a platform rule, not a setting.

A store with only the theme pixel will show pageviews and nothing else. If your checkout events are all zero, this is almost always why.

Setting it up

Most of this is automatic when you connect a store. The steps below are for confirming it, and for the cases where a store needs a nudge.

Connect the Shopify store in Vibel, under Settings, Connections. Each store connects separately, so a brand with five country stores has five connections.
Open Events in the sidebar. The top card lists every connected store and when it last sent an event.
If a store says its theme still needs the switch flipped, use its Open theme editor button. That opens Shopify's theme editor with the Vibel pixel already selected: turn it on and hit Save.
In the Checkout signals card, press Register on all stores. This creates the web pixel on each store, which is what makes Shopify start sending checkout and purchase events. It is safe to press more than once.
If a store comes back as needs re-approval, press its Re-approve button. That store was connected before Vibel asked permission to manage web pixels, and only you can grant a new permission - Vibel cannot grant it to itself.
Confirm in Shopify: Settings, then Customer events. You should see an entry called Vibel checkout signals.

Good to know

Registering can be repeated safely. Vibel reads before it writes, so a second press never creates a duplicate pixel - and a duplicate would double every checkout event.
Re-approving changes nothing else about the connection and re-imports no data.

Confirming it actually works

The Events page leads with one number: how many of your real orders tracking captured, out of how many orders actually happened. The denominator is your own Shopify order count from Vibel's ledger, which is why this number can show what tracking MISSED rather than only what it saw.

Give it a day of real traffic. A brand-new pixel has nothing to measure, and a coverage figure computed over three orders is noise.

Place a test order on the store, or wait for a real one.
On Events, check that the captured count went up, and that the day-by-day chart shows a bar for today.
Check the per-store table. A store reading zero coverage while others read high is an install problem on that store, not a pixel problem.

Good to know

POS, draft and app-created orders are excluded from the fraction and counted separately. No pixel can see an order that never had a browser session, so counting those as misses would blame tracking for something it cannot do.
Expect a ceiling below 100 percent. Consent declines and in-app browsers are real losses that no tracking setup recovers.

Your first sync: what to expect

Run your store on Vibel.

Connect your channels, set up your costs, and see true profit live per SKU and per channel.

Get started free

Set up the Vibel pixel

How the Vibel pixel installs on each Shopify store, what it collects, and how to confirm it is working - in orders, not percentages.

What it is, and what it is not

Good to know

Nothing here changes your storefront's appearance or speed in any way a shopper would notice.
The pixel respects the shopper's consent choice in regions where consent is required.

The two halves, and why both are needed

There are two pieces, and a store can have one without the other. This is the single most common source of confusion, so it is worth understanding before you start.

The THEME pixel reports pageviews and captures the visitor id that links a shopper's sessions together. It is a theme app embed, switched on in your theme editor.

A store with only the theme pixel will show pageviews and nothing else. If your checkout events are all zero, this is almost always why.

Setting it up

Most of this is automatic when you connect a store. The steps below are for confirming it, and for the cases where a store needs a nudge.

Connect the Shopify store in Vibel, under Settings, Connections. Each store connects separately, so a brand with five country stores has five connections.
Open Events in the sidebar. The top card lists every connected store and when it last sent an event.
If a store says its theme still needs the switch flipped, use its Open theme editor button. That opens Shopify's theme editor with the Vibel pixel already selected: turn it on and hit Save.
In the Checkout signals card, press Register on all stores. This creates the web pixel on each store, which is what makes Shopify start sending checkout and purchase events. It is safe to press more than once.
If a store comes back as needs re-approval, press its Re-approve button. That store was connected before Vibel asked permission to manage web pixels, and only you can grant a new permission - Vibel cannot grant it to itself.
Confirm in Shopify: Settings, then Customer events. You should see an entry called Vibel checkout signals.

Good to know

Registering can be repeated safely. Vibel reads before it writes, so a second press never creates a duplicate pixel - and a duplicate would double every checkout event.
Re-approving changes nothing else about the connection and re-imports no data.

Confirming it actually works

Give it a day of real traffic. A brand-new pixel has nothing to measure, and a coverage figure computed over three orders is noise.

Place a test order on the store, or wait for a real one.
On Events, check that the captured count went up, and that the day-by-day chart shows a bar for today.
Check the per-store table. A store reading zero coverage while others read high is an install problem on that store, not a pixel problem.

Good to know

POS, draft and app-created orders are excluded from the fraction and counted separately. No pixel can see an order that never had a browser session, so counting those as misses would blame tracking for something it cannot do.
Expect a ceiling below 100 percent. Consent declines and in-app browsers are real losses that no tracking setup recovers.

Run your store on Vibel.

Connect your channels, set up your costs, and see true profit live per SKU and per channel.

Get started free