AnalyticsEvery plan
Meta, TikTok and Snap pixels with server-side events
Meta, TikTok and Snap browser pixels are on every plan and fire only after the visitor accepts the consent banner. They send view, add-to-cart and purchase events. From Growth, server-side conversions send the same events from the server with your own access tokens, so ad platforms still count purchases a browser blocked.
Pixel events
- TikTok — view_item1,840 today
- Snap — add_to_cart312 today
- Meta — purchase (server)96 today
- Consent accepted78%
How it works
How it works
- 1
Add the pixel IDs
Paste the Meta, TikTok and Snap pixel IDs into the shop settings.
- 2
Wait for consent
The pixels stay silent until the visitor accepts the consent banner.
- 3
Events fire in the browser
view_item, add_to_cart and purchase go to each ad platform.
- 4
Add server-side (Growth)
Enter your own Meta, TikTok and Snap access tokens and the same events are also sent from the server.
Configuration
What you can configure
| Setting | What it does |
|---|---|
| Browser pixels | Meta, TikTok and Snap pixel IDs, each set on its own. Every plan. |
| Consent gate | Shared with every pixel on the store. Nothing fires before agreement. |
| Server-side conversions | Meta Conversions API, TikTok Events API and Snap Conversions API. From Growth. |
| Your own access tokens | Server-side events are sent with tokens from your own ad accounts. |
FAQ
Frequently asked questions
Which plan includes pixels and server-side conversions?
Whose access tokens are used?
Do the pixels respect the consent banner?
Can I run TikTok without Meta?
Put this to work in your store today
Get started and turn this on for your store in minutes.
No card required · Live in a day · Support in Arabic and English