Engage Server Side RT Revenue Reporting
Overview
Server side real-time revenue reporting is an API service that supports server-side reporting of revenue generated by Teads.
Key Characteristics
- Primary usage: Designed for partners who want to know revenue per session.
- Discrepancy rate: Up to 5%.
- Restricted service: Can be enabled for partners only on specific approved use cases.
Endpoint
Partners should provide the endpoint that Teads will use to track revenue via a click pixel.
Postback URL Pattern
https://example.com/outbrain_postbacks?requestId={{requestId}}&rev={{revenue}}×tamp={{click_timestamp}}&extid={{extid}}&secExtid={{extIdSecondary}}&os={{os}}&widgetId={{widgetId}}&publisherId={{publisherId}}
URL Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
https://example.com/outbrain_postbacks? | URL | Mandatory | A unique URL to where Teads fires the pixel. |
{{requestId}} | String | Optional | The identifier from the client, usually holds the session ID (8–64 characters). If not sent from the client, Teads sends our internal request ID. |
{{revenue}} | Decimal | Mandatory | The revenue in USD; supports up to 6 digits after the decimal. Contains either the click value or the impression value for programmatic. |
{{click_timestamp}} | Long | Optional | The timestamp (epoch) when the click/impression occurred (EST). |
{{extid}} | String | Optional | Single value with a maximum of 110 characters for use with the Engage External ID API. |
{{os}} | String | Optional | Operating system. |
{{widgetId}} | String | Optional | Unique widget ID. |
{{extIdSecondary}} | String | Optional | Secondary External ID. |
{{publisherId}} | String | Optional | Hashed string publisher ID. |
Getting the Request ID from the Publisher
Teads uses the odb parameter pubImpId to get the session ID / click identifier from the publisher.
There are two supported ways to send this value:
- Global variable:
OB_pubImpId - HTML attribute on the container div:
data-pub-imp-id
The parameter will be returned to the client alongside the click revenue inside the {{requestId}} macro.
Support
Need Assistance?
For any questions regarding Server Side RT Revenue Reporting, please reach out directly to your Teads account representative.