Conviva has built and deployed a unique and new intelligent video measurement and analytics architecture for the next generation of TV.
To enable this feed, you will need to create SFTP credentials and provide them to your Conviva representative.
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.
Create a password and encrypt credentials:
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:
Encrypt the file using the mParticle PGP public key:
-----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v2 mQENBFRKgRIBCACXmtK5WGdBDk/JWqzYdCd8uiKPJrnY0cAqfM6Rv1IhAl38IRKz 9rsfcK1z3bIZYGwfOk1SPBZmSxLERF1DgwhhInrXf+OojxGiRmMRK7QQ1zE/sqvW RZqPeP+fRquK8BTP37Q+h8aophWBqaVfpejAaJtC+Xqe2xeGvBpnA8wu1c+Z1mLg UfuKfRcadHQ1Ej99kWpIHyXh0D83yV1HbG0Gh8x0USKYiLK0Nn0ykVyAB9mk0GjF 3RoynGNHrbn3CH3f0J6ib+u7aVcZ9Y+E0E8KSI4h/4WhpIEWwicolMNeA+mTfySy HKOUGkGy0k6+ltrA1H9ti/nmBkR9brJKP/7pABEBAAG0I05heWRlbiBLb2xldiA8 bmtvbGV2QG1wYXJ0aWNsZS5jb20+iQE5BBMBAgAjBQJUSoESAhsPBwsJCAcDAgEG FQgCCQoLBBYCAwECHgECF4AACgkQK48THX7ssvDsVQf/XZRuWWme2NvxSa+Ce/hB E6jIVLu5mw/snVo7PuGYRT0SoCRjEgx4J7tsmVlraRzBWAYYLdNd0pLAdkF+8rrh 9klxbDAIuXE1KlyjXIifVQZH6I9Ujnnx+IZd+Ev/+FBLDBaEpcQSN1fEvI+MIotp 9Q/7N+uts7DFFt1z7W/L9v0ujf4/t/L8DjYKm3AK+1DpbTlMt31YHoAuCs165pi/ ZSy61BJM1N1XKAUPR7bcUw+ahhlMF7b3nyVQppmasqUdVLKTApCICX6yjooj0RDV 0xcCNATCQJw/X7kL30Svi1C9oUro0KbRKa9O2ObODfBLt+XcrIqOxBwOcHzIg0bv Gw===fzFR -----END PGP PUBLIC KEY BLOCK-----
Share the encrypted file with mParticle. mParticle will notify you when the setup is complete.
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:
Conviva sends custom events to mParticle, with a Custom Event Type of
Other and an event name of
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:
|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.|
|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
|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.|
|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.|
Conviva supports a slightly different set of platforms to mParticle. Supported platforms are mapped as follows:
|Conviva Platform||mParticle Platform|
|Samsung TV||Smart TV|
|Linux / Unix||Web|
|All Others||Out of Band|
|Setting Name||Data Type||Default Value||Description|
|Viewer ID Identity Type||
||Customer ID||The mParticle Identity Type that Conviva’s Viewer ID will be mapped to.|
Was this page helpful?