Skip to content
Sayfitech
Affiliate & partner systems

Tracking & attribution

First-party links, codes and coupons with attribution rules enforced in one place.

Engagement
Fixed-scope build, run in parallel with your current tracking
Typical timeline
4–6 weeks
Starts with
One month of orders and the partner claims for the same month, so we can measure the gap.
01The situation

A partner sends a customer who researches for three weeks, clicks a Google ad, then buys. Who earned the commission? Today the answer depends on which report you open.

Why it matters

Every sale credited to one partner, without an argument.

Partner revenue that pays out correctly.

What we build

Concrete artefacts, handed over and documented.

  1. 01

    First-party link tracking on your own domain, so a partner click is not lost to browser restrictions or an ad blocker

  2. 02

    Coupon and code tracking for the sales that never touch a link, phone orders, in person, invoiced deals

  3. 03

    Server-side conversion recording from your billing system, which is the one version of a sale that cannot be spoofed

  4. 04

    A written attribution policy: window length, tie-break order, which touch outranks which, and the named exceptions

  5. 05

    A credit record per sale, showing every touch that was considered and why the winner won

What changes

01

Each sale has exactly one credited partner, with reasoning both sides can read

02

Tracked conversions stop falling short of what your billing system recorded

03

Attribution arguments end at a policy document instead of in a meeting

How it runs

Week 1

01Write the policy

The rules first, in plain language, awkward cases included. A tracking build without an agreed tie-break rule just relocates the argument.

Weeks 2–4

02Instrument

First-party links, codes and server-side conversion recording, reconciled against a month you have already closed.

Weeks 5–6

03Credit records

The per-sale explanation, the partner-visible view, and the report finance uses to sign off a period.

06Typical stack

Chosen per project. Named here so you can see the shape of it.

  • Cloudflare Workers
  • Postgres
  • Stripe
  • Segment
  • Metabase

Questions we get asked

Next step

Tell us the outcome, not the tooling.

Send us the situation you are in. We will tell you which discipline it belongs to, what we would do first and what it costs, including when the answer is to wait.

Start a projectOr email us directlyinfo@sayfi.ai