For teams whose customers cross a boundary they don’t own

Attribution that survives the boundary.

Cryptographic, fraud-protected attribution at the edges where every other analytics tool goes dark.

One click, captured up to the boundary
Visibility zone Off-site zone
The problem 10–30% · industry stat

You’re paying for clicks. 10–30% are bots. The rest disappear the moment they leave your domain. We pick up where everyone else stops.

02 · What we capture / what we don’t Honesty over hype

We won’t pretend. The dark zone starts wherever your customer crosses onto a surface you don’t own — and that’s where every analytics tool, ours included, goes dark.

Here’s the bargain in two columns. The left side is yours to own. The right side belongs to whoever runs the boundary — a retailer, an app store, a merchant checkout, a partner site. Nobody who sells you “full-funnel” coverage actually has it.

Quantum Visibility Zone
Yours to own
  • Every click in, signed and verified
    TUID minted on issue · HMAC validated on receipt
  • Branded shortlink → site landing
    go.your-brand.com → www.your-brand.com
  • Anonymous identity across your own domains
    before login, with a single-use audience-bound token
  • On-site behavior — pages, scroll depth, dwell
    first-party tracker on a domain you control
  • The verified outbound click
    the strongest intent signal you actually own
  • Fraud verdict per click — human / bot / replay
    rejected at the signature, not after the fact
Off-Site Zone
Nobody sees this
  • Whatever happens after the boundary
    retailer / app store / merchant / partner site
  • In-app or in-checkout behavior
    never leaves their surface
  • Off-site coupons, pricing changes, OOS
    no shared infrastructure with Quantum
  • Off-site search, ranking, or product detail data
    requires the other side’s own API
  • Cross-device journeys you can’t script either side of
    we won’t pretend we see this
  • What a logged-in user does inside someone else’s app
    no third party should see this
03 · What’s different Three things, not thirty

Wherever other tools leak signal, we sign it.

01

Cryptographic fraud protection

Every click is a signed TUID. Bots can’t forge them.
Format is uuid.timestamp.HMAC-SHA256 — the signature is validated on every event the tracker fires. Replays fail on nonce; forgeries fail on signature.
10–30% of influencer spend bleeds to bots · industry stat
02

Anonymous cross-domain identity

Stitch a visitor across your domains — before they log in.
Identity hands off via a single-use, audience-bound HMAC token with a 10-minute TTL. Works before the user logs in — most cross-domain stitching can only happen after authentication.
10 min TTL · single-use · audience-bound nonce
03

First-party tracker and links

No third-party pixel. The browser sees your brand.
The tracker JS bundle and the shortlink redirect both run on a domain you control — or our shared qtrk.link if you don’t have one. Ad blockers see a request to you, not to a known analytics vendor.
0 third-party pixels added · ad-blocker friendly
04 · Where this pattern shows up Same mechanism, different boundary

The mechanism is unified. The boundary changes.

Signed clicks, anonymous cross-domain identity, first-party tracking. Whether the wall is a retailer’s domain, an app store, a merchant’s checkout, or a partner site — the shape of the answer is the same.

Affiliate / Performance → Merchant 02 / 03

Paid placement → branded redirect → merchant checkout click.

Stop paying per click when 10–30% of clicks are bots. Every click carries a signed TUID; the fraud verdict happens at the signature, not in a weekly clawback report.

Signed TUIDs Replay-proof Fraud at the signature
Multi-domain DTC → Owned ecosystem 03 / 03

Campaign microsite → main brand → product → outbound.

Stitch a visitor across all your owned domains — before they log in — with a single-use, audience-bound HMAC handoff. The cross-domain story is the headline here.

Pre-login identity Audience-bound nonce 10-min TTL
05 · A real journey Example: a CPG journey · same pattern elsewhere

One shopper. One signed identity. Until the boundary.

One instance of the pattern from the previous section — a CPG journey, Instagram to retailer click-out. Swap the boundary and the diagram still reads: lit on your side, dark on theirs.

