Identity Summary Data
The Identity Summary shows the data from the StreamID schema, such as customer ID, client ID, and device ID.
Get Started with Identity Summary Reports
- Define Conviva Session
-
How to use Conviva Connect Fields
- filter against a particular metadata field in the Conviva Connect file, to identify issues or patterns in a set of sessions.
- filter against a particular Conviva Connect ID across one or many days.
- define and shape business KPIs (see Define KPIs).
- map a user journey: a common session ID can be used across multiple data sources (from Conviva Connect and other logs or feeds) to track the user journey through various systems (e.g. site/content discovery, page load, player load, CMS request, DRM request, ad request, CDN request, playback experience, next page/content viewed, app crashes, etc).
-
Get the Conviva Connect Reports
Each row in the Conviva Connect file describes a video session. Conviva defines a Session as an instance of an attempt to play a video; the attempt can be an explicit viewer action or an implicit automatic player action. In VOD, the attempt would typically align with a specific asset; in linear live, the attempt may correspond to multiple played assets within the same session.
A session that is suspended and resumed will appear in different lines in the Conviva Connect log file with the same session ID. Each session line has a respective start time, with the first portion of the session showing the session start time and the second portion of the session showing the session resume time. In this case, the primary key to process the sessions is Session ID + Session Start Time.
In the Conviva Connect file, the Conviva session data (Conviva Connect fields) includes metadata, such as household ID, and household IP. The session time span is from the moment the client starts the session until the client terminates the session. The Conviva Connect file contains the snapshot of each session at the end of the day.
We have summarized all the fields in a table, please review the Conviva Connect field definitions at the end of this document.
You can use the Conviva Connect field data to:
You can also define custom metadata to focus your queries on your specific business needs. This processed information is intended for analysis using a third-party tool.
The supported delivery destinations are:
The Conviva Connect file format is CSV (comma-separated values). We use the standard described in RFC 4180: http://tools.ietf.org/html/rfc4180
The Conviva Connect file name is in the format: DailySessionLog_<CUSTOMER_NAME>_<YYYY-MM-DD>.csv
Tools to Use
Typically users load Conviva Connect into a database such as MySQL or into analytics tools such as Tableau or Micro Strategy, to analyze the data and correlate with other data sets. Please see examples at the sample SQL queries provided for some of the metrics.
StreamID Schema
| Field name | Type | Mode | Description |
|---|---|---|---|
|
CustomerID |
INTEGER |
Customer’s C3 account ID |
|
|
ClientID |
STRING |
Unique ID of the client where video played |
|
|
DeviceId |
STRING |
NULLABLE |
Unique identifier for a physical device in a Household |
|
StartTime |
INTEGER |
NULLABLE |
Start time of ID attachment |
|
EndTime |
INTEGER |
NULLABLE |
End time of ID attachment |
|
HouseholdID |
STRING |
Unique identifier for a Household |
|
|
HouseholdIP |
STRING |
One of the IP addresses in a household related to that client id |
|
|
ConvivaSessionID |
STRING |
Unique identified of a video session. This could be content or ad session. |
|
|
SessionType |
STRING |
Content, Ad |
Type of Session – Content or Ad |