The page_view
call lets you record whenever a user sees a page of your website, along with any optional properties about the page.
Parameters (required and recommended)
Automatically added parameters by cact API for web sources
Example
Send this event to signify that a user has logged in.
Example
Use this event to contextualize search operations. This event can help you identify the most popular content in your app.
Example
This event signifies that a user has selected some content of a certain type. This event can help you identify popular content and categories of content in your app or click on internal promotion.
Example
This event indicates that a user has signed up for an account.
Example
When you send an event, it needs to carry enough information to identify which user made it. We can link events together using cookies. But destination partners require accurate identifiers to take actions.
id
and email
are usually the most useful parameters. Though some destination partners also use firstname
, lastname
, birthdate
, city
, ...
You won't always have all of those parameters. But it is recommended to send them as soon as you can during user's browsing.
About Hashing
In some cases, you won't be able to send a parameter plain value. It is either unavailable or restricted.
Thus it might be possible to send the hashed values. We currently accept 2 algorithm : md5
and sha256
.
Every user.<property>
can be sent under hashed format with algorithm suffix: _md5
or _sha256
(underscore followed by lowercase algorithm name)
Example :
No need to send both plain and hashed values :
if you send plain value, the hashed values aren't necessary We can generate hashed values on server side using plain value
if you don't send plain value, then you should fill as much hashed values as possible Partners require different hash algorithms and without plain value, we can't generate any hash. That's why we need the exact hashed value
Name | Type | Required | Example Value | Description |
---|---|---|---|---|
Name | Type | Required | Example Value | Description |
---|---|---|---|---|
Name | Type | Required | Example | Description |
---|---|---|---|---|
Name | Type | Required | Example value | Description |
---|---|---|---|---|
Name | Type | Required | Example value | Description |
---|---|---|---|---|
Name | Type | Required | Example | Description |
---|---|---|---|---|
Name | Type | Required | Example Value | Description |
---|---|---|---|---|
we only support hex (base16) encoding (i.e.: hashed values are carried by strings with [0-9a-f] characters) Other encodings are not supported yet
page_type
string
Yes
product_list
Page category. Recommanded predefined types:
home
landing
product_list
product
content_list
content
search
funnel
success
funnel_confirmation
account
cart
legal (e.g. Privacy Policy)
Equivalent to tc_vars.env_template
page_name
string
No
Suggestion for Mother's Day
Name of the page.
user
Yes
{
id: '12345',
email: 'toto@domain.fr',
consent_categories: [1,3]
}
consent_categories
is the user's consents list. It is automatically filled from web sources if you use Commanders Act CMP.
You should also add all user's properties in this user object, especially reconciliation key (id, email).
user
Yes
{
id: '12345',
email: 'toto@domain.fr',
consent_categories: [1,3]
}
consent_categories
is the user's consents list. It is automatically filled from web sources if you use Commanders Act CMP.
You should also add all user's properties in this user object, especially reconciliation key (id, email).
title
string
No
Products - MySite.com
Title of the page :document.title
from the DOM API
url
string
No
Full URL of the page. Equivalent tolocation.href
from the DOM API.
path
string
No
/products/mothers
Path portion of the URL of the page : location.pathname
from the DOM API.
referrer
string
No
Full URL of the previous page : document.referrer
from the DOM API.
method
string
No
The method used to login.
user
Yes
{
id: '12345',
email: 'toto@domain.fr',
consent_categories: [1,3]
}
consent_categories
is the user's consents list. It is automatically filled from web sources if you use Commanders Act CMP.
You should also add all user's properties in this user object, especially reconciliation key (id, email).
search_term
string
Yes
t-shirts
The term that was searched for.
user
Yes
{
id: '12345',
email: 'toto@domain.fr',
consent_categories: [1,3]
}
consent_categories
is the user's consents list. It is automatically filled from web sources if you use Commanders Act CMP.
You should also add all user's properties in this user object, especially reconciliation key (id, email).
content_type
string
No
product
The type of selected content.
item_id
string
No
I_12345
An identifier for the item that was selected.
user
Yes
{
id: '12345',
email: 'toto@domain.fr',
consent_categories: [1,3]
}
consent_categories
is the user's consents list. It is automatically filled from web sources if you use Commanders Act CMP.
You should also add all user's properties in this user object, especially reconciliation key (id, email).
method
string
No
The method used for sign up.
user
Yes
{
id: '12345',
email: 'toto@domain.fr',
consent_categories: [1,3]
}
consent_categories
is the user's consents list. It is automatically filled from web sources if you use Commanders Act CMP.
You should also add all user's properties in this user object, especially reconciliation key (id, email).
id
string
No*
845454
User's main identifier (e.g. CRM id)
(*) required for many destinations and internal processing.
email
string
Yes*
john.doe@example.com
Email (plain value)
(*) required for many destinations and internal processing. Not required if email_sha256
is provided
email_md5
string
No*
8eb1b52... (size 32)
Email, hashed using MD5 algorithm. Not required if email
is provided (see below)
email_sha256
string
No*
836f82d... (size 64)
Email, hashed using SHA-256 algorithm. Not required if email
is provided (see below)
phone
string
No*
+33612345678
Phone number, E.164 format (*) required for some destinations.
firstname
string
No
John
First name
lastname
string
No
Doe
Last name
gender
string
No
m
Gender
f
for Female
m
for Male
birthdate
string
No
1970-01-01
Birth date, YYYY-MM-DD
format
city
string
No
Boston
City
state
string
No
Massachusetts
State
zipcode
string
No
02108
Zip code
country
string
No
USA
consent_categories
Array
Yes
[1,2,3]
User's consent categories. Necessary to grant data sharing with destination partners. It is automatically filled from web sources if you use Commanders Act CMP.
This event signifies a user has submitted their payment information
Parameters (required and recommended)
Example
This event signifies a user has submitted their shipping information.
Example
This event signifies that an item was added to a cart for purchase.
Parameters (required and recommended)
Example
The event signifies that an item was added to a wishlist. Use this event to identify popular gift items in your app.
Parameters (required and recommended)
Example
This event signifies that a user has begun a checkout.
Parameters (required and recommended)
Example
Log this event when a lead has been generated to understand the efficacy of your re-engagement campaigns.
Parameters (required and recommended)
Example
Fire this event when one or more items are purchased by a user.
Automatically added by cact API
Example
Fire this event when a purchase was refund
Automatically added by cact API
Example
This event signifies that an item was removed from a cart.
Parameters (required and recommended)
Example
This event signifies an item was selected from a list.
Example
This event signifies that a user viewed their cart.
Parameters (required and recommended)
Example
This event signifies that some content was shown to the user. Use this event to manage the most popular items viewed.
Parameters (required and recommended)
Example
Log this event when the user has been presented with a list of items of a certain category.
Example
Parameters (required and recommended)
When you send an event, it needs to carry enough information to identify which user made it. We can link events together using cookies. But destination partners require accurate identifiers to take actions.
id
and email
are usually the most useful parameters. Though some destination partners also use firstname
, lastname
, birthdate
, city
, ...
You won't always have all of those parameters. But it is recommended to send them as soon as you can during user's browsing.
About Hashing
In some cases, you won't be able to send a parameter plain value. It is either unavailable or restricted.
Thus it might be possible to send the hashed values. We currently accept 2 algorithm : md5
and sha256
.
Every user.<property>
can be sent under hashed format with algorithm suffix: _md5
or _sha256
(underscore followed by lowercase algorithm name)
Example :
No need to send both plain and hashed values :
if you send plain value, the hashed values aren't necessary We can generate hashed values on server side using plain value
if you don't send plain value, then you should fill as much hashed values as possible Partners require different hash algorithms and without plain value, we can't generate any hash. That's why we need the exact hashed value
Enumerated Values for payment methods :
Enumerated Values for purchase status:
In this section, you will find all the events references supported by Commanders Act
Here are the most used events:
This event signifies a user has submitted their payment information
Parameters (required and recommended)
Example
This event signifies a user has submitted their shipping information.
Example
This event signifies that an item was added to a cart for purchase.
Parameters (required and recommended)
Example
The event signifies that an item was added to a wishlist. Use this event to identify popular gift items in your app.
Parameters (required and recommended)
Example
This event signifies that a user has begun a checkout.
Parameters (required and recommended)
Example
Log this event when a lead has been generated to understand the efficacy of your re-engagement campaigns.
Parameters (required and recommended)
Example
Send this event to signify that a user has logged in.
Example
The page_view
call lets you record whenever a user sees a page of your website, along with any optional properties about the page.
Parameters (required and recommended)
Automatically added parameters by cact API for web sources
Example
Fire this event when one or more items are purchased by a user.
Automatically added by cact API
Example
Fire this event when a purchase was refund
Automatically added by cact API
Example
This event signifies that an item was removed from a cart.
Parameters (required and recommended)
Example
Use this event to contextualize search operations. This event can help you identify the most popular content in your app.
Example
This event signifies that a user has selected some content of a certain type. This event can help you identify popular content and categories of content in your app or click on internal promotion.
Example
This event signifies an item was selected from a list.
Example
This event indicates that a user has signed up for an account.
Example
This event signifies that a user viewed their cart.
Parameters (required and recommended)
Example
This event signifies that some content was shown to the user. Use this event to manage the most popular items viewed.
Parameters (required and recommended)
Example
Log this event when the user has been presented with a list of items of a certain category.
Example
Parameters (required and recommended)
When you send an event, it needs to carry enough information to identify which user made it. We can link events together using cookies. But destination partners require accurate identifiers to take actions.
id
and email
are usually the most useful parameters. Though some destination partners also use firstname
, lastname
, birthdate
, city
, ...
You won't always have all of those parameters. But it is recommended to send them as soon as you can during user's browsing.
About Hashing
In some cases, you won't be able to send a parameter plain value. It is either unavailable or restricted.
Thus it might be possible to send the hashed values. We currently accept 2 algorithm : md5
and sha256
.
Every user.<property>
can be sent under hashed format with algorithm suffix: _md5
or _sha256
(underscore followed by lowercase algorithm name)
Example :
No need to send both plain and hashed values :
if you send plain value, the hashed values aren't necessary We can generate hashed values on server side using plain value
if you don't send plain value, then you should fill as much hashed values as possible Partners require different hash algorithms and without plain value, we can't generate any hash. That's why we need the exact hashed value
Enumerated Values for payment methods :
Enumerated Values for purchase status:
This event is associated with your ad being displayed, can be used to track the touch point "impressions" in Campaign Analytics module
This event is associated with someone clicking your ad, can be used to track the touch point "clicks" in Campaign Analytics module
Example
To create touch points 'sites' and 'orders' you can use the following events:
'page_view' to create a touch point 'sites'
'purchase' to create a touch point 'orders'
Commanders Act's video specification lets you define how a customer engages with your videos and the related ad content.
This documentation details the conventions and best practices for sending events when tracking videos. The document clarifies the structure and classification of these events, which fall into four categories: Playback
, Content
, Ads
and Video Settings
.
Playback events are tied to the actual playback of video content and track information about the video player.
For example, when a customer plays a video on an app, a Video Playback Started event is sent along with a unique session_id. All subsequent events generated from that session are tied to the same session_id.
If a web page has two video players, there will be two separate sessions and associated session_ids. However, if two separate videos are played on the same video player, they will still be considered a single session with two associated pieces of content.
All the playback events share the same properties that describe the current state of the video player.
The following table lists all the properties of this playback event object in detail:
This section details all the video playback events.
For more information on each of the properties associated with these events, refer to the Playback Event Properties section.
This event is associated with the user action of pressing the play button on the video player to initiate the video playback.
A sample event is as shown below:
This event corresponds to the user action of pausing the video playback.
A sample event is as shown:
This event is sent when the video playback stops unintentionally. Network loss, user closing the browser, redirect, etc. are some of the common reasons. You can pass the cause within the property interruption_method
.
A sample event is as shown:
This corresponds to the event of buffering content or an advertisement.
A sample event is as shown:
This corresponds to the event when the playback finishes buffering the content or an advertisement.
A sample event is as shown:
This event is sent when a user manually seeks a certain cursor position of the video content or an advertisement in the playback. The cursor_position
property indicates where the user is seeking from (time in seconds) and the seek_position
indicates the cursor position in the playback where the user is seeking to.
A sample event is as shown:
This event is sent after a user manually seeks to a certain cursor position of the video or ad in the playback. The cursor_position
property indicates where the user resumes the playback.
A sample event is as shown:
This event is sent after the user resumes the video playback after it was paused.
A sample event is as shown:
This event is sent after the playback is complete and when the pod session is finished. Note that the cursor_position
property has the same value as the total_length
property.
A sample event is as shown:
A content pod refers to a part / group / segment of the video content or the advertisement within the playback.
Suppose a video playback session has a video and one mid-roll advertisement. This means that the mid-roll ad splits the playback in two separate content pods. The mid-roll ad is included within a single ad pod.
The flow is as follows:
User starts and completes the first content pod
User starts and completes the ad
User starts and completes the second content pod
All of these events within the flow happen within one video playback.
All the content events share the same properties that describe the current state of the video content that is viewed by the user during the playback.
The following table lists all the properties of this playback event object in detail:
This section details all the video content events.
This event is sent once the user starts playing video content segment within a playback.
A sample event is as shown:
These events are sent as heartbeats every after a set interval to indicate the length of video viewed by the user, determined by the cursor_position
property.
A sample event is as shown:
These events are sent when a quarter of the video is reached, determined by the cursor_position
property.
A sample event is as shown:
This event is sent once the video segment within the playback is completed. Note that the cursor_position
property has the same value as the total_length
property.
A sample event is as shown:
All the ad events share the same properties that describe the current state of the video ad content that a user is interacting with during the playback.
The following table lists all the properties of this ad event object in detail:
This section details all the ad events.
For more information on each of the properties associated with these events, refer to the Ad Event Properties section.
This event is sent when an advertisement roll starts playing within the video playback.
A sample event is as shown:
This event is sent between set intervals when the video ad is playing and is determined by the cursor_position
property.
A sample event is as shown:
This event is sent after the user has viewed a video ad completely. Note that the cursor_position
property has the same value as the total_length
property.
This event is sent after the user has viewed the video ad roll completely. Note that the cursor_position
property has the same value as the total_length
property.
This event is sent when the user click on the skip ad button.
This event is sent when an advertisement break starts playing while the video playback.
A sample event is as shown:
This event is sent after the user has viewed the video ad break pod completely. Note that the cursor_position
property has the same value as the total_length
property.
This event is sent when the user click on the add.
All the settings events share the same properties that describe the current state of the video content that a user is interacting with during the playback.
This section details all the video settings events.
This event is sent when the user modify the audio volume of the video player.
A sample event is as shown below:
This event is sent when the user modify the speed of the video player.
A sample event is as shown below:
This event is sent when the user turns on the subtitles of the video player.
A sample event is as shown below:
This event is sent when the user turns off the subtitles of the video player.
A sample event is as shown below:
This event is sent when the user turns on the full screen view of the video player.
A sample event is as shown below:
This event is sent when the user turns off the full screen view of the video player.
A sample event is as shown below:
This event is sent when the video quality of the video player is modified.
A sample event is as shown below:
This event is sent when the video is shared by the user.
A sample event is as shown below:
Every Video Playback Resumed
the event should be followed by an event Video Content Playing
or a Video Ad Playing
event, depending on what asset the playback resumes to.
Commanders Act also lets you track and analyze the performance and quality of your video content during the playback.
Whenever a user changes the video quality during playback, you can track a Video Quality Updated event along with the following properties:
bitrate
: Denotes the updated bit rate in kbps
.
framerate
: Denotes the updated frame rate in fps
.
startupTime
: Denotes the time when the video quality was changed by the user.
droppedFrames
: Indicates if any frames were dropped during the video quality change.
The following event flow demonstrates how you can implement the Commanders Act video specification:
Ads that appear before the start of the video playback are called pre-roll ads.
Ads that appear in the middle of the playback are mid-roll ads.
Ads that appear after the video playback are called post-roll ads.
These ads can be a promotional video by the sponsors or a piece of content offered by the content provider.
Name | Type | Required | Example Value | Description |
---|---|---|---|---|
Name | Type | Required | Example value | Description |
---|---|---|---|---|
Name | Type | Required | Example Value | Description |
---|---|---|---|---|
Name | Type | Required | Example Value | Description |
---|---|---|---|---|
Name | Type | Required | Example Value | Description |
---|---|---|---|---|
Name | Type | Required | Example Value | Description |
---|---|---|---|---|
Name | Type | Required | Example | Description |
---|---|---|---|---|
Name | Type | Required | Example | Description |
---|---|---|---|---|
Name | Type | Required | Example | Description |
---|---|---|---|---|
Name | Type | Required | Example | Description |
---|---|---|---|---|
Name | Type | Required | Example Value | Description |
---|---|---|---|---|
Name | Type | Required | Example value | Description |
---|---|---|---|---|
Name | Type | Required | Example Value | Description |
---|---|---|---|---|
Name | Type | Required | Example Value | Description |
---|---|---|---|---|
Name | Type | Required | Example value | Description |
---|---|---|---|---|
Name | Type | Required | Example Value | Description |
---|---|---|---|---|
Name | Type | Required | Example Value | Description |
---|---|---|---|---|
Name | Type | Required | Example Value | Description |
---|---|---|---|---|
we only support hex (base16) encoding (i.e.: hashed values are carried by strings with [0-9a-f] characters) Other encodings are not supported yet
Property | Value |
---|---|
Property | Value |
---|---|
Name | Type | Required | Example Value | Description |
---|---|---|---|---|
Name | Type | Required | Example value | Description |
---|---|---|---|---|
Name | Type | Required | Example Value | Description |
---|---|---|---|---|
Name | Type | Required | Example Value | Description |
---|---|---|---|---|
Name | Type | Required | Example Value | Description |
---|---|---|---|---|
Name | Type | Required | Example Value | Description |
---|---|---|---|---|
Name | Type | Required | Example | Description |
---|---|---|---|---|
Name | Type | Required | Example Value | Description |
---|---|---|---|---|
Name | Type | Required | Example Value | Description |
---|---|---|---|---|
Name | Type | Required | Example | Description |
---|---|---|---|---|
Name | Type | Required | Example | Description |
---|---|---|---|---|
Name | Type | Required | Example | Description |
---|---|---|---|---|
Name | Type | Required | Example | Description |
---|---|---|---|---|
Name | Type | Required | Example Value | Description |
---|---|---|---|---|
Name | Type | Required | Example value | Description |
---|---|---|---|---|
Name | Type | Required | Example value | Description |
---|---|---|---|---|
Name | Type | Required | Example value | Description |
---|---|---|---|---|
Name | Type | Required | Example | Description |
---|---|---|---|---|
Name | Type | Required | Example Value | Description |
---|---|---|---|---|
Name | Type | Required | Example Value | Description |
---|---|---|---|---|
Name | Type | Required | Example value | Description |
---|---|---|---|---|
Name | Type | Required | Example | Description |
---|---|---|---|---|
Name | Type | Required | Example Value | Description |
---|---|---|---|---|
Name | Type | Required | Example Value | Description |
---|---|---|---|---|
we only support hex (base16) encoding (i.e.: hashed values are carried by strings with [0-9a-f] characters) Other encodings are not supported yet
Property | Value |
---|---|
Property | Value |
---|---|
Name | Type | Required | Example value | Description |
---|
Property | Type | Required | Description |
---|
Property | Type | Required | Description |
---|
For more information on each of the properties associated with these events, refer to the section.
Property | Type | Required | Description |
---|
Property | Type | Required | Description |
---|
For more information on each of the properties associated with these events, refer to the section.
payment_method
string
Yes
card
The chosen method of payment (see list of possible values below)
user
Yes
{
id: '12345',
email: 'toto@domain.fr',
consent_categories: [1,3]
}
consent_categories
is the user's consents list and is mandatory to manage consents. It is automatically filled from web sources if you use Commanders Act CMP.
You should also add all user's properties in this user object, especially reconciliation key (id, email).
coupon
string
No
CHRISTMAS
Coupon code used for a purchase.
revenue
number
No
16.00
Revenue (shipping price and taxes excluded) after discount.
()revenue
is typically required for meaningful reporting.
()currency
is required if you set revenue
.
currency
string (ISO 4217)
No
EUR
Currency of the purchase or items associated with the event, in 3-letter ISO 4217 format.
(*) If you supply the revenue
parameter, you must also supply the currency
parameter so revenue metrics can be computed accurately.
items
No
The items for the event.
currency
string (ISO 4217)
Yes
EUR
Currency of the purchase or items associated with the event, in 3-letter ISO 4217 format.
(*) If you supply the revenue
or value
parameter, you must also supply the currency
parameter so revenue metrics can be computed accurately.
value
number
Yes
22.53
The monetary value of the event (shipping price and taxes included) after discount
user
Yes
{
id: '12345',
email: 'toto@domain.fr',
consent_categories: [1,3]
}
consent_categories
is the user's consents list. It is automatically filled from web sources if you use Commanders Act CMP.
You should also add all user's properties in this user object, especially reconciliation key (id, email).
coupon
string
No
CHRISTMAS
Coupon code used for a purchase.
shipping_tier
string
No
Ground
The shipping tier (e.g. Next-day
, Air`) selected for delivery of the purchased item.
items
Yes
The items for the event.
value
number
Yes*
8.00
The monetary value of the event.
()value
is typically required for meaningful reporting.
()currency
is required if you set value
.
currency
string (ISO 4217)
Yes*
EUR
Currency of the purchase or items associated with the event, in 3-letter ISO 4217 format.
(*) If you supply the revenue
parameter, you must also supply the currency
parameter so revenue metrics can be computed accurately.
user
Yes
{
id: '12345',
email: 'toto@domain.fr',
consent_categories: [1,3]
}
consent_categories
is the user's consents list. It is automatically filled from web sources if you use Commanders Act CMP.
You should also add all user's properties in this user object, especially reconciliation key (id, email).
items
Yes
The items for the event.
value
number
No
8.00
The monetary value of the event.
()revenue
is typically required for meaningful reporting.
()currency
is required if you set revenue
.
currency
string (ISO 4217)
No
EUR
Currency of the purchase or items associated with the event, in 3-letter ISO 4217 format.
(*) If you supply the revenue
parameter, you must also supply the currency
parameter so revenue metrics can be computed accurately.
user
Yes
{
id: '12345',
email: 'toto@domain.fr',
consent_categories: [1,3]
}
consent_categories
is the user's consents list. It is automatically filled from web sources if you use Commanders Act CMP.
You should also add all user's properties in this user object, especially reconciliation key (id, email).
items
Yes
The items for the event.
revenue
number
Yes
16.00
The monetary value of the event (shipping price and taxes excluded) after discount
value
number
Yes
22.53
The monetary value of the event (shipping price and taxes included) after discount
currency
string (ISO 4217)
Yes
EUR
Currency of the purchase or items associated with the event, in 3-letter ISO 4217 format.
(*) If you supply the revenue
parameter, you must also supply the currency
parameter so revenue metrics can be computed accurately.
coupon
string
No
CHRISTMAS
Coupon code used for a purchase.
user
Yes
{
id: '12345',
email: 'toto@domain.fr',
consent_categories: [1,3]
}
consent_categories
is the user's consents list. It is automatically filled from web sources if you use Commanders Act CMP.
You should also add all user's properties in this user object, especially reconciliation key (id, email).
items
Yes
The items for the event.
value
number
No*
9.99
The monetary value of the event.
()revenue
is typically required for meaningful reporting.
()currency
is required if you set revenue
.
currency
string (ISO 4217)
No*
EUR
Currency of the purchase or items associated with the event, in 3-letter ISO 4217 format.
(*) If you supply the revenue
parameter, you must also supply the currency
parameter so revenue metrics can be computed accurately.
id
string
No
Lead id
user
Yes
{
id: '12345',
email: 'toto@domain.fr',
consent_categories: [1,3]
}
consent_categories
is the user's consents list. It is automatically filled from web sources if you use Commanders Act CMP.
You should also add all user's properties in this user object, especially reconciliation key (id, email).
id
string
Yes
O_1245
Transaction id. Used as key for updates
user
Yes
{
id: '12345',
email: 'toto@domain.fr',
consent_categories: [1,3]
}
All properties that you add here will be used as conditions for matching users in our database.
cosent_categories
is automatically filled if you use Commanders Act CMP.
revenue
number
Yes
16.00
The monetary value of the event (shipping price and taxes excluded) after discount
value
number
Yes
22.53
The monetary value of the event (shipping price and taxes included) after discount
shipping_amount
number
No
3.33
Shipping cost associated with a transaction.
tax_amount
number
No
3.20
Tax associated with a transaction.
currency
string (ISO 4217)
Yes
EUR
Currency of the purchase or items associated with the event, in 3-letter ISO 4217 format.
coupon
string
No
CHRISTMAS
Coupon code used for a purchase.
type
string
Yes
offline
Type of conversion (online, offline, call etc.)
items
Yes
The items for the event.
payment_method
string
Yes
card
Payment method type (see list of possible values below)
status
string
Yes
in_progress
Status of the conversion (see list of possible values below). Conversions with status "pending" are not included in default sum and counts aggregated on augmented user attributes feature
last_channel
string
No
display
The last channel just before the purchase.
last_source
string
No
google.com
The last source (referrer) just before the purchase.
url
string(url)
No
none
URL to the website where you can buy the item
Equivalent to window.location.href
id
string
Yes
O_1245
Transaction id. Used as key for updates
user
Yes
{
id: '12345',
email: 'toto@domain.fr',
consent_categories: [1,3]
}
All properties that you add here will be used as conditions for matching users in our database.
cosent_categories
is automatically filled if you use Commanders Act CMP.
revenue
number
Yes
16.00
The monetary value of the event (shipping price and taxes excluded) after discount
value
number
Yes
22.53
The monetary value of the event (shipping price and taxes included) after discount
shipping_amount
number
No
3.33
Shipping cost associated with a transaction.
tax_amount
number
No
3.20
Shipping cost associated with a transaction.
currency
string (ISO 4217)
Yes
EUR
Currency of the purchase or items associated with the event, in 3-letter ISO 4217 format.
coupon
string
No
CHRISTMAS
Coupon code used for a purchase.
type
string
Yes
offline
Type of conversion (online, offline, call etc.)
items
No*
(*) items
is required for partial refunds but it can be omitted for full refunds.
url
string(url)
No
none
URL to the website where you can buy the item
Equivalent to window.location.href
value
number
No
8.00
The monetary value of the event.
()value
is typically required for meaningful reporting.
()currency
is required if you set value
.
currency
string (ISO 4217)
No
EUR
Currency of the purchase or items associated with the event, in 3-letter ISO 4217 format.
(*) If you supply the revenue
parameter, you must also supply the currency
parameter so revenue metrics can be computed accurately.
user
Yes
{
id: '12345',
email: 'toto@domain.fr',
consent_categories: [1,3]
}
consent_categories
is the user's consents list. It is automatically filled from web sources if you use Commanders Act CMP.
You should also add all user's properties in this user object, especially reconciliation key (id, email).
items
Yes
The items for the event.
item_list_name
string
No
Related products
The name of the list in which the item was presented to the user.
items
Yes
The items for the event. The items
array is expected to have a single element, representing the selected item.
value
number
No
8.00
The monetary value of the event.
()value
is typically required for meaningful reporting.
()currency
is required if you set value
.
currency
string (ISO 4217)
No
EUR
Currency of the purchase or items associated with the event, in 3-letter ISO 4217 format.
(*) If you supply the revenue
parameter, you must also supply the currency
parameter so revenue metrics can be computed accurately.
user
Yes
{
id: '12345',
email: 'toto@domain.fr',
consent_categories: [1,3]
}
consent_categories
is the user's consents list. It is automatically filled from web sources if you use Commanders Act CMP.
You should also add all user's properties in this user object, especially reconciliation key (id, email).
items
Yes
The items for the event.
revenue
number
Yes*
9.99
The monetary value of the event.
()revenue
is typically required for meaningful reporting.
()currency
is required if you set revenue
.
currency
string (ISO 4217)
Yes*
EUR
Currency of the purchase or items associated with the event, in 3-letter ISO 4217 format.
user
Yes
{
id: '12345',
email: 'toto@domain.fr',
consent_categories: [1,3]
}
consent_categories
is the user's consents list. It is automatically filled from web sources if you use Commanders Act CMP.
You should also add all user's properties in this user object, especially reconciliation key (id, email).
items
Yes
The items for the event.
item_list_name
string
No
Related products
The name of the list in which the item was presented to the user.
user
Yes
{
id: '12345',
email: 'toto@domain.fr',
consent_categories: [1,3]
}
consent_categories
is the user's consents list. It is automatically filled from web sources if you use Commanders Act CMP.
You should also add all user's properties in this user object, especially reconciliation key (id, email).
items
Yes
The items for the event.
id
string
Yes
SKU_12345
The ID of an item.
If you don't have an item id, you can use the product id as value. This field is used as key for updates (ex : refund)
product
Yes
The product details
variant
string
No
red
The variant of the item.
list_position
number
No
1
The item's position in a list or collection.
discount
number
No
2.00
Monetary value of discount associated with a purchase
quantity
number
Yes
2
The quantity of the item.
affiliation
string
No*
DOWNLOAD
Required for most affiliation's destination.
coupon
string
No
CHRISTMAS
The coupon code associated with an item.
id
string
Yes*
12345
The ID of the product (ex: in your product catalog database)
The item.id
and product.id
do not have to be different. If they are different, typically the product.id
is a database identifier, like 9714107479
and the item.id
is a public-facing identifier like SKU-12345
.
(*) If you have imported your product's catalog in the platform, the product.id
corresponds to the unique product id in the catalog and can be used with id expansion feature.
name
string
Yes
Trex
Product name
price
number
Yes
14.99
The price of the product
currency
string (ISO 4217)
No
EUR
Currency of the price
, in 3-letter ISO 4217 format.
If set, event-level currency
is ignored.
Multiple currencies per event is not supported. Each item should set the same currency.
category_1
string
No
T-Shirts
Product Category (context-specific). item_category2
through item_category5
can also be used if the product has many categories.
brand
string
No
Lacoste
Product brand
colors
Array[string]
No
[blue, white]
The color(s) of the product
size
string
No
128
Size of the article
id
string
No*
845454
User's main identifier (e.g. CRM id)
(*) required for many destinations and internal processing.
email
string
Yes*
john.doe@example.com
Email (plain value)
(*) required for many destinations and internal processing. Not required if email_sha256
is provided
email_md5
string
No*
8eb1b52... (size 32)
Email, hashed using MD5 algorithm. Not required if email
is provided (see below)
email_sha256
string
No*
836f82d... (size 64)
Email, hashed using SHA-256 algorithm. Not required if email
is provided (see below)
phone
string
No*
+33612345678
Phone number, E.164 format (*) required for some destinations.
firstname
string
No
John
First name
lastname
string
No
Doe
Last name
gender
string
No
m
Gender
f
for Female
m
for Male
birthdate
string
No
1970-01-01
Birth date, YYYY-MM-DD
format
city
string
No
Boston
City
state
string
No
Massachusetts
State
zipcode
string
No
02108
Zip code
country
string
No
USA
consent_categories
Array
Yes
[1,2,3]
User's consent categories. Necessary to grant data sharing with destination partners. It is automatically filled from web sources if you use Commanders Act CMP.
payment_method
by_invoice
payment_method
by_bank_transfer_in_advance
payment_method
card
payment_method
check_in_advance
payment_method
cod
payment_method
coupon
payment_method
direct_debit
payment_method
online_payment_system
payment_method
other
status
canceled
status
delivered
status
in_progress
status
partially_delivered
status
partially_returned
status
partially_shipped
status
pending_shipment
status
returned
status
shipped
status
pending
payment_method
string
Yes
card
The chosen method of payment (see list of possible values below)
user
Yes
{
id: '12345',
email: 'toto@domain.fr',
consent_categories: [1,3]
}
consent_categories
is the user's consents list and is mandatory to manage consents. It is automatically filled from web sources if you use Commanders Act CMP.
You should also add all user's properties in this user object, especially reconciliation key (id, email).
coupon
string
No
CHRISTMAS
Coupon code used for a purchase.
revenue
number
No
16.00
Revenue (shipping price and taxes excluded) after discount.
()revenue
is typically required for meaningful reporting.
()currency
is required if you set revenue
.
currency
string (ISO 4217)
No
EUR
Currency of the purchase or items associated with the event, in 3-letter ISO 4217 format.
(*) If you supply the revenue
parameter, you must also supply the currency
parameter so revenue metrics can be computed accurately.
items
No
The items for the event.
currency
string (ISO 4217)
Yes
EUR
Currency of the purchase or items associated with the event, in 3-letter ISO 4217 format.
(*) If you supply the revenue
or value
parameter, you must also supply the currency
parameter so revenue metrics can be computed accurately.
value
number
Yes
22.53
The monetary value of the event (shipping price and taxes included) after discount
user
Yes
{
id: '12345',
email: 'toto@domain.fr',
consent_categories: [1,3]
}
consent_categories
is the user's consents list. It is automatically filled from web sources if you use Commanders Act CMP.
You should also add all user's properties in this user object, especially reconciliation key (id, email).
coupon
string
No
CHRISTMAS
Coupon code used for a purchase.
shipping_tier
string
No
Ground
The shipping tier (e.g. Next-day
, Air`) selected for delivery of the purchased item.
items
Yes
The items for the event.
value
number
Yes*
8.00
The monetary value of the event.
()value
is typically required for meaningful reporting.
()currency
is required if you set value
.
currency
string (ISO 4217)
Yes*
EUR
Currency of the purchase or items associated with the event, in 3-letter ISO 4217 format.
(*) If you supply the revenue
parameter, you must also supply the currency
parameter so revenue metrics can be computed accurately.
user
Yes
{
id: '12345',
email: 'toto@domain.fr',
consent_categories: [1,3]
}
consent_categories
is the user's consents list. It is automatically filled from web sources if you use Commanders Act CMP.
You should also add all user's properties in this user object, especially reconciliation key (id, email).
items
Yes
The items for the event.
value
number
No
8.00
The monetary value of the event.
()revenue
is typically required for meaningful reporting.
()currency
is required if you set revenue
.
currency
string (ISO 4217)
No
EUR
Currency of the purchase or items associated with the event, in 3-letter ISO 4217 format.
(*) If you supply the revenue
parameter, you must also supply the currency
parameter so revenue metrics can be computed accurately.
user
Yes
{
id: '12345',
email: 'toto@domain.fr',
consent_categories: [1,3]
}
consent_categories
is the user's consents list. It is automatically filled from web sources if you use Commanders Act CMP.
You should also add all user's properties in this user object, especially reconciliation key (id, email).
items
Yes
The items for the event.
revenue
number
Yes
16.00
The monetary value of the event (shipping price and taxes excluded) after discount
value
number
Yes
22.53
The monetary value of the event (shipping price and taxes included) after discount
currency
string (ISO 4217)
Yes
EUR
Currency of the purchase or items associated with the event, in 3-letter ISO 4217 format.
(*) If you supply the revenue
parameter, you must also supply the currency
parameter so revenue metrics can be computed accurately.
coupon
string
No
CHRISTMAS
Coupon code used for a purchase.
user
Yes
{
id: '12345',
email: 'toto@domain.fr',
consent_categories: [1,3]
}
consent_categories
is the user's consents list. It is automatically filled from web sources if you use Commanders Act CMP.
You should also add all user's properties in this user object, especially reconciliation key (id, email).
items
Yes
The items for the event.
value
number
No*
9.99
The monetary value of the event.
()revenue
is typically required for meaningful reporting.
()currency
is required if you set revenue
.
currency
string (ISO 4217)
No*
EUR
Currency of the purchase or items associated with the event, in 3-letter ISO 4217 format.
(*) If you supply the revenue
parameter, you must also supply the currency
parameter so revenue metrics can be computed accurately.
id
string
No
Lead id
user
Yes
{
id: '12345',
email: 'toto@domain.fr',
consent_categories: [1,3]
}
consent_categories
is the user's consents list. It is automatically filled from web sources if you use Commanders Act CMP.
You should also add all user's properties in this user object, especially reconciliation key (id, email).
method
string
No
The method used to login.
user
Yes
{
id: '12345',
email: 'toto@domain.fr',
consent_categories: [1,3]
}
consent_categories
is the user's consents list. It is automatically filled from web sources if you use Commanders Act CMP.
You should also add all user's properties in this user object, especially reconciliation key (id, email).
page_type
string
Yes
product_list
Page category. Recommanded predefined types:
home
landing
product_list
product
content_list
content
search
funnel
success
funnel_confirmation
account
cart
legal (e.g. Privacy Policy)
Equivalent to tc_vars.env_template
page_name
string
No
Suggestion for Mother's Day
Name of the page.
user
Yes
{
id: '12345',
email: 'toto@domain.fr',
consent_categories: [1,3]
}
consent_categories
is the user's consents list. It is automatically filled from web sources if you use Commanders Act CMP.
You should also add all user's properties in this user object, especially reconciliation key (id, email).
user
Yes
{
id: '12345',
email: 'toto@domain.fr',
consent_categories: [1,3]
}
consent_categories
is the user's consents list. It is automatically filled from web sources if you use Commanders Act CMP.
You should also add all user's properties in this user object, especially reconciliation key (id, email).
title
string
No
Products - MySite.com
Title of the page :document.title
from the DOM API
url
string
No
Full URL of the page. Equivalent tolocation.href
from the DOM API.
path
string
No
/products/mothers
Path portion of the URL of the page : location.pathname
from the DOM API.
referrer
string
No
Full URL of the previous page : document.referrer
from the DOM API.
id
string
Yes
O_1245
Transaction id. Used as key for updates
user
Yes
{
id: '12345',
email: 'toto@domain.fr',
consent_categories: [1,3]
}
All properties that you add here will be used as conditions for matching users in our database.
cosent_categories
is automatically filled if you use Commanders Act CMP.
revenue
number
Yes
16.00
The monetary value of the event (shipping price and taxes excluded) after discount
value
number
Yes
22.53
The monetary value of the event (shipping price and taxes included) after discount
shipping_amount
number
No
3.33
Shipping cost associated with a transaction.
tax_amount
number
No
3.20
Tax associated with a transaction.
currency
string (ISO 4217)
Yes
EUR
Currency of the purchase or items associated with the event, in 3-letter ISO 4217 format.
coupon
string
No
CHRISTMAS
Coupon code used for a purchase.
type
string
Yes
offline
Type of conversion (online, offline, call etc.)
items
Yes
The items for the event.
payment_method
string
Yes
card
Payment method type (see list of possible values below)
status
string
Yes
in_progress
Status of the conversion (see list of possible values below). Conversions with status "pending" are not included in default sum and counts aggregated on augmented user attributes feature
url
string(url)
No
none
URL to the website where you can buy the item
Equivalent to window.location.href
id
string
Yes
O_1245
Transaction id. Used as key for updates
user
Yes
{
id: '12345',
email: 'toto@domain.fr',
consent_categories: [1,3]
}
All properties that you add here will be used as conditions for matching users in our database.
cosent_categories
is automatically filled if you use Commanders Act CMP.
revenue
number
Yes
16.00
The monetary value of the event (shipping price and taxes excluded) after discount
value
number
Yes
22.53
The monetary value of the event (shipping price and taxes included) after discount
shipping_amount
number
No
3.33
Shipping cost associated with a transaction.
tax_amount
number
No
3.20
Shipping cost associated with a transaction.
currency
string (ISO 4217)
Yes
EUR
Currency of the purchase or items associated with the event, in 3-letter ISO 4217 format.
coupon
string
No
CHRISTMAS
Coupon code used for a purchase.
type
string
Yes
offline
Type of conversion (online, offline, call etc.)
items
No*
(*) items
is required for partial refunds but it can be omitted for full refunds.
url
string(url)
No
none
URL to the website where you can buy the item
Equivalent to window.location.href
value
number
No
8.00
The monetary value of the event.
()value
is typically required for meaningful reporting.
()currency
is required if you set value
.
currency
string (ISO 4217)
No
EUR
Currency of the purchase or items associated with the event, in 3-letter ISO 4217 format.
(*) If you supply the revenue
parameter, you must also supply the currency
parameter so revenue metrics can be computed accurately.
user
Yes
{
id: '12345',
email: 'toto@domain.fr',
consent_categories: [1,3]
}
consent_categories
is the user's consents list. It is automatically filled from web sources if you use Commanders Act CMP.
You should also add all user's properties in this user object, especially reconciliation key (id, email).
items
Yes
The items for the event.
search_term
string
Yes
t-shirts
The term that was searched for.
user
Yes
{
id: '12345',
email: 'toto@domain.fr',
consent_categories: [1,3]
}
consent_categories
is the user's consents list. It is automatically filled from web sources if you use Commanders Act CMP.
You should also add all user's properties in this user object, especially reconciliation key (id, email).
content_type
string
No
product
The type of selected content.
item_id
string
No
I_12345
An identifier for the item that was selected.
user
Yes
{
id: '12345',
email: 'toto@domain.fr',
consent_categories: [1,3]
}
consent_categories
is the user's consents list. It is automatically filled from web sources if you use Commanders Act CMP.
You should also add all user's properties in this user object, especially reconciliation key (id, email).
item_list_name
string
No
Related products
The name of the list in which the item was presented to the user.
items
Yes
The items for the event. The items
array is expected to have a single element, representing the selected item.
method
string
No
The method used for sign up.
user
Yes
{
id: '12345',
email: 'toto@domain.fr',
consent_categories: [1,3]
}
consent_categories
is the user's consents list. It is automatically filled from web sources if you use Commanders Act CMP.
You should also add all user's properties in this user object, especially reconciliation key (id, email).
value
number
No
8.00
The monetary value of the event.
()value
is typically required for meaningful reporting.
()currency
is required if you set value
.
currency
string (ISO 4217)
No
EUR
Currency of the purchase or items associated with the event, in 3-letter ISO 4217 format.
(*) If you supply the revenue
parameter, you must also supply the currency
parameter so revenue metrics can be computed accurately.
user
Yes
{
id: '12345',
email: 'toto@domain.fr',
consent_categories: [1,3]
}
consent_categories
is the user's consents list. It is automatically filled from web sources if you use Commanders Act CMP.
You should also add all user's properties in this user object, especially reconciliation key (id, email).
items
Yes
The items for the event.
revenue
number
Yes*
9.99
The monetary value of the event.
()revenue
is typically required for meaningful reporting.
()currency
is required if you set revenue
.
currency
string (ISO 4217)
Yes*
EUR
Currency of the purchase or items associated with the event, in 3-letter ISO 4217 format.
user
Yes
{
id: '12345',
email: 'toto@domain.fr',
consent_categories: [1,3]
}
consent_categories
is the user's consents list. It is automatically filled from web sources if you use Commanders Act CMP.
You should also add all user's properties in this user object, especially reconciliation key (id, email).
items
Yes
The items for the event.
item_list_name
string
No
Related products
The name of the list in which the item was presented to the user.
user
Yes
{
id: '12345',
email: 'toto@domain.fr',
consent_categories: [1,3]
}
consent_categories
is the user's consents list. It is automatically filled from web sources if you use Commanders Act CMP.
You should also add all user's properties in this user object, especially reconciliation key (id, email).
items
Yes
The items for the event.
id
string
Yes
SKU_12345
The ID of an item.
If you don't have an item id, you can use the product id as value. This field is used as key for updates (ex : refund)
product
Yes
The product details
variant
string
No
red
The variant of the item.
list_position
number
No
1
The item's position in a list or collection.
discount
number
No
2.00
Monetary value of discount for one current item
quantity
number
Yes
2
The quantity of the item.
affiliation
string
No*
DOWNLOAD
Required for most affiliation's destination.
coupon
string
No
CHRISTMAS
The coupon code associated with an item.
id
string
Yes*
12345
The ID of the product (ex: in your product catalog database)
The item.id
and product.id
do not have to be different. If they are different, typically the product.id
is a database identifier, like 9714107479
and the item.id
is a public-facing identifier like SKU-12345
.
(*) If you have imported your product's catalog in the platform, the product.id
corresponds to the unique product id in the catalog and can be used with id expansion feature.
name
string
Yes
Trex
Product name
price
number
Yes
14.99
The price of the product (taxes and discount excluded)
currency
string (ISO 4217)
No
EUR
Currency of the price
, in 3-letter ISO 4217 format.
If set, event-level currency
is ignored.
Multiple currencies per event is not supported. Each item should set the same currency.
category_1
string
No
T-Shirts
Product Category (context-specific). item_category2
through item_category5
can also be used if the product has many categories.
brand
string
No
Lacoste
Product brand
colors
Array[string]
No
[blue, white]
The color(s) of the product
size
string
No
128
Size of the article
id
string
No*
845454
User's main identifier (e.g. CRM id)
(*) required for many destinations and internal processing.
email
string
Yes*
john.doe@example.com
Email (plain value)
(*) required for many destinations and internal processing. Not required if email_sha256
is provided
email_md5
string
No*
8eb1b52... (size 32)
Email, hashed using MD5 algorithm. Not required if email
is provided (see below)
email_sha256
string
No*
836f82d... (size 64)
Email, hashed using SHA-256 algorithm. Not required if email
is provided (see below)
phone
string
No*
+33612345678
Phone number, E.164 format (*) required for some destinations.
firstname
string
No
John
First name
lastname
string
No
Doe
Last name
gender
string
No
m
Gender
f
for Female
m
for Male
birthdate
string
No
1970-01-01
Birth date, YYYY-MM-DD
format
city
string
No
Boston
City
state
string
No
Massachusetts
State
street
string
No
303 Sumner St
Street address
zipcode
string
No
02108
Zip code
country
string
No
USA
consent_categories
Array
Yes
[1,3,4]
User's consent categories. It should contain only the categories where the user has given his consent. Necessary to grant data sharing with destination partners. It is automatically filled from web sources if you use Commanders Act CMP.
status
string
No
New
Status as reported in your CRM (E.g. "New", "Existing", "Premium")
payment_method
by_invoice
payment_method
by_bank_transfer_in_advance
payment_method
card
payment_method
check_in_advance
payment_method
cod
payment_method
coupon
payment_method
direct_debit
payment_method
online_payment_system
payment_method
other
status
canceled
status
delivered
status
in_progress
status
partially_delivered
status
partially_returned
status
partially_shipped
status
pending_shipment
status
returned
status
shipped
status
pending
|
| Yes | A unique ID that ties all the events generated from a specific playback session. These events include playback, content, and ad events. |
|
| No | Denotes the title of the video content. |
|
| No | Denotes the genre of the video content asset. |
|
| No | Denotes the publisher / creator / author of the video content asset. |
|
| Yes | Content asset ID/s of the video/s playing or about to be played. For of unique asset IDs should be sent. For other playback events, a singular content asset ID at the time of the event should be sent. |
|
| No | Content pod ID/s of the video/s playing or about to be played. For of unique pod IDs should be sent. For other playback events, a singular content pod ID associated with the current content pod at the time of the event should be sent. |
|
| No | Ad asset ID/s of the video/s playing or about to be played. For of unique ad asset IDs should be sent. For other playback events, a singular ad asset ID at the time of the event should be sent. |
|
| No | Ad pod ID/s of the video/s playing or about to be played. For of unique ad pod IDs should be sent. For other playback events, a singular content pod ID associated with the current ad pod at the time of the event should be sent. |
|
| No | Denotes the type of ad playing at the time of the event. The values can be ' ' |
|
| Yes | Denotes the current index position of the playhead
in seconds. It includes the duration of any seen ads.
Not required in |
|
| No | Denotes the index position of the playhead where the user is seeking to. Only applicable on the the |
|
| Yes | Denotes the total duration of the video playback in seconds. Includes the whole duration of all the content and ads included in the session. Set to |
|
| No | Bit rate of the video playback, denoted in |
|
| No | Denotes the average frame rate of the video
playback in |
|
| No | Denotes the name of the video player used for playback. Example: |
|
| No | Denotes the sound level of the video playback. Range is from 0-100, where 0 represents mute and 100 is full volume. |
|
| No | Set to |
|
| No | Set to If the user can view your video ads, it is set to
|
|
| No | Specifies the quality of the video. Examples: 'hd1080', 'highres' |
|
| No | For the playback was interrupted. Some examples include 'device_lock', 'call', and 'browser_redirect'. |
|
| No | Set to |
|
| Yes | A unique ID that ties all the events generated from a specific playback session. These events include playback, content, and ad events. |
|
| Yes | Denotes the unique ID of the video content asset. |
|
| No | Denotes the unique ID of the video content pod. |
|
| No | Denotes the title of the video content. |
|
| No | Describes the video content asset in short. |
|
| No | Denotes the relevant keywords associated with the categorizing the video content |
|
| No | Denotes the season number, if applicable. |
|
| No | Denotes the episode number, if applicable. |
|
| No | Denotes the genre of the video content asset. |
|
| No | Denotes the name of the program / show of which the video content is a part. |
|
| No | Denotes the publisher / creator / author of the video content asset. |
|
| No | Denotes the channel in which the video content is playing. |
|
| No | Set to |
| Boolean | No | If the video content is a live stream, this is set to
|
|
| No | Denotes the original date of airing / publishing the video content. |
|
| Yes | Denotes the current playhead position into the video content in seconds. This does not include any ads played in this duration. In case of live streams, refer to the relevant destination's documentation for details on how to pass this property. |
|
| Yes | The total duration of the video content in seconds. This does not include any ads included in the playback of this content asset. For livestream playback, this should be set to |
|
| No | Denotes the current bit rate in |
|
| No | Denotes the frame rate in |
|
| Yes | A unique ID that ties all the events generated from a specific playback session. These events include playback, content, and ad events. |
|
| Yes | Denotes the unique ID of the ad asset. |
|
| Yes | Denotes the unique ID of the ad pod. |
|
| No | Denotes the position of the ad asset relative to other ads in the same pod. |
|
| No | Denotes the type of ad playing at the time of the event. The values can be ' ' |
|
| No | Denotes the number of ad assets in the current ad pod. |
|
| No | Denotes the title of the ad. |
|
| No | Denotes the author/ creator/ publisher of the ad. |
|
| Yes | The current playhead position in relation to the total length of the ad, in seconds. |
|
| Yes | Denotes the total length of the ad asset in seconds. |
|
| No | Denotes if the ads are loaded dynamically or if they are the same for all the users.
Values can be either ' |
|
| No | For the can be used to indicate when a specific ad quartile is reached. If you are using a client-side library to track your video events, this property is optional as Commanders Act automatically tracks the ad quartiles. |
|
| Yes | A unique ID that ties all the events generated from a specific playback session. These events include playback, content, and ad events. |
|
| Yes | Denotes the unique ID of the video content asset. |
|
| No | Denotes the unique ID of the video content pod. |
|
| No | Denotes the unique ID of the ad asset. |
|
| No | Denotes the unique ID of the ad pod. |
|
| No | Denotes the type of ad playing at the time of the event. The values can be ' ' |
|
| No | Denotes the title of the video content. |
|
| No | Describes the video content asset in short. |
|
| No | Denotes the relevant keywords associated with the categorizing the video content |
|
| No | Denotes the season number, if applicable. |
|
| No | Denotes the episode number, if applicable. |
|
| No | Denotes the genre of the video content asset. |
|
| No | Denotes the name of the program / show of which the video content is a part. |
|
| No | Denotes the publisher / creator / author of the video content asset. |
|
| No | Denotes the channel in which the video content is playing. |
|
| No | Set to |
|
| No | If the video content is a live stream, this is set to
|
|
| No | Denotes the original date of airing / publishing the video content. |
|
| Yes | Denotes the current playhead position into the video content in seconds. This does not include any ads played in this duration. In case of live streams, refer to the relevant destination's documentation for details on how to pass this property. |
|
| Yes | The total duration of the video content in seconds. This does not include any ads included in the playback of this content asset. For livestream playback, this should be set to |
|
| Yes | Denotes the current bit rate in |
|
| No | Denotes the frame rate in |
|
| Yes | Denotes the current video sound level Required in |
|
| Yes | Denotes the current video screen mode.
Required in |
|
| No | Denotes if ad were enabled |
|
| Yes | Denotes the current video queity resolution.
Required in |
|
| No | 1254965 | replace the |
| Yes |
|
You should also add all user's properties in this user object, especially reconciliation key (id, email). |
|
| No | image | Ad type/format |
|
| No | my_campaign | campaign name |
|
| No | t-shirt | keywords of the campaign |
|
| Yes | seo | medium of touch point |
|
| Yes | my_source | source of touch point |