Traffic sources for affiliates

This article explains traffic sources for affiliates under an internal supplier. Use it when you host the page in your program and need per-affiliate tracking, payouts, or postbacks.

A traffic source is not a second API key. Affiliates post through the supplier credentials and identify their channel as shown in the supplier's in-app API documentation.

What is a traffic source?

A traffic source is an affiliate channel tied to an Internal supplier's shared page. It lets Datahubb attribute leads, apply affiliate payouts, and send outcome postbacks per channel.

External suppliers usually do not use Datahubb traffic sources. Those publishers manage channels on their own platforms.

Prerequisites

• A campaign with an Internal supplier already created
• Affiliate contacts who will drive traffic to your page
• Clarity on payout expectations per affiliate

Add traffic sources

1. Go to Campaigns and open the campaign.
2. Confirm Suppliers has an active Internal supplier.
3. Open the Traffic Sources tab.
4. Optionally click Add Page if you need a campaign page record for affiliates.
5. Click Add Traffic Source.
6. Select the traffic source user or publisher the form asks for.
7. Set payout type and any payout fields shown.
8. Set traffic channel and timezone if available.
9. Add volume or budget caps only if you already know limits.
10. Click Save.
11. Open the traffic source and note the channel identifier the UI provides for that affiliate.
12. Share with the affiliate:
    • Supplier credentials copied from the supplier page
    • Their traffic source identifier
    • A pointer to the supplier's in-app API documentation for examples
13. Remind them that the traffic source identifier is not a replacement API key.

How tracking fits together

If affiliates omit the traffic source identifier, leads may still ingest under the supplier but lose clean affiliate breakdowns. Exact field names and examples belong in the in-app API docs, not in this article.

Tips and gotchas

• Create the internal supplier before traffic sources. The shared page model depends on it.
• Do not create an external supplier when what you really need is affiliate tracking in Datahubb.
• Caps on traffic sources can stop one affiliate without pausing the whole supplier.
• For postback customization at campaign level, see Campaign postback overrides.
• Keep affiliate credential distribution private and per partner.

Expected result

Each affiliate appears on Traffic Sources, posts through the internal supplier credentials, and shows up as a distinct channel in leads and analytics when they send their traffic source identifier correctly.

Frequently asked questions

Is a traffic source a separate supplier? No. It is a channel under an internal supplier. One supplier credential set, many traffic sources.

Do external publishers need traffic sources? Usually no. Use External on the supplier and let them manage channels outside Datahubb.

Where do affiliates get API examples? From the supplier's in-app API documentation. Copy credentials from the supplier page.

Why are all leads lumped under the supplier with no affiliate split? The posts may be missing the traffic source identifier, or the supplier may be external. Verify both.

Can traffic sources have their own filters? Yes. Campaign filters support a traffic source level. See Campaign filters.

How do postbacks relate to suppliers? Outcome postbacks are a traffic source concern for internal affiliate setups. Suppliers get the immediate ingest response when they post. Configure postbacks on the traffic source or campaign postback settings your workspace provides.

Related articles

• Add a supplier and connect traffic
• Campaign postback overrides
• Key concepts: campaigns, buyers, and suppliers
• Dashboard and analytics