Publisher applications for compliant lead sources.

aventia Performance works with lead sources that can document where inquiries came from, how consent was captured, and what category and location the customer requested.

Apply as a publisher

Publisher intake

Source and consent details required

Source

URL, campaign, traffic type

Consent

Proof and timestamp required

Quality

Duplicates and disputes monitored

Payment

Custom terms in dashboard

Meta Ads traffic is not accepted.

Accepted formats

Calls + web leads

Proof standard

Source + consent records

Payment model

Terms by account

Publisher review path

Traffic needs a source record before it moves.

Publisher traffic must be traceable enough to understand the source, consent path, category, and location behind each inquiry.

Source review

URL and traffic type

Consent record

Timestamp and evidence

Quality watch

Duplicates and disputes

Custom terms

Dashboard payment setup

Meta Ads

Not accepted

Proof

Required

Terms

Custom

Publisher requirements

Publishers must be able to identify source URL, traffic source, campaign, category, geography, timestamp, and consent evidence for contactable leads.

All compliant non-Meta traffic types may be reviewed, including search, SEO, owned web properties, vetted source sites, call campaigns, and compliant media sources

Meta Ads traffic is not accepted

No non-consented traffic

No misleading, fake, or incentivized submissions

No robocall, spam, or scraped-contact traffic

Source, campaign, and consent tracking required

Quality monitoring

Publisher traffic is measured by contactability, duplicate rate, category accuracy, complaint risk, and buyer feedback.

Publisher application

Publisher applications should include business details, source examples, traffic type, categories, states, expected volume, consent process, sample leads, and payment preferences.