Click + signup attribution
Per-creator clicks, signups, and cost-per-customer for any campaign — works for SaaS funnels, software trials, or anything you fire as a conversion event.
What it does
Every offered contract gets a short redirect URL — proofapp.net/r/<slug>. The creator shares that link in their post, bio, or boosted ad. Every click goes through PROOF before bouncing the visitor to your site, and we log who came from which creator. When the visitor signs up, your thank-you page fires a conversion event back to PROOF — and you see per-creator clicks, signups, and cost-per-customer on the campaign Efficiency tab.
Built for SaaS-style funnels
Unlike the Shopify integration (which attributes via per-creator discount codes for physical goods), click tracking works when there's no discount code — software signups, free trials, lead-gen forms, demo requests. Anything you can fire as a Pixel event, PROOF can attribute back to the creator.
How attribution flows
Creator shares the redirect link
PROOF mints a unique slug per contract (e.g. sarah-fitlife-c8a1). The creator pastes proofapp.net/r/sarah-fitlife-c8a1 into their Instagram bio, TikTok caption, YouTube description, or boosted Meta ad.
Visitor clicks → logged → bounced to your site
PROOF's redirect handler logs the click with country, referrer, optional Meta ad-ID, then 302s to your landing page with proof_cid + UTMs appended. Hashed IP and user-agent are stored; raw values are not.
Your snippet captures the proof_cid
A 4-line JS snippet on your site reads the proof_cid query param on the first page load and persists it (localStorage + first-party cookie). It survives multi-step funnels — signup → email confirm → first login can all be one attributed customer.
On conversion, snippet posts back to PROOF
When your user signs up, starts a trial, or completes any conversion event you care about, the snippet fires POST /v1/conversions with the proof_cid + event_type. PROOF correlates back to the creator's contract and records the conversion.
(Optional) PROOF mirrors to Meta CAPI
If you've connected your Meta Pixel + Conversions API token, PROOF dual-sends every conversion server-side. Meta dedupes with your browser Pixel via the shared event_id. iOS conversions that ATT would have eaten get recovered.
Setting it up (one-time)
Go to /brand/integrations/tracking. Three things to do:
- 1Generate a signing secret — you'll see it once; copy into your snippet.
- 2Drop the 4-line JS snippet on your signup-success / thank-you / order-complete page. Substitute your brand_id + signing_secret values.
- 3(Optional) Paste your Meta Pixel ID + CAPI access token to enable iOS conversion recovery. The token is AES-256-GCM-encrypted at rest.
No per-contract setup
Every offered contract automatically gets a redirect URL. You don't tag campaigns, you don't ask creators to remember UTMs. PROOF handles it.
Viewing the breakdown
Open any campaign and view the Efficiency tab. The Attribution card shows totals (clicks · signups · revenue · cost-per-customer) and a per-creator breakdown table. Switch the conversion event from the dropdown — count trial-starts, signups, subscriptions, purchases, or leads depending on your funnel.
Privacy posture
- Raw IP and user-agent are never persisted — only BLAKE3 hashes with a monthly-rotating salt for fraud-dedup.
- PII-shaped brand_user_id values (emails, phone numbers) are hashed before storage if your snippet sends them raw.
- Cookie is first-party on YOUR domain (your snippet sets it), not a PROOF third-party cookie — survives Safari ITP's 7-day cap.
- Optional: CNAME a subdomain (e.g. track.brand.com) to PROOF's edge so the redirect itself looks first-party.
Meta Conversions API (recommended)
iOS 14+ App Tracking Transparency blocks the Meta Pixel for ~75% of iOS visitors. Meta's official recovery is server-side CAPI: your browser Pixel still fires for consenting visitors, and PROOF mirrors the same event server-side via the Conversions API with a matching event_id. Meta dedupes within a 48-hour window. Match rates jump from ~25% to ~95% on iOS.
To enable: in Meta Events Manager, go to your Pixel → Settings → Conversions API → Generate access token. Paste both the Pixel ID and the access token into /brand/integrations/tracking. PROOF starts mirroring every conversion automatically.