Tracking conversions with the pixel
The conversion pixel tells you what happened after someone clicked one of your short links, things Styrar can't see on its own, like a purchase, a signup, or a booking completed on a page you don't control (a storefront, a landing page builder, a partner's site).
Use it together with link A/B tests: clicks alone only tell you which variant got more traffic. The pixel tells you which variant actually converted.
When to use it
- You're running an A/B test on a short link and want to know which destination page actually drove results, not just clicks.
- Your destination page lives outside Styrar (Shopify, WordPress, Wix, Framer, a custom site) and you want conversions credited back to the right link and variant.
- You want to attach a value to a conversion, such as order revenue, so reporting reflects more than a raw count.
Setting it up
- Open the link's Advanced → A/B test panel and configure or start an experiment.
- Copy the embed snippet from the "Track conversions on the destination page" card.
- Paste the snippet into the destination page, the same page visitors land on after the short link redirects them. This works regardless of what platform hosts the page.
- Mark a conversion, either by adding the snippet's tracking attribute to a button or form, or by calling it from your own code when something worth counting happens.
There's nothing else to configure, no account ID, site ID, or API key. The pixel automatically recognizes which click sent the visitor to your page.
Reading the results
Once the pixel is live, open the link's A/B test panel to see conversions and conversion rate per variant. Promote the winning variant when you're ready, the same way you would based on click data alone.
Platform guides
Exact installation steps vary slightly by platform. See the developer documentation for step-by-step setup:
- Conversion pixel overview — how it works and the full API reference.
- Shopify — install via a Custom Pixel.
- WordPress — with or without a plugin.
- Wix — via Custom Code, with or without Velo.
- Framer — via Custom Code.
- Server-side reporting — report a conversion from your own backend in Node.js, Python, or Ruby on Rails when it happens outside the browser.
Bio page trackers are separate
The conversion pixel is for short link destinations. If you want general analytics or ad pixels (Google Analytics, Meta, Google Tag Manager, and similar) running on your bio page itself, that's configured separately and gated behind cookie consent. See Bio page trackers in the developer docs.
Privacy and limits
- The pixel only sends the click token, the event name and value you choose to send, and the current page URL, no cookies, fingerprinting, or cross-site identifiers.
- Conversion tracking requires an A/B test configured on the link, conversions attribute to whichever variant the visitor saw at click time.
- There's no automatic pageview tracking. The pixel only reports events you explicitly trigger, to keep things lightweight on the destination page.
Need more help?
Open a ticket from Help → Tickets (sign in required).