Real-Time Data Integration

The Scope3 real-time data provider (RTDP) is a low latency (sub 10 ms) RESTful API that enables Ad Tech Platforms to retrieve Scope3 signals for real-time ad decisioning.

Segment Configuration

Before making requests to the Scope3 Real-Time Data Provider (RTDP), most Ad Tech platforms require segment objects to be pre-created with a defined name, category, and price. Ideally, we prefer API access to create and price segments automatically, eliminating the need for manual intervention. This streamlines the deployment process and enables faster activation of custom brand segments.

Requests to the Scope3 Real-time Data provider

Authentication

You will need an authentication key to use the real-time data provider (RTDP). This is different than the API keys used for the primary Scope3 API. Pass this key into a header with the key x-scope3-auth.

Endpoints

We operate servers in several geographical regions globally. We suggest testing latencies from each of your data centers by hitting our /status endpoint.

Endpoint	Location
`rtdp.scope3.com`	Global

Regional-specific endpoints can be made available if needed, to ensure global coverage and low latency.

Input Parameters

The RTDP takes in parameters a JSON body that confines to the OpenRTB specifications or query string key-value pairs. We recommend partners to send full OpenRTB requests, but the below are the current fields that can impact the RTDP response.

Key	Example Value	OpenRTB Field	Priority
domain	yahoo.com	site.domain	✅ Required
appId	com.accuweather.android	app.bundle	✅ Required
page	https://www.nytimes.com/athletic/6125021/2025/02/09/super-bowl-2025-score-eagles-win-chiefs/	site.page app.content.url	✅ Required
country	US	device.geo.country	💡 Strongly Recommended
region	CA	device.geo.region
city	Los Angeles	device.geo.city
metro	803	device.geo.metro
zip	90049	device.geo.zip
device_type	2	device.devicetype
gpid	/22888152279/us/yhp/main/dt/us_yhp_main_dt_top_center	imp[].ext.gpid	💡 Recommended
sellerPlacementId	rKbSuikdwy9UPfEwBcR8Pf6z	imp.tagid
sellerId	ifW4ft3g	app.publisher.id site.publisher.id
schain_nodes	[{"asi":"bluenetwork.com", "sid":"1200", "hp":1 }, {"asi":"exchange.com", "sid":"184033B", "hp":1 } ]	schain.nodes	💡 Recommended
exchange_sid	96724	schain.nodes.sid
exchange_name	example_exchange	schain.nodes.name
exchange_domain	example.com	schain.nodes.domain
eids	[{"source":"liveramp.com","uids":[{"id":"AvxfXjwFaie3SW…"}]}]	user.ext.eids

Output Response

Depending on ad platform, we can respond with deal ID, segment ID, or a combination. Incremental costs can be defined dynamically (as below) or configured in the underlying object.

Key	Example Value	Comment
segments	`["gmp_plus_eligible", "gmp_eligible", "fxj1", "gh23"]`	The segments that are eligible for this request
deal_ids	`["deal1234","deal2342"]`	The deals that are eligible for this request
segments_incremental_cost	`[ "fxj1:0.10", "gh23:0.23"]`	An array of incremental costs for segments that have one, allowing ad tech platforms to adjust bids and floors to ensure additional segment costs are accounted for. Only returned for ad tech platforms that support dynamic data pricing.
nurl	`https://rtdp.scope3.com/nurl/auctionid={AUCTION_ID}&price=${AUCTION_PRICE}&status=delivered`	The status field should be `delivered` for impressions delivered to the page, and `won` for impressions that are won in the ad platform

Win notifications

Scope3 exposes a web hook endpoint for notifications for every impression won delivered (the openrtb nurl and burl concepts). This endpoint expects at least auction ID and price, as well as a status field for delivered vs won. The Scope3 solutions team will help set this up to use available ad platform macros.

Log files

Scope3 expects a log file with official, billable impressions on at least a daily basis. This log file should include:

Field	Values	Example

QPS & scaling considerations

To ensure that using the Scope3 RTDP remains cost-effective and minimizes environmental impact, we recommend collaborating with our team to scale QPS caps as demand for the integration grows, and discuss how to best use the allocated QPS. Contact us to discuss this further.