Ooyala Pulse Audience Management

Attention: Please contact your Account Manager at Ooyala before you start using Ooyala Pulse Audience Management. Your Account Manager initiates the integration project in collaboration with our Professional Services Group.
This document details a typical data management platform (DMP) integration with Ooyala Pulse Audience Management, which allows you to target users based on 3rd party data directly through the Pulse platform. Please contact your Account Manager at Ooyala if you want to start using Ooyala Pulse Audience Management. For more general information, refer to Appendix C - Pulse Audience Management (PAM).
Note: Ooyala does not target users that have manually opted out of data targeting from our ad serving network even if they technically match an audience segment. For more information, read our Privacy Policy.

Limitations

  • Maximum 100 segments types per integration. For example, gender, age or location.
  • Maximum 15 segment values per segment type. For example, male, female or 18-24, 25-34.
  • Maximum 3 integrations per account (default setting).
  • If using session store:
    • Maximum 1 async HTTP request per day and per unique user.
    • Minimum one update every 13 days per unique user.
    Note: Inactive users are automatically purged after 13 days. The data is lost from the session store, making the users unavailable for audience management. Campaigns using audience targeting do not deliver to purged users.
  • If using cookies: Maximum 1 async HTTP request per day and per unique user

Data Integration Options

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

*If the native app does not support 3rd party cookies.

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

*If the native app does not support 3rd party cookies.

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 3rd 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

Using Session Store

Pros:

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

Cons:

  • Client 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, refer to Data Management Platform (DMP) Integration.

Overview:

  1. Client sends 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

해당 내용이 도움 되었습니까?