Skip to content
Newv6.18.0Generated values for buyer deliveries, a safer Google Sheet connection, and a post log filter step that explains itself.Read the changelog
For affiliate networks

Many publishers, one system, nobody chasing you for numbers.

Per-source attribution, caps and filters that catch bad traffic before a buyer does, and a partner login so affiliates read their own numbers instead of asking you for them.

Start Free Trial
Book a Demo
Per-source payouts
Self-serve postbacks
Partner logins
Click tracking overview with clicks, conversions, EPC and revenue per traffic source
The problem

Sound familiar?

A network breaks in three places: visibility, quality, and money.

Publishers email you for numbers

They want to know what converted, what got rejected, and what they earned. You answer the same question all week, by hand, one affiliate at a time.

One bad publisher costs you a buyer

Quality slips on one source, the buyer starts rejecting, and the damage lands on the whole network. By the time it shows up in the totals the relationship is already strained.

Payouts get reconciled by spreadsheet

What the buyer accepted, what came back as a return, what each affiliate is actually owed. Three sources of truth and a month-end that eats a day.

How Datahubb helps

Run the network, not the admin

Every publisher is its own traffic source

Affiliates point at one hosted page and are told apart by the traffic source they post with. Payout, caps, filters, and reporting all hang off that record — so per-affiliate numbers are structural, not something you rebuild from a sub-ID afterwards.

Postbacks your affiliates author themselves

A traffic source builds their own postback configs: the events they fire on, the tokens in the URL, form or JSON bodies, HMAC signing. They can point their own Meta pixel at their leads through the CAPI preset. You stop hand-crafting a URL per affiliate.

Caps and filters before the damage

Daily, weekly, and monthly volume and budget caps per traffic source, plus filters at traffic-source level — a level above supplier. A source that starts sending rubbish is stopped at the door, not in the month-end review.

Quality visible per source, not in aggregate

Rejections grouped by reason, each with the revenue estimated to be at stake — lost leads multiplied by what a lead actually sold for, times the rate at which rejected leads still went on to sell. Filterable down to a traffic source, an affiliate ID, or a sub-source.

Partner portals

The report your publishers stop asking for

Give a traffic source their own login and they see their own clicks, their own conversions, and what they earned — live, and only theirs. The weekly email asking for a breakdown stops arriving, and nobody has to export anything.

  • Each partner sees their own traffic and nothing else
  • Live numbers, not a spreadsheet you sent on Monday
  • They wire their own postbacks and their own pixel
Buyer portal showing the leads a buyer purchased, with bid settings and return requests
What it looks like day to day

Add a publisher without adding a process

Add a publisher as a traffic source with its own payout, caps, and filters
Give them a login so they read their own clicks, conversions, and earnings
Let them wire their own postbacks and their own pixel without raising a ticket
Close the month off accepted, rejected, and returned records rather than a spreadsheet
FAQ

Frequently asked questions

Affiliates post against a shared internal supplier page and send a traffic source value with each lead. That resolves to a traffic source record, and the record is what carries the payout, the caps, and the filters. Reporting, postbacks, and payouts all read that same attribution.

No. Traffic source users author their own postback configs — the events they fire on, the tokens, the body, the signing secret — scoped to themselves and to the campaigns they have access to. They can also attach their own Meta pixel through the CAPI preset, which handles the hashing and the fire. See conversions and postbacks.

No. A traffic source sees their own configs and the campaigns assigned to them, and nothing else. Buyer names, revenue, and profit are admin-only — not hidden in the interface, but refused by the server, so a stale page or a hand-crafted request gets no further than a correct one would.

Rejections are grouped by reason with the estimated revenue at stake against each, and the list filters down to a single traffic source, affiliate ID, or sub-source. That turns “this publisher is underperforming” into “this publisher keeps failing the duplicate check”. See rejection insights.
Further reading

More for affiliate networks

Give your publishers their own numbers.

Start your 14-day trial. Full platform access. Card required, no charge if you cancel during the trial.

Start Free Trial
Book a Demo