SSP Reporting
SSP Reporting pulls revenue and performance reports from your own seats at supply-side platforms into Bidkernel. Every report row is normalized to a common shape — date and hour, device type, media type, impressions, ad requests, net revenue, net CPM, and fill rate — so data from different SSPs can be reported on together, while each SSP's raw fields are preserved on the row.
Supported SSPs Link to section
Adapters currently exist for Equativ, Google Ad Exchange, Index Exchange, Media.net, Nativo, Nexxen, Omnidex, OpenX, Pubmatic, Rubicon, SmileWanted, and Sovrn.
Connections Link to section
A connection links one SSP account to your publisher. Depending on the SSP's adapter, a connection uses one of two ingestion mechanisms:
- API: Bidkernel stores your credentials (an API key, OAuth2 service account, basic auth pair, or portal login, depending on the SSP) and pulls reports on a per-connection cron schedule — daily at 06:00 by default.
- Email: the SSP emails its scheduled reports to a Bidkernel address specific to your publisher. Inbound emails are matched to a connection by sender, their attachments are stored, and a background job parses them into report rows.
Credentials are stored encrypted with AES-256-GCM under data encryption keys wrapped by Google Cloud KMS. Each connection tracks its sync status and last error, can be tested and toggled individually, and has a report timezone setting used when the SSP's data carries no timezone information. A retention threshold (90 days by default) stops syncs from fetching data older than that.
Ad Slot Mapping Link to section
SSPs report against their own external ad unit identifiers. Slot mappings link each external ad unit to one or more Bidkernel ad slot codes and, where applicable, to the property it belongs to. Creating, changing, or deleting a mapping also updates already-ingested report rows in the background, so historical data reflects the current mapping. Rows the SSP itself could not attribute to an ad unit are flagged as unattributable and cannot be mapped.
Where the Data Appears Link to section
The Supply Reports section of the publisher dashboard is the management surface: connection setup, a report builder for querying across supply partners, inbound email review, ad slot mappings, and scrape job monitoring. Publishers with the analytics feature enabled also get an SSP Reported Analytics dashboard charting daily reported impressions and revenue from connected SSPs.
Enabling the Feature Link to section
SSP Reporting is off by default and toggled per publisher from the feature catalog. The toggle controls whether the Supply Reports section appears in the dashboard; scheduled scraping is governed by each connection's own enabled switch.