Ringier Axel Springer Polska (Onet Ads)
Datafly Signal sends page, product, cart, lead and purchase activity to Ringier Axel Springer Polska (Onet Ads) server to server, through the DL API activity collector documented at pomoc.onetads.pl. RASP uses these events for retargeting and campaign attribution across Onet, Business Insider Polska and the rest of its network.
Status: alpha. Built from RASP’s published OpenAPI definitions; not yet tested against a live RASP account. Ask your RASP account manager to validate the integration before relying on it.
Prerequisites
- A RASP (Onet Ads) advertiser account.
- Your Pixel ID (
actgid), shown in the Onet Ads panel. Each website has its own pixel ID. - Your Network ID, the path segment of
csr.onet.pl/{network}(1746213unless RASP tells you otherwise).
Configuration fields
| Field | Required | Notes |
|---|---|---|
network_id | Yes | 1746213 (default) or 4178463. |
pixel_id | Yes | The pixel number RASP assigned to this website (actgid). |
Request format
GET https://csr.onet.pl/1746213/activity?event=purchased&actgid=<pixel ID>&src=s2s
&ord=321-123&cost=33.33&tax=3.33&products=[{"id":"SKU_1","name":"...","price":120,"qty":2}]
&eid=<MD5 of the email>&npa=0&gdpr=1&gdpr_consent=<TCF string>&lu=...&aid=...&_=<epoch ms>
User-Agent: <visitor user agent>
X-Forwarded-For: <visitor IP>
Referer: <page URL>
Cookie: adp_session=<session ID>Identity and consent
| RASP field | Source | Notes |
|---|---|---|
adp_session cookie | properties.adp_session | RASP’s session ID, “required in server-to-server communication”. It can only be fetched in the browser (GET csr.onet.pl/{network}/session with third-party cookies). |
lu, aid | properties.dlapi_lu, properties.dlapi_aid | The dlapi_lu and dlapi_aid values RASP appends to landing URLs. |
eid | properties.email or traits.email | Normalised (trim, lowercase), then MD5, as RASP documents. |
npa | marketing consent | 0 when granted, 1 otherwise. |
gdpr, gdpr_consent | TCF consent | gdprApplies and the TCF v2 string from your CMP. |
Datafly.js does not yet collect adp_session, dlapi_lu or dlapi_aid. Until it does, pass them as event properties (for example from a first-party cookie your site already keeps). Without adp_session, RASP may not attribute the event.
Event mapping
| Signal event | RASP event | Required RASP fields | Preset |
|---|---|---|---|
page | page_view | actgid | Default, Ecommerce |
view_item | product_detail (sitetype=product) | actgid | Default, Ecommerce |
add_to_cart | add_to_cart | actgid | Default, Ecommerce |
generate_lead | custom | actgid, ord (lead ID, else the event ID) | Default, Ecommerce |
purchase | purchased | actgid, ord, cost | Default, Ecommerce |
view_item_list | page_view (sitetype=list) | actgid | Ecommerce |
search | search_query | actgid, query | Ecommerce |
remove_from_cart | remove_from_cart | actgid | Ecommerce |
view_cart | view_cart (sitetype=cart) | actgid, cost | Ecommerce |
begin_checkout | checkout | actgid | Ecommerce |
Items are sent as RASP’s products parameter: a stringified JSON array of id, name, price, qty, category, brand and variant.
Signal forwards properties the preset does not map unless the integration’s strict output contract is on; for a query-string destination such as RASP they would become extra URL parameters. Turn on strict_output_contract for this integration.