Creator-commerce attribution architecture

This whitepaper describes how cyrqle implements creator-commerce attribution as a first- party system: how the on-page tag stays under 2KB gzipped, how QR codes and promo codes join back to the same creator ID, how the order-data reconciliation runs, and how cohort forward-joins are computed at 30/60/90 days.

What's inside

• The tag — how it stays under 2KB, what events it captures, what it deliberately doesn't.
• The URL convention — creator ID + cluster ID + campaign ID encoding, including the hash routing and link-shortener pattern.
• The QR pipeline — how per-creator QR codes are provisioned, where they route, how they reconcile.
• The promo pipeline — Shopify, BigCommerce, and custom-cart integration shapes; how to handle code sharing and abuse mitigation.
• The reconciliation job — order-data join, dedup logic across surfaces, dispute workflow.
• The cohort forward-join — how 30/60/90-day repeat behavior is computed without losing creator ID.

Who this is for

Eng leads at brands and retailers building or evaluating creator-commerce attribution; ops leads who want to understand what the platform does under the hood; consultants who need a canonical reference to point clients at.

Why we publish this

Attribution that nobody understands is attribution nobody trusts. The architecture is in the open so the numbers can be audited.