Meta Pixel

See which Facebook and Instagram ads bring in sales

Connect your Meta Pixel to your store with an ID and a token. Svippit sends your purchases to Meta, even when the customer pays in the Vipps MobilePay app and comes back in a different browser, and asks your customers for permission first.

Why connect the Meta Pixel?

For many Svippit stores, Facebook and Instagram are the biggest source of visitors. If you spend money on ads there, the pixel is what tells you whether they work.

See what your ads actually sold

See purchases and revenue per campaign in Ads Manager to compare your ads.

Let Meta find your buyers

Purchase events let Meta optimise your ads for sales.

Reach people who looked but did not buy

Show ads to people who viewed a product or added something to their cart without buying.

Built for purchases that happen in the Vipps MobilePay app

A typical customer taps a link in Instagram, pays in the Vipps MobilePay app and comes back in Safari or Chrome. There the browser pixel no longer recognises them, so the purchase is lost. Svippit solves that from the server.

The purchase is sent from the server

With a Conversions API token, Svippit sends the purchase straight to Meta the moment the payment is confirmed, whichever browser the customer ends up in.

Never counted twice

The browser and the server send the purchase with the same ID, so Meta keeps only one. If a send fails, Svippit retries on its own.

Svippit checks that it works

With a token, your settings show when Meta last accepted an event and what Meta said if something went wrong, and a test event shows up in Events Manager right away. Without a token, the time shown is when the pixel last fired in a customer’s browser, as Svippit sees it; whether Meta accepted the event, you see in Events Manager.

How to connect

Connect under Settings, Ad tracking. You do not need to write code.

1

Copy your pixel ID

Open Meta Events Manager and choose Datasets. Copy the ID under your dataset’s name, 15 or 16 digits.

In Meta Events Manager

Datasets in the left menu. The number under the dataset name is your pixel ID.
Datasets in the left menu. The number under the dataset name is your pixel ID.
2

Create a token, recommended

Click the dataset, open the Settings tab and press Generate access token under Conversions API. The token is optional, but it is what catches the purchases made in the Vipps MobilePay app.

In Meta Events Manager

The Settings tab. Scroll down to Set up direct integration and press Generate access token. The option above the button can stay as it is.
The Settings tab. Scroll down to Set up direct integration and press Generate access token. The option above the button can stay as it is.
3

Paste and connect

Paste the ID and the token, tick the box confirming you are responsible for the tracking in your store, and press Connect. The token is stored encrypted and never shown again.

4

Send a test event

This step needs the token. Paste the test code from the Test events tab in Events Manager and press Send. Meta’s answer appears right below the button.

In Meta Events Manager

The Test events tab. Copy the code and paste it into Svippit.
The Test events tab. Copy the code and paste it into Svippit.
When the test works, the event shows up as Processed.
When the test works, the event shows up as Processed.

Your customers decide

Customers choose whether to allow Meta tracking in your store.

Asks for permission, per store

The customer sees a banner naming your store, with Decline and Accept the same size and a link to your store’s privacy page, which names Meta. Nothing is sent to Meta until the customer has said yes in your store specifically.

No banner without a pixel

Stores without a pixel show no cookie banner at all. The pixel loads only on your store’s own pages, never in the dashboard or in other stores.

What Meta receives

The events carry product IDs, quantities, amounts and currency, never product names or descriptions. The browser pixel also sends the page address, and a product page’s address contains the product name. With a token, the purchase sent from the server also carries the customer’s IP address and browser, Meta’s _fbp and _fbc cookie values, and the email address (also as an external ID) and phone number, both hashed. All of it only for customers who said yes.

A privacy page included

Your store gets its own privacy page following the rules of its country, with a section on Meta as soon as the pixel is connected. Customers can change their answer from the Cookies link at the bottom of the storefront, the product pages, the cart and the order confirmation.

Good to know

Meta shows fewer purchases than Svippit

Customers who reject are not tracked, and not every purchase can be matched to an ad. Svippit’s numbers are always the right ones; Meta shows which ads contribute.

Health and wellness

If you sell anything in health, fitness or diet, Meta may restrict what the pixel can be used for. Svippit cannot change this. Check the data source alerts in Events Manager before you spend money on ads.

You are responsible for the tracking

Your store decides that Meta gets data, and you accept Meta’s Business Tools Terms. Svippit handles the consent, the privacy page and sending as little as possible.

Included, at no extra cost

The Meta Pixel is part of Svippit, with nothing added to the price. You only pay for the ads you run with Meta.

Frequently asked questions

Do I need the Conversions API token?

No, but we recommend it. Without a token, Meta only sees purchases where the customer returns to the same browser after paying. With a token, the purchase is sent from the server, so Meta hears about far more of your sales.

Which events are sent to Meta?

The five standard events: page view, view content, add to cart, initiate checkout and purchase. The standard names mean Ads Manager understands them without any setup.

Why does Meta say 3 sales when Svippit says 11?

Customers who reject cookies are not tracked, and some purchases cannot be matched to an ad. That is normal. Use Meta to compare your ads with each other, and Svippit to see what you actually sold.

Can I paste in my own tracking script?

No. Arbitrary script on svippit.com would be a security risk for every store and for the checkout. That is why Meta is built in as its own setting, with consent and privacy already handled.

What happens if the customer rejects?

Then nothing is sent to Meta for that customer, from neither the browser nor the server. They shop exactly as before.

What happens if I disconnect?

Your store stops sending events to Meta immediately, and the token is deleted. The banner disappears from your store. You can connect again whenever you like.

Does it work in Denmark and Finland?

Yes. The banner and the privacy page follow the language and the rules of the country your store is registered in.

Questions about setup? Write to hello@svippit.com.

Create your online store

Add products and apply for Vipps MobilePay from your account.

No credit card required.