The Advertiser's Checklist for Vetting an Affiliate Network

2026-05-29

You are buying calls or leads. You are also buying the network's compliance posture, because in the U.S. an advertiser can be held liable for what its publishers do under the TCPA. So the evaluation is two questions at once: will this traffic convert, and will it create regulatory exposure?

Here is what to ask for, and what should make you walk.

Traffic Source Transparency

You should know where every call and lead originates. Not "social" or "search" — the actual source down to sub-ID and publisher.

Ask:

• Can you see source-level and sub-ID data, not just aggregate campaign numbers?
• Can you run separate tracking links per traffic source so you can isolate a bad publisher without killing the whole campaign?
• Are display URLs, ad creatives, and landing pages available for review on request?

A network that can only show you blended performance is hiding the parts that hurt you. Insist on per-publisher visibility before you spend a dollar.

Publisher Vetting

Networks that auto-approve affiliates are the ones fraud rings target. Ask how they recruit and onboard:

• Manual application review, website quality checks, identity verification?
• New publishers started on lower caps and slower payout terms, with caps raised only after a proven traffic period?
• Do they participate in industry fraud-sharing lists (shared spreadsheets of known bad actors in pay-per-call)?

Ask to review the affiliate terms the network makes publishers sign. They are usually public — click the "sign up as affiliate" link. Read what behavior is actually prohibited.

Compliance Handling

This is where advertiser liability lives. The TCPA requires prior express written consent that names one identified seller, ties the call to the interaction that produced the consent, and lists the number being contacted. Violations run $500 to $1,500 each, and they add up per call.

Require:

• Consent capture and proof. TrustedForm or Jornaya certificates (or equivalent) on every lead, retrievable on demand.
• Consent validation tooling that filters non-consented or mismatched records before they reach your call center.
• DNC scrubbing against federal and state Do-Not-Call lists.
• Suppression handling. Your suppression list honored across all publishers, with a defined update cadence.
• One-seller consent language that names your brand, not a generic "marketing partners" clause that won't hold up.

If the network treats consent as your problem, the liability is still yours and the protection is gone.

Lead and Call Quality Controls

Volume is not the metric. Billable, qualified conversions are. Pin down the rules in writing before launch.

For calls:

• Billable duration / connect threshold — at what call length does a call become billable (commonly 60–120 seconds, but get the exact number).
• Duplicate window — same caller inside X hours/days does not bill twice.
• IVR / buffer filtering to screen out misdials and non-intent before the call routes to you.
• Return / dispute policy — how you flag bad calls, the window to do it, and how credits are issued.
• QA process — call recordings available, and the network listening to new-publisher calls daily.

For leads:

• Real-time field validation (phone, email, address), duplicate dedup window, and a defined return policy for invalid or out-of-criteria leads.

Get every threshold as a number in the IO. "High quality" is not a spec.

Source-Level Reporting and Tracking

You need a tracking stack you can read independently. Ringba, Invoca, Everflow, and Phonexa are the common ones; the platform matters less than the access.

Confirm:

• Real-time reporting, not next-day batch.
• Source/sub-ID breakouts of calls, billable calls, duration, and conversion.
• Postback or pixel integration into your own CRM or attribution so you are not reading only the network's dashboard.
• Call recordings and lead detail tied to the originating publisher.

If reporting only lives inside their UI with no export and no per-source view, you cannot diagnose quality problems, and you cannot prove fraud.

Test Caps Before Scale

A good network expects you to test small. Start with a daily cap, measure billable conversions and disposition data, then raise the cap. Any network pushing you to commit to large volume before a controlled test is optimizing for their invoice, not your close rate.

Dedicated Account Management

You should have a named person who provides written campaign rules (insertion order plus addendums listing what is and isn't allowed), responds to quality disputes, and can pause or block a specific publisher on request. A shared inbox and a self-serve dashboard is not account management.

Payout and Commercial Terms

Get the model and the mechanics in writing:

• Model: CPA, CPL, CPC, pay-per-call, or hybrid — and exactly what triggers a billable event.
• Billable definition for that model (the duration, the qualified-lead criteria, the duplicate rules above).
• Net payment terms and how disputes/credits apply against an invoice.
• Return reconciliation — how flagged bad traffic is netted out.

Ambiguity here is where margin disappears.

Fraud Protection

Beyond vetting, ask what runs continuously:

• IP/device checks and tools like IPQualityScore or Anura on inbound traffic.
• Alerts on the standard signals: high clicks with zero conversions, repeated clicks from one IP, traffic from unexpected geos, abnormally short sessions, robocall-pattern call spikes.
• Documented action when a publisher trips those signals — paused and investigated, not paid first.

Red Flags

Walk away, or test very small, if you see:

• No source-level or sub-ID reporting; aggregate numbers only.
• Auto-approval of publishers and no documented vetting.
• Consent and DNC framed as entirely your responsibility, no consent certificates.
• No written billable definition, duplicate window, or return policy.
• Pressure to scale before a capped test.
• No call recordings or no export of your own data.
• Vague answers about traffic sources, or refusal to name publishers behind specific calls.

The Short Version

A network worth working with sells you visibility and control, not just volume. You should see every source, hold proof of consent, dispute bad traffic against written rules, and grow the cap on your timeline. If any of those is missing, the gap becomes your liability and your wasted spend — not theirs.