Data integration options

INVIDI Pulse offers three data integration options:
  1. Using cookies to locally store viewer ID and segmentation.
  2. Using Pulse session store (we may charge a storage monthly fee).
  3. Using cookies and session store combined, where you can use cookies for platforms where the viewer does not log in, and you can use session store for cookieless or subscription platforms.
Table 1. Platform support using Pulse 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.

Integration using cookies

Pros

  • Easier to integrate as it does not require any additional app or player code modification.
  • Ideal if viewers 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 viewer information.

Overview

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

Integration using cookies

Integration using session store

Pros

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

Cons

  • Your players are required to manage the viewer unique persistent identifier (PID) 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 viewer ID and segments to Pulse.
  2. Pulse stores the viewer ID and segments in the session store.
  3. When the viewer plays a new video, an ad request is made to Pulse containing the viewer ID.
  4. Pulse responds with ads that match the viewer segmentation rules. Session store segments update cookie segments.

Integration using session store

Example: Cookies and session store combined

A viewer watches videos on a website first as an anonymous viewer and then as an authenticated viewer.

  1. Viewer goes to the website for the first time and does not authenticate, they navigate as anonymous viewer.
  2. The viewer is segmented by DMP and an HTTP request is sent to Pulse with anonymous viewer segments. For example, gender=male, age=20-30.
  3. Pulse drops a cookie in the viewer browser with the following parameters:
    • PID=XYZ (Pulse randomly generated ID)
    • VP-DMP=123abc (encrypted viewer segments gender=male, age=20-30)
  4. Now, the same viewer does authenticate on the website and is identified as 2467a22f-9d74-406a-ab62-54fae1414af9.
  5. An HTTP request is made to Pulse containing the viewer ID:

    http://subdomain.videoplaza.tv/proxy/pixel/v2?dmpParam=a%3D1%2Cg%3D2&pid=2467a22f-9d74-406a-ab62-54fae1414af9

  6. Pulse session store adds the viewer 2467a22f-9d74-406a-ab62-54fae1414af9 segments gender=male, age=20-30 to the list.
  7. The viewers's local cookie is also updated to reflect the new ID:
    • PID=2467a22f-9d74-406a-ab62-54fae1414af9 (replaces the previously randomly generated ID)
    • VP-DMP=123abc (encrypted viewer segments gender=male, age=20-30)
  8. Viewer watches a video and the player makes a new ad request with pid=2467a22f-9d74-406a-ab62-54fae1414af9. Pulse checks the session store for segments that match viewer 2467a22f-9d74-406a-ab62-54fae1414af9 and returns targeted ads.
  9. Viewer logs out of a website and cookie ID is still using the viewer ID 2467a22f-9d74-406a-ab62-54fae1414af9.