“The last click before they leave is the strongest intent signal you’ll ever own.”
Day 1
Tuesday · 7:42pm

Branded shortlink tap

A creator drops a recipe Reel with go.your-brand.com/quick-pasta. Tap → 302 to your site. We mint TUID 7f3c…b81e, signed and stamped with the campaign slug.

Campaign A Mobile · iOS go.your-brand.com
Day 1
Tuesday · 7:43pm

Lands on recipes

Same TUID, now on www.your-brand.com. The cross-domain handoff is an audience-bound nonce — no login, no cookie hop, no third-party request. Reads two recipes, leaves.

www.your-brand.com 2 pageviews no login
Day 3
Thursday · 12:18pm

Direct return visit

Same browser, same TUID. No referrer this time — just navigates back to the recipe. Stays 4 min. The intent is building; we can already see it.

direct 4m 12s TUID rebound
Day 7
Monday · 9:06pm

Outbound: “Buy at Walmart”

Click on the retailer button — the click-out event fires, TUID still attached. This is the strongest purchase-intent signal you will ever capture. Campaign A gets credit, verified and signed.

CLICK-OUT Campaign A walmart.com
Day 7+
After the click

walmart.com

We don’t see this — and we won’t pretend we do. The retailer’s domain is sealed, and that’s the honest end of the journey.

no tracker no off-site data unknowable
06 · What you get out of the box Real software, deeply built

Twelve things, already shipped.

The narrative sells why we’re different. This is what’s actually in the box. No roadmap items, no asterisks — all available in the workspace on day one.

Branded shortlinks

Your own domain. go.your-brand.com/summer-launch — or qtrk.link while you set up DNS.

QR codes

Generated in-app, downloadable as SVG/PNG, optional center logo.

Geo routing

One shortlink, different destination per country. US → A, UK → B, default → C.

A/B testing

Weighted destination variants, sticky per visitor — same TUID always lands on the same arm.

Link expiry

Set expires_at per link; the worker hard-stops at expiry.

Click limits

max_uses per link, atomically enforced via D1 counters.

Passcode links

Gate any shortlink behind a passcode. Useful for unreleased landing pages.

White-label

Run shortlinks under the client’s domain via Cloudflare for SaaS — fully white-labeled.

Goals & funnels

Define an ordered event sequence; the admin shows step conversion and drop-off.

Realtime stream

SSE direct from our edge to your browser. No polling, no hop — used by the live dashboard.

Outbound webhooks

Push every event (or just goal completions) to your endpoint with retry + signing.

Audit log

Every workspace mutation recorded with actor, before/after, and metadata.

07 · How it ships Two script tags

Deploys in an afternoon, not a quarter.

One write key, one tracker URL. The tracker is served from a domain you control — drop it in the same place you put your other site scripts and you’re done.

index.html · <head>
<script>
  window.__QA_WRITE_KEY = "pk_live_…";
</script>
<script src="https://analytics.your-brand.com/qtrk.js" async></script>

// That's it.
Annotations
Line 2 Your write key from your workspace settings
Line 4 Your branded shortlink domain or shared qtrk.link if you don’t have one
Line 4 Canonical path /qtrk.js — /go.js is a deprecated alias, ignore it
✓ No tag manager required ✓ No third-party domain ✓ No PII in transit ✓ Runs on Cloudflare edge
08 · Where we’re not the right fit Honesty about scope, not a competitor swipe

Three plain-language sentences, so we don’t waste each other’s time.

If you need a 200-integration tag manager,
→ THEN
we’re not that.
If you need to track what happens inside someone else’s checkout,
→ THEN
nobody can — and we won’t pretend we can.
If you need white-glove implementation services and a named account team,
→ THEN
we’re self-serve.

Own everything that happens before the boundary.

A 30-minute call on your domains, your top channels, and what a first-party tracker on a domain you own would look like.

Thanks — message received.

We'll be in touch within a business day.

Typical setup one afternoon
Tracker domain your brand
Data residency your Cloudflare or ours