Skip to content

SDK Pixel

SDK Pixel is an integration component that enables collecting user events from mobile applications (Android / iOS) and sending them to analytics and advertising systems. It acts as a “bridge” between the app and the data platform – WP Data Platform.

Core Features of SDK Pixel

  • Event collection – e.g., app openings, clicks, screen views, transactions,
  • Identifier handling – e.g., WPCLID (for attribution purposes), session ID – session building,
  • Dynamic parameter support – passing campaign parameters (UTM, referer, custom events),
  • Support for deeplinks and install attribution,
  • Modular configuration and extensibility – adaptable to partner needs,
  • Geolocation support (optional) – GDPR-compliant location data collection.

Why Implement SDK Pixel?

  • Improved quality of analytics and marketing data – SDK-provided data is more reliable and stable than web-based or third-party SDK data,
  • Easier personalization and retargeting – more precise ad targeting,
  • Independent integration monitoring (Metrix) – identification of potential app-side issues.

Scope of Data Collected by SDK Pixel

SDK Pixel collects both technical and contextual data, which may include:

Device and App Technical Parameters

Parameter Description Example
c_make device manufacturer e.g., "Apple"
c_make device model e.g., "iPhone"
c_os operating system e.g., "iOS"
c_osv system version e.g., "18.2.1"
an app name e.g., "demo"
ap unique app identifier e.g., "com.developer.demo"
av app version e.g., "6.12.0"
ab app build e.g., "1"
tz user time zone e.g., "Warsaw"
ua user agent – device and system type/version

Identifiers and Sessions

Parameter Description
wph_st session identifier
wph_a user identifier
ltid long-term user ID
fpuid device fingerprint ID
wph_clid click identifier (click ID)
dtid, atid clickthrough identifiers (depending on the campaign source)

Campaign Parameters (UTM)

  • c_utm_source, c_utm_medium, c_utm_campaign, c_utm_content, c_utm_term, c_utm_id, c_utm_gclid, c_utm_device, c_utm_channel, etc.
  • r – referer (referring page),
  • h – page host,
  • v – script version.

Event and Product Parameters

  • e – event type (e.g., ViewContent, Purchase),
  • c_contents – list of products (id, name, category, price, currency, quantity, colour, size, ean, brand, etc.),
  • c_value, c_value_gross – transaction value,
  • c_discount_code, c_discount_value – discount code and value,
  • c_transaction_id – transaction ID,
  • c_shipping_cost – shipping cost,
  • c_item_ids, c_content_ids – product IDs,
  • c_content_category, c_content_name, c_content_type – event content description.

Geolocation Parameters (Optional)

  • c_glat – latitude,
  • c_glon – longitude,
  • c_gcac – position accuracy,
  • c_galt – altitude,
  • c_gaac – altitude accuracy,
  • c_gspe – device speed.

Requirements and Integration

  • SDK is available for Android and iOS platforms,
  • Distribution: WP repository or direct (GitHub / Nexus),
  • Initial configuration required (technical documentation provided by WP team),
  • Configuration can be customized to client-specific needs,
  • Integration support provided by WP's technical team during onboarding.

SDK implementation requires technical support and individual access to the script repository. If you decide to implement SDK Pixel, please contact us at: sdkpixel@grupawp.pl

Frequently Asked Questions (FAQ)
Does SDK Pixel track personal data?

Yes, the SDK collects personal data. Transmitted data may include user and technical identifiers (e.g., WPCLID) that can identify specific individuals.

Can I disable certain SDK features?

Yes, the SDK is modular. You can enable only the components required for your deployment.

Does the SDK impact app performance?

The SDK operates asynchronously and is performance-optimized – it does not affect app performance.

Does the SDK require user consent?

Only if geolocation is enabled. By default, the SDK complies with app privacy policies and does not enforce data collection requiring user consent.