Understanding Polar Pixel & Attribution

Last updated: October 23, 2026

This article explains what the Polar Pixel is, how it tracks attribution, and what you need in place to get accurate results.

New to the Pixel? Start with Using the Polar Pixel: Complete Installation & Tracking Setup Guide.

What is the Polar Pixel?

The Polar Pixel is a first-party, server-side tracking solution for Shopify merchants. It captures customer journeys directly from your store, which helps you recover visibility lost to iOS 14+ restrictions and ad blockers.

No third-party cookies: it doesn't rely on third-party cookies, so it's resilient to browser updates and privacy settings.
Unified customer journeys: every visitor gets a unique Lifetime ID. If a customer clicks a Facebook ad on Monday and returns through Google Search on Friday to buy, Polar connects both visits into one journey.
Shopify App Pixel: on Shopify, the Pixel runs in an isolated, secure environment with no impact on site speed.

Availability

The Polar Pixel isn't available on the Free Trial. The Pixel needs about two weeks of tracking before its data is reliable, so there wouldn't be enough time to evaluate it during a trial.

Why Polar Pixel numbers differ from your ad platforms

It's normal to see different numbers in Polar than in Meta Ads Manager or Google Ads. Each ad platform only sees its own interactions and applies its own attribution window, so if a customer clicks a Facebook ad and then a Google ad before buying, both platforms may claim the full sale.

The Polar Pixel sees the whole journey, so each sale is counted once and credit is assigned according to the attribution model you choose. For example, under First Click, if Facebook was a middle touchpoint rather than the first, it receives no credit for that order in Polar, even though Facebook's own reporting may count it.

For more detail, see Troubleshooting Data Differences Between Polar and Your Ad Platform.

Attribution models and settings

Polar Pixel metrics use the First Click model by default, with an all-time lookback window. You can switch models and adjust settings in your Acquisition reports and custom tables to see your data through different lenses.

Understanding Attribution Models covers every model and when to use it.
Understanding Attribution Settings covers Is Paid Only, the lookback window, and Cash vs. Accrual.

Tracking parameters

The Pixel can only attribute conversions to campaigns whose ads are tagged correctly. The Pixel still fires without them, but untagged campaigns may show up as Direct or Organic, leaving gaps in your reporting.

Purpose	Parameter	Description
Attribution	`utm_source` (required)	The platform (e.g., `facebook`, `google`).
	`utm_campaign` (required)	The specific campaign name.
	`campaign_id` (recommended)	The unique numeric ID from the ad platform.
	`ad_id`	Identifier for individual Meta ads.
	`utm_medium` / `utm_term`	Identifies ad type or search keywords.
Optimization	`gclid` / `fbclid` / `ttclid`	Click IDs used to sync conversion data back to platforms.

Tip: name matching. Polar matches campaigns by name. If your campaign is called "PMax Direct," utm_campaign=pmax_direct will match. An abbreviation like utm_campaign=PM won't.

Set up parameters for each platform you use:

Keeping your attribution healthy

Your Attribution Rate is the percentage of orders linked to a marketing source. Aim for 85% or higher. Having 15–20% of orders show as Undefined is normal, since some visits come from ad blockers or direct traffic. If Undefined is consistently higher than that, check your tracking parameters first.

Tag every ad. Consistent UTMs are the single biggest factor in your attribution rate.
Allow two weeks. The Pixel doesn't track retroactively and needs about two weeks of data to build a complete picture of your customer journeys.

See Understanding and Improving Your Polar Pixel Attribution Rate for a step-by-step guide.

Watch a quick walkthrough of how to view this data:

Troubleshooting

If the Pixel isn't firing or your attribution looks stuck, the most common cause is a cookie consent banner blocking the script. See Troubleshooting Low Attribution: The Impact of Cookie Banners on Polar Pixel.

Headless Shopify stores: make sure the Polar Pixel script is allowed in your Content Security Policy (CSP) headers. For installation on a headless store, see the Polar Pixel SDK documentation.

Common questions

How long does it take for data to load after I install the Pixel?

Attribution data starts coming through the day after installation, then refreshes hourly or daily depending on your plan.

Can I see where the first touch came from for past sales?

No. The Pixel isn't retroactive, so it can only see touchpoints from the moment it was installed.

Why use the Polar Pixel instead of Google Analytics?

Polar pulls first-party data along with campaign, ad set and ad data from the major ad platform APIs. It also uses server-side cookies and identity resolution to unify visitors across sessions and devices. If one person visits from Google Search and later through a Facebook ad, Polar tracks both as one journey.

How can I check that my attribution is accurate?

Place a few test orders through tagged links and confirm they're attributed as expected. If you'd like help reviewing your setup, reach out through the in-app chat.

What's the difference between live Polar Pixel data and Polar Pixel conversions?

Live Polar Pixel data is for monitoring conversions in real time. It covers the last 72 hours and has no attribution applied. Polar Pixel conversions and other Pixel metrics are the same data with attribution and full history included.

Why do totals differ slightly between attribution models?

Small differences between models, especially Linear and other multi-touch models, come from rounding at high precision. These variations are expected. For how each model assigns credit, see Understanding Attribution Models.

How does the Pixel handle bot traffic?

Polar flags likely bot sessions and events with the Is Bot Session dimension, but doesn't filter them out automatically. See Excluding bot traffic from Polar Pixel data.