Contact Support
System StatusAudience Fields and Data Definitions
Brightcove Audience will deliver a set of video viewing data to specific fields in your integrated platform. Below is an example of those fields and a description of what the data is that will populate each field
Standard fields
These fields will always be populated by Brightcove Audience.
| Field | Description |
|---|---|
| video_id | The ID of the Brightcove video associated with the viewing event |
| video_name | The name of the video in Video Cloud |
| tracking_id | You can add a custom tracking ID to a URL |
| external_id | The Global User ID (GUID) used to identify the user |
| player_id | The ID of the Brightcove Player that created the view event |
| page_url | The URL of the page where the video was viewed |
| watched | Percent watched - How far down the timeline they watched |
| time_watched | Seconds of the video watched - The total amount of time they actually spent with that video |
| created_at | Creation date |
| updated_at | Last updated date |
| is_synced | A boolean denoting whether or not the view event has been synchronized to the third party platform. |
Additional fields
These fields are not automatically populated. They are used to track additional custom data. By default, they are configured to capture interactivity from Gallery In-Page experiences. If you are not using interactivity, these fields will be blank.
| Field | Description |
|---|---|
| event_1, event_2, event_3 | Custom events |
| metric_1, metric_2, metric_3 | Custom metrics |
| UTM fields - utmSource, utmMedium, utmCampaign, utmTerm and utmContent | For information on working with UTM fields see Working with UTM Fields in the Audience Module. |
Custom fields
These fields are not automatically populated. You have the option to sync reference ID, tags or custom fields to your MAP or CRM via these fields. To set this up please contact support and request, for example: “Please map my Video Cloud field “tags” to the Audience “custom_1” field.”
| Field | Description |
|---|---|
| custom_1, custom_2, custom_3 | Custom events |