Verify

Cross-Browser Attribution Tester

Some commissions disappear in Firefox but not Chrome. Some links route EU visitors to a lower-rate marketplace. Some mobile links bypass your tag entirely when the native shopping app opens. The Cross-Browser Tester runs your link across three real browser engines and two geographic regions in parallel, compares every result, and tells you where attribution breaks and which audiences it affects.

Join the beta →

What it does

Runs your link through three real browser engines, Chromium, WebKit, and Firefox, simultaneously, each in a clean session. Chromium represents Chrome and most Android browsers. WebKit represents iOS Safari, the most ITP-restricted environment. Firefox represents privacy-focused users with Enhanced Tracking Protection active.
Checks whether visitors from the EU land on a different marketplace or a lower commission rate than your US audience. A geo-redirect that silently changes the destination can mean your non-US traffic earns nothing, or earns at a different rate, with no visible indication.
Verifies whether mobile visitors who open the native shopping app still carry your tag through the deep link. The LTK documentation acknowledges cookies do not transfer between Instagram's in-app browser and Safari. This tester detects that failure and quantifies it.
Reports a confidence range for any dollar-loss estimate, never a single number. Quantification depends on audience demographic data that carries real uncertainty; a range is honest and legally defensible in a way a fabricated precise figure is not.

How it works

01
We orchestrate the engines
Three real browser engines and two geographic vantage points run simultaneously against your link. The ITP simulation harness advances virtual time past the 7-day mark in WebKit to confirm whether the cookie survives the cap or expires before your conversion window closes.
02
We compare the deltas
When engines disagree on the final URL, the cookie that sets, or the deep-link outcome, the disagreement is the finding. A link that works in Chromium but loses the cookie in WebKit is a real attribution gap, not an edge case.
03
You get a quantified risk report
The iOS Attribution Audit translates browser findings into a dollar-range estimate, using your audience iOS percentage and your historical conversion data from the Dashboard. The evidence packet attaches to dispute letters automatically.

What you’ll see

Cross-Browser Tester

This is where your links appear after a scan: graded, annotated, and ready to act on. Join the beta list to see your own results here when it opens.

Is your link paying out across every browser?

The Cross-Browser Tester ships as part of the full product. Leave your details and we will notify you when multi-engine testing goes live.

Related features

Hijack Exposure Score

Per-link risk grade. Honey-class cookie hijack, scored and cited.

Link Chain Analyzer

Find the exact hop where your commission tag goes missing.

Cookie Validator

See how Safari actually handles your cookie, and what that costs you.

Beta

See this feature applied to your own links.

VigiLink is in active development. Join the beta list and we will reach out when the Cross-Browser Tester opens, so you can see where attribution breaks across all three engines.

Join the beta →

Cross-Browser Attribution Tester

Join the beta →