Publisher Portal
Give publishers the instructions and visibility to send better traffic
Recruit publishers, share campaign posting specifications and let their teams inspect submissions, call integrations, outcomes and payouts in your branded portal.
How it works
- 1
Recruit and approve
Use an invitation or turn on publisher signup on your branded domain. Ask the questions your network needs, then choose automatic approval or a pending queue that an operator reviews.
- 2
Connect a campaign
Publishers see the offers and campaign instructions you make available to them. Generated specifications describe the enabled lead and call channels, required fields, authentication and testing behavior.
- 3
Follow traffic and earnings
The portal connects submitted leads, posting outcomes, call tools, reports and payout information to that publisher’s account. Teams can investigate a rejected submission without waiting for a screenshot from an admin.
One place to connect supply
Keep the campaign’s instructions beside the traffic and results they describe.
Server and browser posting
Server integrations use the partner posting key and campaign ID. Campaign browser posting uses a separately enabled publishable key that only works from approved website addresses. Browser keys submit only to their campaign; they do not grant management, lead-reading or ping access.
Specs, snippets and readiness
Use the campaign’s generated posting specification for required fields, response fields and the browser snippet. Progressive capture can connect partial form sessions to a later lead. The landing-page assistant writes a prompt to guide building a page; it does not host the publisher’s site.
Call integrations when enabled
Call-capable campaigns show their call specifications, tracking-number or SIP transport and RTB instructions. RTB quotes have an expiry and transfer requirements. A simulated win in testing mode checks the integration response. It does not mean there is funded live demand.
Posting and postback visibility
Inspect successful and unsuccessful submissions, reported outcomes and the logs available to the publisher role. A failed attempt can carry a specific validation or routing reason. Portal access stays scoped to the publisher’s traffic.
Manage the ongoing relationship
Give publishers useful business context while keeping operator configuration under your control.
Offer and campaign access
Make relevant offers visible to a publisher and provide campaign-specific setup assets. Lead and call instructions follow enabled channels so a lead-only publisher is not sent an unrelated call integration.
Payout and outcome reporting
Publisher reports separate time of lead from time of revenue and show the payouts and outcomes their role can access. Partner payout rules set whether lead accrual follows Sold or Delivered. Payment schedules and thresholds are handled separately.
Team and API access
Authorized publisher users can invite teammates and manage scoped portal API access. Portal API keys and partner posting keys do different jobs: one opens permitted portal tools, and the other submits campaign traffic.
Webhooks and help
Set up the outbound notifications allowed for the account and check the available postback reporting. Role-specific documentation, account contacts and release notes support day-to-day work without giving access to another publisher’s data.
What your account needs
Publisher signup and offer visibility are controlled by the operator. Active membership and permissions decide access. Calls, SIP, RTB and browser posting each need their own campaign or module setup; call RTB is still in controlled rollout. The generated specification is the authority for each campaign, including testing-mode behavior.
Frequently asked questions
Does a portal API key replace the posting key?
No. Portal keys authorize scoped publisher tools. Lead submission uses the partner posting key and campaign ID, or the separately enabled campaign browser-posting key.
Can publishers register without an invitation?
Yes, when you enable publisher self-registration. Configure questions, terms and automatic or manual approval before sharing the branded signup link.
Can one publisher see another publisher’s traffic?
Publisher portal data is scoped to the authenticated account and its permissions. Administrative cross-account views belong to the operator workspace.
Does a sandbox RTB win mean a buyer will accept real calls?
No. A simulated test win only checks the integration’s success path. Live traffic still needs eligible demand, valid funding, capacity and a working transfer setup.
Explore the platform
Set up your buyer network
Choose how buyers get leads and calls. Keep their setup and routing rules in one place.
Every feature is part of the plan. Usage is billed in credits.