What is Wirtualna Polska?

Wirtualna Polska is a leading Polish digital media and advertising platform that leverages machine learning algorithms to deliver personalized advertising solutions across its extensive network of websites and services. Their platform analyzes user behavior and engagement data at scale to help advertisers reach relevant audiences with precision, enabling highly tailored ad experiences for millions of Polish internet users. A unique advantage of this integration is the ability to activate advertisers' first-party data—including hashed emails and CRM IDs—directly within the platform, significantly enhancing targeting accuracy and overall campaign effectiveness. By connecting businesses with their target audiences across multiple channels and devices, Wirtualna Polska enables advertisers to maximize their ad spend efficiency, drive higher conversions, and achieve measurable marketing results.

Product Type: Advertising

Integration Type: Starter Kit & ID Sync

Capabilities

• Retrieves statid via a fetch request to Wirtualna Polska and stores it for advertising attribution.
• Generates a unique userId for cross-session user tracking.
• Generates a sessionId to group events within a single session.
• Adds identifiers to server-side events for attribution and targeting.
• Migrates userId from Wirtualna Polska’s legacy pixel localStorage keys when available.

Considerations

• Requires coordination with Wirtualna Polska to allowlist your domain for CORS access to the identity endpoint.
• If the fetch request fails, a failure marker is stored for 1 day and the sync will retry after expiration.

Sync Details

• IDs:

  • statid – A device identifier retrieved from Wirtualna Polska's identity endpoint and used for advertising attribution.
  • userId – A unique identifier generated in the format {10-digit-random}.{unix-timestamp} to represent a user across sessions.
  • sessionId – A session identifier generated in the same format as userId, used to group events within a session.

• Description:

  • The sync retrieves statid from a fetch request and generates userId and sessionId when not already present in storage.
  • The sync migrates userId from Wirtualna Polska’s localStorage keys when available and valid.
  • Migration requires three keys in localStorage: __wph_a.key, __wph_a.ts, and __wph_a.accessed. The userId is migrated only if __wph_a.accessed is less than 1 year old (static window per WP spec, independent of Cookie Lifetime setting). If the value is older or any key is missing, a new userId is generated.
  • All three identifiers (statid, userId, sessionId) use rolling expiration — their TTLs are extended on every sync run, so the storage marker persists as long as the user is active.
  • Existing userId and sessionId values are reused if present in storage.
  • The statid is stored with a fixed lifetime of 1095 days, though browser limitations may reduce this duration (e.g., Chrome caps at 400 days).
  • Values are refreshed when expired or when new data is detected.
  • The identifiers are added to server-side event payloads for attribution or targeting.

• Response Example:

  JSON

  {
    "statid": "a3ff56e7298979042e2314761eebc884:7e83d1:1772685915:v3"
  }

• 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

  JSON

  {
    "wirtualnaPolska": {
      "statid": "a3ff56e7298979042e2314761eebc884:7e83d1:1772685915:v3",
      "userId": "5065210629.1770720426993",
      "sessionId": "3847291056.1770720426993"
    }
  }

• Cookie Name:

  • Cookie: _meta_wirtualnaPolska_statid, _meta_wirtualnaPolska_statid_failure, _meta_wirtualnaPolska_user_id, _meta_wirtualnaPolska_session_id
  • IndexedDB: [your storage prefix]_wirtualnaPolska_statid, [your storage prefix]_wirtualnaPolska_statid_failure, [your storage prefix]_wirtualnaPolska_user_id, [your storage prefix]_wirtualnaPolska_session_id
  • For a general guide on ID Sync validation, see here.

Sync Setup Guide

1. Gather Credentials

This sync requires coordination with Wirtualna Polska. Contact Wirtualna Polska's support team to have your domain added to allowed origins in their CORS settings.

2. Add a Wirtualna Polska Sync in MetaRouter

To gather the statid, userId, and sessionId, you must add a Wirtualna Polska sync.

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 Wirtualna Polska sync.
3. Fill out the following fields:
   1. Cookie Lifetime (in days) - How long a synced identifier remains in first-party storage. When expired or no longer detected, the sync will re-trigger. Default: 365 days
      1. Important Note: The default 365 days is set per Wirtualna Polska requirements. Please do not change the default lifetime without approval from your Wirtualna Polska representative.
   2. Session Lifetime (in minutes) - Duration a session ID remains valid. A new ID is created when this time expires. Example: 15
   3. API Timeout (in milliseconds) - Maximum time the Sync Injector waits for a response from the vendor's API. Example: 300
4. Scroll down and click the Save and Build File button.
5. Deploy your AJS file to propagate changes to your web property.