What is Ringier Axel Springer Poland?

Ringier Axel Springer Poland (RASP) is a leading digital media and advertising company in Poland, offering a wide range of premium advertising products across its extensive portfolio of news, lifestyle, and technology platforms. Through high-traffic sites like Onet.pl and Business Insider Polska, RASP provides advertisers with access to a broad and engaged audience. The company leverages data-driven targeting, native advertising, and programmatic solutions to optimize campaign performance. RASP's advertising ecosystem is designed to deliver measurable results across display, video, mobile, and branded content formats.

Product Type: Advertising

Integration Type: Starter Kit & ID Sync

Capabilities

• Captures dlapi_lu and dlapi_aid from URL parameters.
• Fetches adp_session from RASP’s session API.
• Adds all synced IDs to server-side events for attribution.

Sync Details

• IDs:
  • dlapi_lu - A local user identifier captured from the URL to help associate activity with an anonymous user.
  • dlapi_aid - A registered account identifier from the URL used to recognize known users.
  • adp_session - A session ID fetched from RASP that identifies a user’s active browsing session.
• Description:
  • The sync captures the values of dlapi_lu and dlapi_aid from URL parameters and stores them as first-party identifiers for up to 365 days.
  • It performs a fetch call to retrieve the adp_session value from RASP's session endpoint and stores it for up to 7 days.
  • All synced identifiers (dlapi_lu, dlapi_aid, adp_session) are added to server-side events under the context.providers.ringierAxelSpringerPoland object.
  • The values are automatically updated when new URL parameters are detected or the session expires.
  • A failure flag (_adp_session_failure) is stored for 1 day if the session fetch request fails.
  • These identifiers support downstream identity resolution and are required for the starter kit to function correctly.
• Response Example: {"adp_session":"c2lkOjIwMjUwMzI3MDk1ODI2MzcyNjkwOTk1Nw=="}
• Server-side Event Payload: Upon completion of all vendor's sync, the server-side events will incorporate all resolved identifiers as described above. The following object will be appended to the context.providers property within the event's JSON payload.

  {
     "ringierAxelSpringerPoland": {
       "dlapi_lu": "URL parameter value from dlapi_lu",
       "dlapi_aid": "URL parameter value from dlapi_aid",
       "adp_session": "User session value"
     }
  }
  

• Cookie Name:
  • Cookie: _meta_ringierAxelSpringerPoland_dlapi_lu, _meta_ringierAxelSpringerPoland_dlapi_aid, _meta_ringierAxelSpringerPoland_adp_session, _meta_ringierAxelSpringerPoland_adp_session_failure
  • IndexedDB: [your storage prefix]_ringierAxelSpringerPoland_dlapi_lu, [your storage prefix]_ringierAxelSpringerPoland_dlapi_aid, [your storage prefix]_ringierAxelSpringerPoland_adp_session, [your storage prefix]_ringierAxelSpringerPoland_adp_session_failure
  • For a general guide on ID Sync validation, see here.

Sync Setup Guide

1. Gather Credentials

• Obtain the following values from your Ringier Axel Springer Poland representative:
  • Network ID

2. Add a Ringier Axel Springer Poland Sync in MetaRouter

1. From the Pipelines page, find the pipeline associated with the web property you’d like to add a sync to. Hover over the three dot dropdown and select “Build AJS File.”
2. In the Identity Syncs section, select the Ringier Axel Springer Poland sync.
3. Fill out the following fields:
   1. Network ID – Defines a unique identifier for the Ringier Axel Springer Poland network.
   2. Anonymous Local User ID Lifetime (in days) – Specifies how long the synced identifier dlapi_lu remains in the first-party ID graph. Once this duration ends, or if the identifier is no longer detected, a new sync will be triggered.
      • RASP recommends a default value of 365 days.
   3. Registered Account User ID Lifetime (in days) – Specifies how long the synced identifier dlapi_aid remains in the first-party ID graph. Once this duration ends, or if the identifier is no longer detected, a new sync will be triggered.
      • RASP recommends a default value of 365 days.
   4. User Session Lifetime (in days) – Specifies how long the synced identifier adp_session remains in the first-party ID graph. Once this duration ends, or if the identifier is no longer detected, a new sync will be triggered.
      • RASP recommends a default value of 7 days.
   5. API Timeout (in milliseconds) – Sets the time limit for how long the Sync Injector will wait for a response from the RASP session endpoint.
      • Default value is 300 milliseconds.
4. Scroll down and click the Save and Build File button.
5. Deploy your AJS file to propagate changes to your web property.