Partner Portal: manage all your publishers in one place
The partner portal is the module inside the OXIAE platform where you, as a lead generator, manage everyone who delivers leads to you: media agencies, publishers, affiliates and your own brands. You invite them, choose how they deliver, set quality rules and see exactly what comes in per publisher: volume, quality, acceptance rate and rejections.
No separate spreadsheets, no email threads about who delivered what. Every publisher gets their own, shielded dashboard under your brand; you keep the full overview from the platform. And with every delivered request, provenance and consent travel along by default, with a complete audit trail per publisher.
Per publisher you see exactly what they deliver
A publisher is only valuable once you can objectively see what they produce. The platform translates every delivery into the numbers that matter: how many, how good, and at what cost. So you steer on quality instead of gut feeling, and you walk into every publisher conversation with data in hand.
Volume per publisher
See at a glance how many requests each publisher delivers, per day, week or campaign, with trends and peaks in view.
Quality & acceptance rate
The percentage of accepted leads per publisher, alongside rejection reasons and duplicates. So you can see straight away who delivers valuable requests and who does not.
Rejections & reasons
Every rejection is labelled with a reason: outside target audience, invalid phone number, or missing consent, so you have the conversation with your publisher backed by facts.
Provenance & consent
For every delivered lead, the source, campaign and consent proof travel along. Per publisher you can see whether the consent chain is complete and provable.
Quality rules
Set thresholds and filters per publisher: minimum fields, valid postal codes, target-audience criteria. Anything that does not comply is automatically blocked or flagged.
Settlement & payouts
Open balances, accepted volume and payout status per publisher, tied to your payout process, without separate spreadsheets.
Three ways a publisher can deliver
Not every publisher works the same way. One simply wants a form or landing page, another pushes through their own system and the API. You choose the delivery method that fits per publisher, and in every case requests are validated on arrival, including consent and provenance.
Form or landing page
Give your publisher a form or landing page under your brand. Every submitted request enters your flow directly, validated and with provenance.
No-code
API delivery
Publishers with their own systems push requests via a scoped API key to a fixed endpoint. Fields, validation and consent are checked on receipt.
POST /v1/leads
Portal upload
For batch suppliers: an upload in the partner portal (CSV or file) with instant validation, so faulty rows are visible immediately before acceptance.
CSV / batch
Connecting a publisher
Getting a new publisher live is a matter of four steps. You set the rules up front in the platform, so the first delivery meets your quality standard right away, and you never have to clean up afterwards.
Invite
Invite the publisher by email. They create their own, shielded account under your brand and from that moment see only their own environment, never other publishers or your buyers.
Choose delivery method
Decide together how the publisher delivers: a form or landing page under your brand, an API connection with a scoped key, or a portal upload for batches.
Set quality rules
Set the thresholds per publisher: required fields, target-audience criteria, valid postal codes and the requirement of provable consent. Anything that does not comply is rejected or flagged.
Live & monitoring
Set the publisher live and follow their first deliveries on their dashboard: volume, acceptance rate and rejection reasons. You steer by tightening the rules, not by manual work.
Roles & access per publisher
A publisher should see enough to deliver well on their own, and nothing more. The portal works with strictly separated layers: everyone sees only their own delivery, settlement and disputes. Your margins, routing and buyers stay fully private.
What a publisher does see
A publisher sees only their own delivery: numbers, acceptance rate, rejection reasons, outstanding settlement and the status of their disputes.
What a publisher does not see
Other publishers, your buyers, your margins, routing rules or the price you resell at stay fully shielded. Everyone sees only their own layer.
Roles & permissions
Assign roles per publisher: deliver only, view reporting only, or both. Access can be revoked per user and every change is logged.
Per-publisher dashboards & reporting
Every publisher gets their own dashboard with their delivery in real time: numbers, acceptance rate, rejection reasons and the state of their settlement. You see all publishers side by side in the platform and can easily compare who delivers the best quality.
Reports are exportable and always traceable to the source. Want to dig deeper into the numbers, or build your own reporting on the data? You can, via the API and the docs.
Example: publisher overview
| Publisher | Volume | Acceptance | Open |
|---|---|---|---|
| Media Agency North | 1,240 | 92% | € 3,180 |
| Affiliate South | 860 | 74% | € 1,540 |
| Publisher West | 2,110 | 88% | € 5,020 |
How a publisher delivers via the API
Publishers with their own system deliver using a scoped API key that applies only to them. On receipt, the platform checks the request against that publisher’s quality rules, including valid consent, and immediately ties the delivery to the right publisher label.
// A publisher delivers a request via the API
// Header: Authorization: Bearer sk_live_partner_… (scoped to this publisher)
POST https://api.oxiae.com/v1/leads
{
"partner": "media-agency-north",
"contact": {
"name": "Sanne de Vries",
"email": "sanne@example.com",
"phone": "+31 6 12345678"
},
"provenance": {
"source": "facebook-ads",
"campaign": "spring-campaign-q2",
"landing_page": "https://request.partner.com/start"
},
"consent": {
"given": true,
"text": "I consent to being contacted.",
"timestamp": "2026-03-12T09:41:07Z",
"ip": "84.12.x.x"
}
}
// Response (validated against this publisher's quality rules)
{
"id": "lead_8f21",
"partner": "media-agency-north",
"status": "accepted",
"quality_check": {
"consent": "valid",
"target_audience": "within",
"duplicate": false
}
}Provenance & consent safeguarded per publisher
The more publishers you connect, the more important it becomes that you can prove, per delivery, where a lead came from and that there is valid consent. In the partner portal that is not manual work but a built-in guarantee: the consent chain travels with every request and can be audited per publisher, GDPR-compliant.
Consent at the source
Consent is captured the moment the applicant gives it, with text, timestamp and IP. If a publisher delivers without valid consent, the rule blocks the lead.
Provenance inseparable
Source, campaign and the publisher label travel along as fixed fields with every request. Afterwards you can always trace which publisher delivered which lead.
Audit trail per publisher
Every delivery, acceptance, rejection and dispute is logged and exportable. When a buyer or regulator asks, you show the whole chain per publisher.
Processor role clear
Roles and responsibilities between you and your publishers are recorded, so it is clear who is responsible for what in the processing of personal data.
Want to know more about how consent and source are captured? Read consent & provenance or view the full audit trail.
Disputes per publisher, with proof
A rejected lead need not turn into an email discussion. Disputes run in the platform along fixed rules, tied to the original delivery and the consent proof. The right publisher sees the rejection, can respond, and an upheld dispute is automatically settled in their payout.
Objection with proof
A buyer rejects a lead; the rejection reaches the right publisher with a reason, tied to the original delivery and the consent proof.
Handling by rule
Disputes follow fixed rules and deadlines. Your publisher sees the status, can respond and supply additional proof where needed, all in the portal.
Settlement
An upheld dispute is automatically settled in the relevant publisher’s payout, without you having to correct things manually in spreadsheets.
Settlement and payout per publisher are arranged in the payouts & disputes process, tied directly to this portal.
Managing publishers in spreadsheets vs. in the partner portal
As long as you have one or two publishers, a spreadsheet still gets the job done. But as soon as there are more, that approach breaks down on transparency, quality, settlement and disputes. The partner portal inside OXIAE solves exactly that.
One overview, every publisher
Steer your publishers on quality, not gut feeling
“We went from four spreadsheets to one platform. Now we see per publisher what they really deliver, and the arguments about rejections are over, because the proof comes attached.”
Frequently asked questions about the partner portal
The questions we get most often from lead generators who want to manage their publishers in one place.
How do I invite a new publisher?
You send an invitation by email from the portal. The publisher creates their own, shielded account under your brand, chooses a delivery method together with you and goes live once you have set the quality rules. From the first delivery you see their numbers on their dashboard.
Which delivery methods does the partner portal support?
Three: a form or landing page under your brand, an API connection with a scoped key for publishers with their own system, and a portal upload (CSV or batch) for publishers that deliver files periodically. You choose what fits per publisher.
What does a publisher see and not see?
A publisher sees only their own delivery: volume, acceptance rate, rejection reasons, outstanding settlement and the status of their disputes. Other publishers, your buyers, your margins and your routing rules stay fully shielded.
How do I set quality thresholds per publisher?
Per publisher you set rules: required fields, target-audience criteria, valid postal codes and the requirement of provable consent. A delivery that does not comply is automatically rejected or flagged, so your quality stays at level without manual work.
How are provenance and consent safeguarded per publisher?
With every delivered request the source, campaign, the publisher label and the consent proof (text, timestamp, IP) travel along by default. If a publisher delivers without valid consent, the rule blocks the lead. Everything is auditable and exportable per publisher.
How does settlement per publisher work?
Settlement is tied to the accepted volume per publisher and to upheld disputes, which are settled automatically. You manage payouts in the payouts process, without separate spreadsheets. See the payouts page for the details.
How do I handle a dispute with a publisher?
A buyer's rejection reaches the right publisher with a reason, tied to the original delivery and the consent proof. The dispute follows fixed rules and deadlines; an upheld dispute is automatically settled in that publisher's payout.
Manage all your publishers in one place
Book a demo and see how you onboard publishers, guard quality per publisher and settle, with provenance and consent delivered by default.