Conviva has built and deployed a unique and new intelligent video measurement and analytics architecture for the next generation of TV.

Enable the Feed

To enable this feed, you will need to create SFTP credentials and provide them to your Conviva representative.

Create SFTP Credentials

To configure the feed, you will need to create SFTP credentials. These same credentials will be used for all feeds you have set up across your organization account. Any password changes must be coordinated with mParticle.

  1. mParticle will provide you with a Username based on your mParticle Org ID in the format customer_<org_id>.
  2. Create a password and encrypt credentials:

    1. Create a password. To be accepted, your password must be at least 16 characters in length and contain at least one of each of the following:

      • Uppercase alphabet characters (AZ)
      • Lowercase alphabet characters (az)
      • Base 10 digits (0 through 9)
      • Non alphanumeric characters: ~!@#$%^&*_-+=`&#124;\(){}[]:;"'<>,.?/
    2. Create a basic text file containing the Username/Password
    3. Encrypt the file using the mParticle PGP public key:

      Version: GnuPG v2
      -----END PGP PUBLIC KEY BLOCK-----

Share the encrypted file with mParticle. mParticle will notify you when the setup is complete.

Configure the Feed in mParticle

  1. From the Directory, select the Conviva tile and add the Feed integration
  2. Name the configuration and select which mParticle User Identity type your Conviva Viewer ID should be mapped to.
  3. Click Create and Copy the SFTP Hostname and Path.

Conviva configuration

Contact you Conviva manager to complete the setup of the feed in Conviva. You will need to provide the SFTP Hostname and Path, as well as the SFTP credentials you created above. Conviva will upload CSV extracts of your data to mParticle. To be processed, the files must be named according to the following template: DailySessionLog_<CUSTOMER_NAME>_<YYYY-MM-DD>.csv.

Data Mapping

Conviva sends custom events to mParticle, with a Custom Event Type of Other and an event name of Video Session

Event Attributes

mParticle maps Conviva’s field names directly to custom attributes of the event, unless otherwise specified. Exact field names are custom for each Conviva customer, but available fields may include:

Field Name Notes
Viewer ID Unique ID of the viewer or subscriber watching the video content. Typically a masked or hashed identifier without any personally identifying information. This is mapped to a user identity type of your choice.
device/os Mapped to device_info.platform.
Asset Unique ID for the content being viewed.
Conviva Session ID Unique Conviva session identifier.
Start Time Time Conviva received the first Heartbeat for the session. Mapped to the event’s timestamp_unixtime_ms.
ISP Internet Service Provider name
ASN Autonomous System Number for the ISP
CDN The Content Delivery Network used
Stream URL The last streaming URL used during the session.
Startup Time Total time between when Conviva monitoring starts and the first frame of video is played, excluding any pre-roll video.
Playing Time Total time spent displaying video, excluding buffering time
Buffering Time Total time spent rebuffering, not including initial buffering before the video begins to play.
Interupts Number of times the video was interrupted for rebuffering.
Startup Error 0 if the video played successfully. 1 if the video failed to play.
VPF Error List List of errors that caused playback to fail.
Average Bitrate Average bitrate at which content was delivered during the session.
Percentage Complete Total viewing time divided by content length
Video Restart Time Amount of time after the user completes seeking until the video restarts. Cumulative for the whole session.
Connection Induced Rebuffering Time Rebuffering time not related to seek, divided by total playing time.
Session Tags A list of custom session tags. Each tag is mapped directly to a Custom Attribute.
Country Country Name
State State Name

Platform Mapping

Conviva supports a slightly different set of platforms to mParticle. Supported platforms are mapped as follows:

Conviva Platform mParticle Platform
tvOS tvOS
Android Android
Roku Roku
Windows Web
MacOS Web
Xbox One Xbox
Xbox 360 Xbox
Samsung TV Smart TV
Linux / Unix Web
All Others Out of Band

Configuration Settings

Setting Name Data Type Default Value Description
Viewer ID Identity Type string Customer ID The mParticle Identity Type that Conviva’s Viewer ID will be mapped to.

Was this page helpful?