Data Integration Options

Pulse offers two data integration options:
  1. Using cookies to locally store user ID and segmentation.
  2. Using Pulse backend session store (we may charge a storage monthly fee).
Table 1. Platform Support Using SDK
Platform + Pulse SDK Cookie Session Store
HTML5 web mobile Yes Yes
Android native app No* Yes
iOS/tvOS native app No* Yes

*If the native app does not support third-party cookies.

Table 2. Platform Support Using VAST
Platform + VAST Cookie Session Store
HTML5 web mobile Yes Yes
Android native app No* Yes
iOS/tvOS native app No* Yes

*If the native app does not support third-party cookies.

Integrate Using Cookies

Pros

  • Easier to integrate as it does not require any additional app or player code modification.
  • Ideal if users do not log in or subscribe to applications.

Cons

  • Does not work on cookieless environments (some native apps).
  • Does not work on browsers that block third-party cookies.
  • Requires a DMP partner to segment user information.

Overview

  1. DMP segments the user and sends the user segments to Pulse backend.
  2. Pulse drops a cookie in the user browser.
  3. When the user plays a new video, an ad request is made to Pulse backend containing the user information that has been stored locally in the cookie.
  4. Pulse backend responds with ads that match the user segmentation rules.

Integration using cookies

Integrate Using Session Store

Pros

  • Enables tracking of users across devices.
  • Ideal if users log in or subscribe to applications.
  • You can combine user database and DMP segmentation to enhance targeting.

Cons

  • Your players are required to manage the user unique ID and make sure it is sent with every ad request.
  • May require code changes across all applications to add new functionality (low complexity changes). For more information, see Data Management Platform (DMP) Integration.

Overview

  1. You send the user ID and segments to Pulse backend.
  2. Pulse stores the user ID and segments in the backend session store.
  3. When the user plays a new video, an ad request is made to Pulse backend containing the user ID.
  4. Pulse backend responds with ads that match the user segmentation rules. Session store segments update cookie segments.

Integration using session store