For more information on how to pull reports, refer to our Pulling Reports support documentation.
NOTE: The Click, Event and Install reports are fully customizable allowing the user to decide which data is present and the order that the data is presented within the report. For more information about customizing the Click, Event and Install reports, refer to our Pulling Reports support documentation.
NOTE: Detail Reports that exceed 5.0 gigabytes in size will be compressed to enable accelerated download.
NOTE: For a sample of each of the reports listed below, download our KochavaReportsDemo document.
NOTE: There are several sources of Restricted data you will see across views in Query, Reporting and Analytics. This is data the media channel prohibits Kochava from sharing at the row level, but you will find the channel information contained in your summary reporting. Please reach out to your Kochava Client Success Management Team for more information.
Audience Export
The Audience Export report provides a list of audience device IDs in either CSV or JSON format based upon audience filter setup with Analytics. Audience Export reports can be setup as a onetime report or repeatedly on a daily, weekly or monthly basis.
NOTE: For more information about creating filters within Kochava Analytics, refer to our Analytics Page Tools support documentation.
NOTE: Fore more information about pulling a Audience Export report, refer to out Pulling Reports support documentation.
The Click Report provides a row-level view of clicks for a given campaign.
Field Name | Description |
Type
|
May be Null
|
---|---|---|---|
The Kochava-specific ID of the campaign to which the click was attributed. | |||
The user defined name for the campaign to which the click was attributed. | ✔ | ||
2-digit country designation where the click originated, based on IP lookup. | ✔ | ||
Data received on click in the creative_id parameter. | ✔ | ||
click_custom_parameters | Custom parameters passed with the click. | ||
Date and time of the click (Selected Time Zone). | |||
Date and time of the click (Coordinated Universal Time). | |||
An internal identifier used for mapping purposes. | ✔ | ||
User Agent of the device gathered upon click. | ✔ | ||
The device type and version of the device received on click. | ✔ | ||
The ID assigned to duplicate clicks. | ✔ | ||
An array of all device identifiers received on the click. | ✔ | ||
Raw ADID provided on the click (Android specific). | ✔ | ||
Raw Android_ID received on the click (Android specific). | ✔ | ||
MD5 encrypted Android_ID received on the click (Android specific). | ✔ | ||
SHA1 encrypted Android_ID received on the click (Android specific). | ✔ | ||
Custom provided identifier received with the click. | ✔ | ||
Primary email address delivered with the click. | ✔ | ||
Secondary email address delivered with the click. | ✔ | ||
Raw IDFA received on the click (iOS specific). | ✔ | ||
Raw IP address where the click originated. | ✔ | ||
Raw WAID received on the click (Windows specific). | ✔ | ||
The IP address from which the click originated. | |||
ID representation of the impression which the click was matched to. | ✔ | ||
ID representation of the install which matched to the click. | ✔ | ||
The Kochava-specific ID of the Network to which the click originated. | |||
The name of the Network to which the click originated. | ✔ | ||
Raw URL which was received for specific click.
NOTE: API call will return data in JSON format. |
✔ | ||
The price per click. | ✔ | ||
The total number of clicks generated from the qr code during the selected time frame. | |||
Identifies the site to which the click was served within the publisher partner. | ✔ | ||
Indicator to define if the click has simply been received (publish) or matched to an install. | |||
The tier/segment to which the click is associated. | ✔ | ||
The Kochava-specific ID of the tracker to which the click originated. | |||
The user defined name for the tracker to which the click originated. | ✔ | ||
The area code where the click originated, based on IP lookup. | ✔ | ||
The name of the city where the click originated, based on IP lookup. | ✔ | ||
The region where the click originated, based on IP lookup. | ✔ | ||
2-digit country designation where the click originated, based on IP lookup. | ✔ | ||
3-digit country designation where the click originated, based on IP lookup. | ✔ | ||
The name of the country where the click originated, based on IP lookup. | ✔ | ||
The code for the designated marketing area where the click originated, based on IP lookup. | ✔ | ||
The latitude where the click originated, based on IP lookup.
Latitude values are populated based on a 3rd party IP lookup service and are associated with a general city center location. |
✔ | ||
The longitude where the click originated, based on IP lookup.
Longitude values are populated based on a 3rd party IP lookup service and are associated with a general city center location. |
✔ | ||
The postal code of the region where the click originated, based on IP lookup. | ✔ | ||
An alpha-numeric code identifying the geographic region where the click originated, based on IP lookup. | ✔ | ||
The Kochava-specific ID of the campaign to which the click was attributed. | ✔ | ||
The user defined name for the campaign to which the click was attributed. | ✔ | ||
2-digit country designation where the impression originated, based on IP lookup. | ✔ | ||
Data received on impression in the creative_id parameter. | ✔ | ||
The date the impression occurred (Selected Time Zone). | ✔ | ||
The date the impression occurred in UTC. | ✔ | ||
The device type and version of the device received on impression. | ✔ | ||
An array of all device identifiers received on the impression. | ✔ | ||
Unique identifier associated with the impression which has been received. | ✔ | ||
The IP address from which the impression originated. | ✔ | ||
Kochava generated unique identifier associated with the impression which has been received. | ✔ | ||
ID representation of the click which the impression was matched to. | ✔ | ||
ID representation of the install which matched to the impression. | ✔ | ||
The Kochava-specific ID of the Network to which the impression originated. | ✔ | ||
The name of the Network to which the impression originated. | ✔ | ||
impression_original_request | Raw URL which was received for specific impression.
NOTE: API call will return data in JSON format. |
✔ | |
Identifies the site to which the impression was served within the publisher partner. | ✔ | ||
The Kochava-specific ID of the tracker to which the impression was attributed. | ✔ | ||
The user defined name for the tracker to which the click was attributed. | ✔ | ||
Click ID assigned by Kochava. | ✔ | ||
Click ID as received from the partner. | ✔ | ||
The tier/segment to which the reengagement is associated. | ✔ | ||
Indicator if the click traffic was valid or invalid based on Traffic Verification rules. | ✔ | ||
Indicator if the click traffic was valid or invalid based on Traffic Verification rules. | ✔ | ||
The device ATT status. | ✔ | ||
ATT status 1 – authorized ATT status 0 – |
✔ | ||
User response timestamp. | ✔ | ||
✔ |
NOTE: Some columns within the report may contain JSON encoded data. “_querystring” can be appended to the column name to provide a URL queryString encoded version of these columns. The JSON path for each value in the JSON will be used as the querystring key for that value.
The Click MTA Report provides a row-level view of the influencers that led to a click for a given campaign. (see iOS 14+ restrictions)
Field Name | Description |
Type
|
May be Null
|
---|---|---|---|
The internally generated unique ID to which the install is attributed. | |||
Date and time of install (Coordinated Universal Time). | |||
Date and time of install (Selected Time Zone). | |||
The ID of the click that won attribution. | |||
The ID of the network awarded the winning click. | |||
The name of the network awarded the winning click. | ✔ | ||
Identifies the site to which the winning click was served within the publisher partner. | ✔ | ||
The ID/name of the creative which drove the winning click. | ✔ | ||
Date and time of the winning click (Coordinated Universal Time). | |||
Date and time of the winning click (Selected Time Zone). | |||
Provides the actual piece of data that the click was matched on; that is, the device ID. | |||
The ID type to which the winning click is attributed. | |||
The total number of winning clicks generated from the qr code during the selected time frame. | |||
Unique identifier associated with the influencer which has been received. | |||
The ID of the network which influenced the winning click. | ✔ | ||
The name of the network which influenced the winning click. | ✔ | ||
Identifies the site to which the influencer was served within the publisher partner. | ✔ | ||
The ID/name of the creative which influenced the click. | ✔ | ||
Date and time the influencer was served (Coordinated Universal Time). | |||
Date and time the influencer was served (Selected Time Zone). | |||
Provides the actual piece of data the influencer was matched on; for example, the device ID. | |||
Description of how we matched the install to the influencer; for example, device ID, Facebook, etc | |||
Click ID assigned by Kochava. | ✔ | ||
The reason the install was attributed to another Network (for example, another network was credited with last-click).
device_id_inclusive – Reconciliation settings are set to default, the click had a mismatched device_id but would have been eligible to win attribution on fingerprint if inclusive had been set. fingerprint_equalizer_lookback – Fingerprint Equalizer was activated and the click would have been eligible to win attribution, but the click occurred outside the configured Fingerprint Equalizer lookback window. ip_disabled – The click would have been eligible to match on IP if that setting was enabled. last_click – The click was eligible to win attribution, but there was a more recent click closer to the install that won attribution. lookback_disabled – The click would have been eligible to match, but the lookback setting was disabled. lookback_enforced – The click would have matched but it occurred outside the configured lookback window (ex: click was at 10 days prior to the install but lookback was set to 9 days). partial_ip_disabled – The click would have been eligible to match on partial IP if that setting was enabled.
|
NOTE: Some columns within the report may contain JSON encoded data. These columns will have “*_querystring” versions that will provide a URL QueryString encoded version of these columns. The JSON path for each value in the JSON will be used as the querystring key for that value.
NOTE: exclude0rows has been added to the Traffic Including filter which removes rows without data which can significantly decreasing the size of this report.
Field Name | Description |
Type
|
May be Null
|
---|---|---|---|
The Kochava-specific ID of the Cost Configuration job. | |||
The user-defined name for the Cost Configuration. | |||
The network defined 24 hour period for the cost window. | |||
The UTC start date of the cost window. | |||
The UTC end date of the cost window. | |||
The ID of the company networks e.g., unity ios, unity android, etc., are all under the same ID. | |||
The name of the network the configuration is associated to. | |||
The device platform. | ✔ | ||
ad_account | The client advertiser account with the network company. | ✔ | |
The user-defined name to which the configuration is associated to at the network level. | |||
The user-defined ID of the campaign the configuration is associated to at the network level. | |||
The country code retrieved by Kochava from the network. | ✔ | ||
creative_name | The name representing the ad creative served by the network. | ✔ | |
The ID representing the ad creative served by the network. | ✔ | ||
The type of ad being served by the network. | ✔ | ||
ad_size | The dimensions of the ad being served by the network. | ✔ | |
site_name | The internal code (name or ID) used by the network for the site to which the campaign is associated to. | ✔ | |
The internal ID used by the network for the site to which the campaign is associated to. | ✔ | ||
The number of impressions associated with the configuration. | |||
The total number of clicks associated with the configuration. | |||
The total number of installs associated with the configuration. | |||
The total spend in the user-defined currency at the network level. | |||
The original currency for the associated configuration. | |||
The total spend in USD. | |||
network_timezone | The timezone reported by the network. | ||
collected_day_after | How many day after the cost date, Kochava retrieved the cost data. | ||
time_collected | The datetime when Kochava retrieved the cost data. | ||
sub_campaign_name | The name of the sub-campaign level layer as specified in the media partner’s dashboard. May represent ad group, ad set, line item, etc. | ||
sub_campaign_id | The ID of the sub-campaign level layer as specified in the media partner’s dashboard. May represent ad group, ad set, line item, etc. | ||
channel | Set at the network level and retrieved by Kochava. | ||
sub_site_id | The sub-site ID of the app where the ad was served, retrieved from the network. | ||
placement_id | The ID for the ad location within the app where the ad was served. | ||
keyword | Campaign keywords. | ||
keyword_id | The ID for the campaign keywords. | ||
bid_strategy | The bid strategy defined by the advertiser in the media partner’s dashboard. | ||
bid_type | Bid type set by the media partner. | ||
campaign_objective | Objective of campaign set in media partner dashboard. |
NOTE: exclude0rows has been added to the Traffic Including filter which removes rows without data which can significantly decreasing the size of this report.
Field Name | Description |
Type
|
May be Null
|
Filter
|
Group
|
---|---|---|---|---|---|
Unique identifier associated with the the campaign. Used to join the data sets and is normally the partner_campaign_id. This value may also be the partner_campaign_name in the absence of the partner_campaign_id. | ✔ | ||||
The user-defined name for the Cost Configuration at the network level. Multiple partner campaign names may be present within this field if more than one campaign name is tied to a partner_campaign_id. | ✔ | ✔ | |||
The numeric ID of the advertiser’s app in Kochava. | ✔ | ||||
The name of the advertiser’s app within Kochava. | ✔ | ||||
The numeric ID of the company network partner in Kochava. | ✔ | ||||
The name of the company network partner in Kochava. | ✔ | ✔ | |||
The total number of impressions for the associated configuration. | ✔ | ||||
The cost per thousand impressions. | ✔ | ||||
The total number of clicks for the associated configuration | ✔ | ||||
The cost per click. | ✔ | ||||
The click-through rate. | ✔ | ||||
The total number of installs for the associated configuration reported by the network. | ✔ | ||||
The cost per install. | ✔ | ||||
The conversion rate. | |||||
The total spend in USD for the associated configuration. | ✔ | ||||
Cost per Install using Kochava install count. | ✔ | ||||
Install count from Kochava measurement data. | ✔ | ||||
Count of all events found in Kochava measurement. | ✔ | ||||
Cost per Kochava event (total events). | ✔ | ||||
Distinct user count with an event in Kochava measurement. | ✔ | ||||
Count of revenue flagged events in Kochava measurement. | ✔ | ||||
Distinct user count with a revenue flagged event. | ✔ | ||||
Average value for revenue flagged events. | ✔ | ||||
Average revenue value per distinct user with a revenue event. | ✔ | ||||
Sum of event value sent on revenue events in USD. | ✔ | ||||
Total revenue USD – total spend USD/ total revenue USD | ✔ | ||||
total revenue USD / total spend USD | ✔ | ||||
Latest event value sent on custom LTV event. | ✔ |
* Revenue must be added to Traffic Includes.
** LTV must be added to Traffic Includes.
NOTE: exclude0rows has been added to the Traffic Including filter which removes rows without data which can significantly decreasing the size of this report.
Field Name | Description |
Type
|
May be Null
|
Filter
|
Group
|
---|---|---|---|---|---|
Unique identifier associated with the the campaign. Used to join the data sets and is normally the partner_campaign_id. This value may also be the partner_campaign_name in the absence of the partner_campaign_id. | |||||
The user-defined name for the Cost Configuration at the network level. Multiple partner campaign names may be present within this field if more than one campaign name is tied to a partner_campaign_id. | ✔ | ✔ | |||
The numeric ID of the integrated cost company network partner in Kochava. | ✔ | ||||
The name of the integrated cost company network partner in Kochava. | ✔ | ✔ | |||
SKAd report host name | ✔ | ||||
The numeric ID of the advertiser’s app in Kochava. | ✔ | ||||
The name of the advertiser’s app within Kochava. | ✔ | ||||
Count of SKAdNetwork-reported installs. | ✔ | ||||
Count of SKAdNetwork-reported installs that were flagged as redownloads by SKAdNetwork. | ✔ | ||||
The original currency for the associated configuration. | ✔ | ||||
The total number of impressions for the associated configuration retrieved from the network. | ✔ | ||||
The total number of clicks for the associated configuration retrieved from the network. | ✔ | ||||
The total number of installs for the associated configuration reported by the network. | ✔ | ||||
The total spend in the user-defined currency at the network level. | ✔ | ||||
The total spend in USD. | ✔ | ||||
The cost per thousand impressions. | ✔ | ||||
The cost per click. | ✔ | ||||
The click-through rate. | ✔ | ||||
The cost per install. | ✔ | ||||
Install per mille, the number of times your app or game is installed per thousand ad impressions. | ✔ |
Field Name | Description |
Type
|
May be Null
|
Filter
|
Group
|
---|---|---|---|---|---|
The user-defined name for the Cost Configuration. | ✔ | ||||
The network defined 24 hour period for the cost window. | |||||
The UTC start date of the cost window. | |||||
The UTC end date of the cost window. | |||||
The ID of the company networks e.g., unity ios, unity android, etc., are all under the same ID. | |||||
The name of the network the configuration is associated to. | ✔ | ||||
The device platform. | ✔ | ||||
The client advertiser account with the network company. | ✔ | ||||
The user-defined name to which the configuration is associated to at the network level. | ✔ | ||||
The user-defined ID of the campaign the configuration is associated to at the network level. | |||||
The country code retrieved by Kochava from the network. | ✔ | ||||
The name representing the ad creative served by the network. | ✔ | ||||
The ID representing the ad creative served by the network. | ✔ | ||||
The type of ad being served by the network. | ✔ | ||||
The dimensions of the ad being served by the network. | ✔ | ||||
The name of the site to which the campaign is associated to. | ✔ | ||||
The internal ID used by the network for the site to which the campaign is associated to. | ✔ | ||||
The timezone reported by the network. | |||||
sub_campaign_name | The name of the sub-campaign level layer as specified in the media partner’s dashboard. May represent ad group, ad set, line item, etc. | ✔ | |||
sub_campaign_id | The ID of the sub-campaign level layer as specified in the media partner’s dashboard. May represent ad group, ad set, line item, etc. | ✔ | |||
channel | Set at the network level and retrieved by Kochava. | ||||
sub_site_id | TThe sub-site ID of the app where the ad was served, retrieved from the network. | ✔ | |||
The ID for the ad location within the app where the ad was served. | ✔ | ||||
keyword | Campaign keywords. | ✔ | |||
keyword_id | The ID for the campaign keywords. | ||||
bid_strategy | The bid strategy defined by the advertiser in the media partner’s dashboard. | ✔ | |||
bid_type | Bid type set by the media partner. | ✔ | |||
Objective of campaign set in media partner dashboard. | ✔ | ||||
The original currency for the associated configuration. | |||||
The total spend in the user-defined currency at the network level. | ✔ | ||||
The total spend in USD. | |||||
The number of impressions associated with the configuration. | |||||
The total number of clicks associated with the configuration. | |||||
The total number of installs associated with the configuration. | |||||
The cost per thousand impressions. | ✔ | ||||
The cost per click. | ✔ | ||||
The click-through rate. | ✔ | ||||
The cost per install. | ✔ | ||||
Install per mille, the number of times your app or game is installed per thousand ad impressions. | ✔ |
The Event Report provides a row-level report on events.
NOTE: Details for currency normalization can be found within the custom_dimensions field.
Field Name | Description |
Type
|
May be Null
|
---|---|---|---|
The action through which attribution was achieved, install or event. |
|||
The user defined name for the campaign to which the event was attributed. | ✔ | ||
The Kochava-specific ID of the campaign to which the event was attributed. | |||
Data received on event in the creative_id parameter. | ✔ | ||
The date and time of attribution (Adjusted to the Selected Time Zone). | |||
The date and time of attribution. (Coordinated Universal Time). | ✔ | ||
If true, identity link bridge values helped with the attribution match. If false, identity link bridge did not assist with the attribution match. | ✔ | ||
The means by which the user was attributed(click/impression). | |||
The initial action by which attribution was matched, impression or click or impression with click. | |||
The Kochava-specific ID of the Network to which the event was attributed. | |||
Unique identifier associated with the network to which the event was attributed. | |||
The number of seconds since attribution was made. | |||
Identifies the site to which the event was attributed within the publisher partner. | ✔ | ||
The tier/segment to which the attribution is associated. | ✔ | ||
The date and time of attribution(Coordinated Universal Time). | |||
The date and time of attribution (Adjusted to the Selected Time Zone). | |||
The Kochava-specific ID of the tracker to which the event was attributed. | ✔ | ||
The Kochava-specific ID of the tracker to which the event was attributed. | |||
The user defined name for the tracker to which the event was attributed. | ✔ | ||
The Kochava-specific ID of the campaign to which the click was attributed. | ✔ | ||
The user defined name for the campaign to which the click was attributed. | ✔ | ||
2-digit country designation where the click originated, based on IP lookup. | ✔ | ||
Data received on click in the creative_id parameter. | ✔ | ||
click_custom_parameters | Custom parameters passed with the click. | ||
Date and time of the click (Selected Time Zone) | ✔ | ||
Date and time of the click (Coordinated Universal Time). | ✔ | ||
An internal identifier used for mapping purposes. | ✔ | ||
User Agent of the device gathered upon click. | ✔ | ||
The ID assigned to duplicate clicks. | ✔ | ||
The device type and version of the device received on click. | ✔ | ||
An array of all device identifiers received on the click. | ✔ | ||
Raw ADID provided on the click (Android specific). | ✔ | ||
Raw Android_ID received on the click (Android specific). | ✔ | ||
MD5 encrypted Android_ID received on the click (Android specific). | ✔ | ||
SHA1 encrypted Android_ID received on the click (Android specific). | ✔ | ||
Custom provided identifier received with the click. | ✔ | ||
Primary email address delivered with the click. | ✔ | ||
Secondary email address delivered with the click. | ✔ | ||
Raw IDFA received on the click (iOS specific). | ✔ | ||
Raw IP address where the click originated. | ✔ | ||
Raw WAID received on the click (Windows specific). | ✔ | ||
The IP address from which the click originated. | ✔ | ||
ID representation of the impression which the click was matched to. | ✔ | ||
ID representation of the install which matched to the click. | ✔ | ||
The numeric value of the month the install was received. | ✔ | ||
The Kochava-specific ID of the Network to which the click originated. | ✔ | ||
The name of the Network to which the click originated. | ✔ | ||
Raw URL which was received for specific click.
NOTE: API call will return data in JSON format. |
✔ | ||
The total number of clicks generated from the qr code during the selected time frame. | |||
Identifies the site to which the click was served within the publisher partner. | ✔ | ||
Indicator to define if the click has simply been received (publish) or matched to an install. | ✔ | ||
The Kochava-specific ID of the tracker to which the click originated. | ✔ | ||
The user defined name for the tracker to which the click originated. | ✔ | ||
The area code where the click originated, based on IP lookup. | ✔ | ||
The name of the city where the click originated, based on IP lookup. | ✔ | ||
2-digit continent designation where the click originated, based on IP lookup. | ✔ | ||
2-digit country designation where the click originated, based on IP lookup. | ✔ | ||
3-digit country designation where the click originated, based on IP lookup. | ✔ | ||
The name of the country where the click originated, based on IP lookup. | ✔ | ||
The code for the designated marketing area where the click originated, based on IP lookup. | ✔ | ||
The latitude where the click originated, based on IP lookup.
Latitude values are populated based on a 3rd party IP lookup service and are associated with a general city center location. |
✔ | ||
The longitude where the click originated, based on IP lookup.
Longitude values are populated based on a 3rd party IP lookup service and are associated with a general city center location. |
✔ | ||
The postal code of the region where the click originated, based on IP lookup. | ✔ | ||
An alpha-numeric code identifying the geographic region where the click originated, based on IP lookup. | ✔ | ||
Number of events (based on selection) during defined time frame. | |||
Custom provided dimensions received with the event. | ✔ | ||
Raw ADID provided on the event (Android specific). | ✔ | ||
Raw Android_ID received on the event (Android specific). | ✔ | ||
Custom provided identifier received with the event . | ✔ | ||
Raw IDFA provided on the event (iOS specific) | ✔ | ||
Raw IDFV provided on the event (iOS specific) | ✔ | ||
Kochva generated Unique ID assigned to device. | |||
The operating system of the device. | ✔ | ||
The device type of the device. | ✔ | ||
The device version of the mobile device. | ✔ | ||
Number of custom events (based on selection). | |||
Data provided dimensions received with the event. | ✔ | ||
The sum of event data. | ✔ | ||
The name of the advertiser defined and integrated event. | ✔ | ||
The time that the event was performed by the mobile device. | |||
The name of the city where the event originated, based on IP lookup. | ✔ | ||
The two digit code where the event originated, based on IP lookup. | ✔ | ||
The latitude where the event originated, based on IP lookup.
Latitude values are populated based on a 3rd party IP lookup service and are associated with a general city center location. |
✔ | ||
The longitude where the event originated, based on IP lookup.
Longitude values are populated based on a 3rd party IP lookup service and are associated with a general city center location. |
✔ | ||
An alpha-numeric code identifying the geographic region where the event originated, based on IP lookup. | ✔ | ||
The iAd specific campaign ID. | ✔ | ||
Indicates whether iAd has claimed and won attribution (1). | ✔ | ||
Indicates whether the legacy iAd is attribution logic was utilized (1). | ✔ | ||
The Kochava-specific ID of the network to which the iAd attribution is attributed. | ✔ | ||
A customer defined unique identifier for linking devices. | ✔ | ||
The Kochava-specific ID of the campaign to which the impression is associated. |
✔ | ||
The user defined name for the campaign to which the impression is associated. | ✔ | ||
2-digit country designation where the impression originated, based on IP lookup. | ✔ | ||
The ID/name of the creative which was served with the impression. | ✔ | ||
The date the impression occurred (Selected Time Zone). | ✔ | ||
Date and time of the impression (Coordinated Universal Time). | ✔ | ||
The device type and version of the device which received on impression. | ✔ | ||
An array of all device identifiers received on the impression. | ✔ | ||
Unique identifier associated with the impression which has been received. | ✔ | ||
The IP address from which the impression originated. | ✔ | ||
Kochava generated unique identifier associated with the impression which has been received. | ✔ | ||
ID representation of the click which the impression was matched to. | ✔ | ||
ID representation of the install which matched to the impression. | ✔ | ||
The Kochava-specific ID of the Network to which the impression originated. | ✔ | ||
The name of the Network to which the impression originated. | ✔ | ||
impression_original_request | Raw URL which was received for specific impression.
NOTE: API call will return data in JSON format. |
✔ | |
Identifies the site to which the impression was served within the publisher partner. | ✔ | ||
The Kochava-specific ID of the tracker to which the impression is associated. | ✔ | ||
The user defined name for the tracker to which the impression is associated. | ✔ | ||
The date the install occurred (Selected Time Zone). | ✔ | ||
Date and time of the install (Coordinated Universal Time). | ✔ | ||
User Agent of the device gathered upon install. | ✔ | ||
The device type and version of the device received on install. | ✔ | ||
Raw ADID provided on the install (Android specific). | ✔ | ||
Raw Android_ID provided on the install (Android specific). | ✔ | ||
Custom provided identifier received with the install. | ✔ | ||
Primary email address delivered with the install. | ✔ | ||
Secondary email address delivered with the install. | ✔ | ||
Raw IDFA provided on the install (iOS specific). | ✔ | ||
An array of the device identifiers received on install. | ✔ | ||
The IP address from which the install originated. | ✔ | ||
Raw WAID received on install (Windows specific). | ✔ | ||
Defines the nature of the data point on which the click was matched to the install. | ✔ | ||
ID representation of the install which matched to the click. | ✔ | ||
Indication whether a receipt was received from the app store for the associated install as well as the level of authentication of the receipt. | |||
The original Self Attributing Network to which the install is attributed. | ✔ | ||
Indicator to define if an install has been simply been received (publish) or matched to a click. | |||
Indicator if event is being attributed to the last reengagment. | |||
Click ID assigned by Kochava. | ✔ | ||
Click ID as received from the partner. | ✔ | ||
The IP address from which the request originated. | ✔ | ||
User Agent from which the request originated. | ✔ | ||
The date and time of the event (Selected Time Zone). | |||
The date and time of the event (Coordinated Universal Time). | ✔ | ||
Indicator if the click traffic was valid or invalid based on Traffic Verification rules. | ✔ | ||
Indicator if the impression traffic was valid or invalid based on Traffic Verification rules. | ✔ | ||
The device ATT status. | ✔ | ||
ATT status 1 – authorized ATT status 0 – |
✔ | ||
User response timestamp. | ✔ | ||
✔ |
NOTE: Some columns within the report may contain JSON encoded data. These columns will have “*_querystring” versions that will provide a URL QueryString encoded version of these columns. The JSON path for each value in the JSON will be used as the querystring key for that value.
NOTE: The “mtr_rejected”:”86400″ flag being present in the custom_dimensions column in an event detail report indicates that that instance of the event did not meet the minimum time to reengagement requirements and that it is not eligible for reengagement. This feature can be configured in the dashboard under the “Events” tab. By default, it is set to 24 hours, which is why you see “mtr_rejected”:”86400”, 86400 = amount of seconds in 24 hours.
Field Name | Description |
Type
|
May be Null
|
---|---|---|---|
The percentage awarded to the network for the install. | |||
the date and time of the install (Coordinated Universal Time). | |||
The date and time of the install (Selected Time Zone). | |||
Fractional ID assigned by Kochava. | |||
The Kochava-specific ID of the Network to which the click originated. | |||
The identifier by which the fractional attribution was credited. | |||
The Kochava-specific ID of the match that won attribution. | |||
The identifier by which the fractional attribution was matched. | |||
Date and Time of traffic (Coordinated Universal Time). | ✔ | ||
Date and time of traffic(Selected Time Zone). | ✔ | ||
The Kochava-specific ID of the traffic to which the install was fractional attributed. | |||
The numeric value of the month the install was received. | ✔ | ||
The type of traffic the fractional attribution is accredited to. |
NOTE: Some columns within the report may contain JSON encoded data. These columns will have “*_querystring” versions that will provide a URL QueryString encoded version of these columns. The JSON path for each value in the JSON will be used as the querystring key for that value.
(see iOS 14+ restrictions)
Field Name | Description |
Type
|
May be Null
|
---|---|---|---|
Random internal identifier. | |||
The Kochava-specific ID of the match that won attribution. | |||
The date and time of attribution (Coordinated Universal Time). | |||
The date and time of attribution (Selected Time Zone). | |||
The number of the month in which attribution occurred. | |||
Description of how attribution was performed; for example, device ID, Facebook, etc. | |||
The Kochava-specific ID of the impression which led to install. | |||
The Kochava-specific ID of the Network to which the impression originated. | |||
The name of the Network to which the impression originated. | ✔ | ||
The type of attribution the impression was matched on. | |||
The ID which the impression was matched on. | |||
Unique identifier associated with the influencer. | |||
The Kochava-specific ID of the Network to which the influencer originated. | |||
The name of the network in which the influencer occurred. | ✔ | ||
The date and time of the influencer (Corrdinated Universal Time) | |||
The date and time of the influencer (Selected Time Zone). | |||
Description of how we matched the click to the influencer; for example, device ID, Facebook, etc. | |||
Provides the actual piece of data the influencer was matched on; for example, the device ID. | |||
The reason the install was attributed to another Network (for example, another network was credited with last-click) |
NOTE: Some columns within the report may contain JSON encoded data. These columns will have “*_querystring” versions that will provide a URL QueryString encoded version of these columns. The JSON path for each value in the JSON will be used as the querystring key for that value.
The Install Report provides a row-level view of installs for a given campaign.
Field Name | Description |
Type
|
May be Null
|
---|---|---|---|
The Kochava-specific ID of the campaign to which the the install was attributed. | |||
The user defined name for the campaign to which the install was attributed. | ✔ | ||
Data received on install in the creative_id parameter. | ✔ | ||
If true, identity link bridge values helped with the attribution match. If false, identity link bridge did not assist with the attribution match. | ✔ | ||
The Kochava-specific ID of the Network to which the install was attributed. | |||
The name of the Network to which the install was attributed. | ✔ | ||
Identifies the site to which the install was attributed within the publisher partner. | |||
The tier/segment to which the attribution is associated. | ✔ | ||
The Kochava-specific ID of the tracker to which the install was attributed. | |||
The user defined name for the tracker to which the install was attributed. | ✔ | ||
The Kochava-specific ID of the campaign to which the click was attributed. | |||
The user defined name for the campaign to which the click was attributed. | ✔ | ||
2-digit country designation where the click originated, based on IP lookup. | ✔ | ||
Data received on click in the creative_id parameter. | ✔ | ||
click_custom_parameters | Custom parameters passed with the click. | ||
An internal identifier used for mapping purposes. | ✔ | ||
User Agent of the device gathered upon click. | ✔ | ||
The device type and version of the device received on click. | ✔ | ||
The ID assigned to duplicate clicks. | ✔ | ||
An array of all device identifiers received on the click. | ✔ | ||
Raw ADID provided on the click (Android specific). | ✔ | ||
Raw Android_ID received on the click (Android specific). | ✔ | ||
MD5 encrypted Android_ID received on the click (Android specific). | ✔ | ||
SHA1 encrypted Android_ID received on the click (Android specific). | ✔ | ||
Custom provided identifier received with the click. | ✔ | ||
Primary email address delivered with the click. | ✔ | ||
Secondary email address delivered with the click. | ✔ | ||
Raw IDFA received on the click (iOS specific). | ✔ | ||
Raw IP address where the click originated. | ✔ | ||
Raw WAID received on the click (Windows specific). | ✔ | ||
The IP address from which the click originated. | |||
ID representation of the impression which the click was matched to. | ✔ | ||
ID representation of the install which matched to the click. | ✔ | ||
The numeric value of the month the install was received. | |||
The Kochava-specific ID of the Network to which the click originated. | |||
The name of the Network to which the click originated. | ✔ | ||
The total number of clicks generated from the qr code during the selected time frame. | |||
Raw URL which was received for specific click.
NOTE: API call will return data in JSON format. |
|||
Identifies the site to which the click was served within the publisher partner. | ✔ | ||
Indicator to define if the click has simply been received (publish) or matched to an install. | |||
The tier/segment to which the click is associated. | ✔ | ||
The Kochava-specific ID of the tracker to which the click originated. | |||
The user defined name for the tracker to which the click originated. | ✔ | ||
The area code where the click originated, based on IP lookup. | ✔ | ||
The name of the city where the click originated, based on IP lookup. | ✔ | ||
2-digit continent designation where the click originated, based on IP lookup. | ✔ | ||
2-digit country designation where the click originated, based on IP lookup. | ✔ | ||
3-digit continent designation where the click originated, based on IP lookup. | ✔ | ||
The name of the country where the click originated, based on IP lookup. | ✔ | ||
The code for the designated marketing area where the click originated, based on IP lookup. | ✔ | ||
The latitude where the click originated, based on IP lookup.
Latitude values are populated based on a 3rd party IP lookup service and are associated with a general city center location. |
✔ | ||
The longitude where the click originated, based on IP lookup.
Longitude values are populated based on a 3rd party IP lookup service and are associated with a general city center location. |
✔ | ||
The postal code of the region where the click originated, based on IP lookup. | ✔ | ||
An alpha-numeric code identifying the geographic region where the click originated, based on IP lookup. | ✔ | ||
A customer defined unique identifier for linking devices. | ✔ | ||
The Kochava-specific ID of the campaign to which the impression is associated. | ✔ | ||
The user defined name for the campaign to which the impression is associated. | ✔ | ||
2-digit country designation where the impression originated, based on IP lookup. | ✔ | ||
The ID/name of the creative which was served with the impression. | ✔ | ||
The device type and version of the device which received on impression. | ✔ | ||
An array of all device identifiers received on the impression. | ✔ | ||
Unique identifier associated with the impression which has been received. | ✔ | ||
The IP address from which the impression originated. | ✔ | ||
Kochava generated unique identifier associated with the impression which has been received. | ✔ | ||
ID representation of the click which the impression was matched to. | ✔ | ||
ID representation of the install which matched to the impression. | ✔ | ||
The Kochava-specific ID of the Network to which the impression originated. | ✔ | ||
The name of the Network to which the impression originated. | ✔ | ||
impression_original_request | Raw URL which was received for specific impression.
NOTE: API call will return data in JSON format. |
✔ | |
Identifies the site to which the impression was served within the publisher partner. | ✔ | ||
The tier/segment to which the impression is associated. | ✔ | ||
The user defined name for the tracker to which the impression is associated. | ✔ | ||
The user defined name for the tracker to which the impression is associated. | ✔ | ||
The channel type to which the install is attributed. | ✔ | ||
The date and time the click occurred which led to install (Selected Time Zone). | ✔ | ||
The date and time the click occurred which led to install (Coordinated Universal Time). | ✔ | ||
The date and time of install (Selected Time Zone). | |||
The date and time of install (Coordinated Universal Time). | ✔ | ||
User Agent of the device gathered upon install. | ✔ | ||
The device version of the mobile device. | ✔ | ||
Raw ADID provided on install (Android specific). | ✔ | ||
Raw Android_ID received on install (Android specific). | ✔ | ||
Custom provided identifier received with install. | ✔ | ||
Unique identifier associated with the custom provided identifier. | ✔ | ||
Primary email address delivered with install. | ✔ | ||
Secondary email address delivered with the click. | ✔ | ||
Raw IDFA received on install (iOS specific). | ✔ | ||
An array of all device identifiers received on install. | ✔ | ||
The IP address from which the install originated. | ✔ | ||
Raw WAID received on the click (Windows specific). | ✔ | ||
The date and time the impression occurred which led to install (Selected Time Zone). | ✔ | ||
The date and time the impression occurred which led to install (Coordinated Universal Time). | ✔ | ||
Install ID assigned by Kochava | |||
The ID type to which installation is attributed. | |||
Unique identifier to which the install is matched on. | |||
Raw URL which was received for specific install.
NOTE: API call will return data in JSON format. |
|||
The user defined price per click or price per install. | ✔ | ||
Indication whether a receipt was received from the app store for the associated install as well as the level of authentication of the receipt. | |||
If a value is present this signifies that the install was a reprocessed install(not the first install from the device). | |||
Indicator to define if an install has been simply been received (publish) or matched to a click. | |||
The area code where the install originated, based on IP lookup. | ✔ | ||
The name of the city where the install originated, based on IP lookup. | ✔ | ||
2-digit continent designation where the impression originated, based on IP lookup. | ✔ | ||
2-digit continent designation where the install originated, based on IP lookup. | ✔ | ||
3-digit continent designation where the impression originated, based on IP lookup. | ✔ | ||
The name of the country where the install originated, based on IP lookup. | ✔ | ||
The code for the designated marketing area where the install originated, based on IP lookup. | ✔ | ||
The latitude where the install originated, based on IP lookup.
Latitude values are populated based on a 3rd party IP lookup service and are associated with a general city center location. |
✔ | ||
The longitude where the install originated, based on IP lookup.
Longitude values are populated based on a 3rd party IP lookup service and are associated with a general city center location. |
✔ | ||
The postal code of the region where the install originated, based on IP lookup. | ✔ | ||
An alpha-numeric code identifying the geographic region where the install originated, based on IP lookup. | ✔ | ||
Click ID assigned by Kochava. | |||
Click ID as received from the partner. | ✔ | ||
Indicator if the click traffic was valid or invalid based on Traffic Verification rules. | ✔ | ||
Indicator if the install traffic was valid or invalid based on Traffic Verification rules. | ✔ | ||
The device ATT status. | ✔ | ||
ATT status 1 – authorized ATT status 0 – |
✔ | ||
User response timestamp. | ✔ | ||
✔ |
NOTE: Some columns within the report may contain JSON encoded data. These columns will have “*_querystring” versions that will provide a URL QueryString encoded version of these columns. The JSON path for each value in the JSON will be used as the querystring key for that value.
Field Name | Description |
Type
|
May be Null
|
---|---|---|---|
Click ID assigned by Kochava. | ✔ | ||
Kochava generated Unique ID assigned to device. | |||
Date and time of the event (Coordinated Universal Time). | |||
Date and time of the event (Selected Time Zone). | |||
The numeric value of the month the click was received. | |||
Date and time of the click (Coordinated Universal Time). | |||
Date and time of the click (Selected Time Zone). | |||
The name of the advertiser defined and integrated event for reengagement. | ✔ | ||
Indicator to define if the click has been matched to an event for reengagement. | |||
The Kochava-specific ID of the Network to which the reengagement originated. | |||
The name of the Network to which the reengagement originated. | ✔ | ||
The Kochava-specific ID of the tracker to which the reengagement originated. | |||
The user defined name for the tracker to which the reengagement originated. | ✔ | ||
The Kochava-specific ID of the campaign to which the reengagement was attributed. | |||
The user defined name for the campaign to which the reengagement was attributed. | ✔ | ||
Identifies the site to which the reengagement was served within the publisher partner. | ✔ | ||
✔ | |||
Data received on reengagement in the creative_id parameter. | ✔ | ||
2-digit country designation where the reengagement originated, based on IP lookup. | ✔ | ||
Raw IP address where the reengagement originated. | ✔ | ||
The device type and version of the device received on reengagement. | ✔ | ||
The primary device ID received on reengagement. | ✔ | ||
reengage_original_request | Raw URL which was received for specific reengagement.
NOTE: API call will return data in JSON format. |
||
ID representation of the impression which the reengagement was matched to. | ✔ | ||
ID representation of the install which matched to the reengagement. | |||
Identifiers available for attribution on the reengagement. | ✔ | ||
The ID assigned to duplicate reengagements. | ✔ | ||
click_original_request | Raw URL which was received for specific click.
NOTE: API call will return data in JSON format. |
||
2-digit continent designation where the reengagement originated, based on IP lookup. | ✔ | ||
2-digit country designation where the reengagement originated, based on IP lookup. | ✔ | ||
3-digit country designation where the reengagement originated, based on IP lookup. | ✔ | ||
The name of the country where the reengagement originated, based on IP lookup. | ✔ | ||
An alpha-numeric code identifying the geographic region where the reengagement originated, based on IP lookup. | ✔ | ||
The postal code of the region where the reengagement originated, based on IP lookup. | ✔ | ||
The code for the designated marketing area where the reengagement originated, based on IP lookup. | ✔ | ||
The name of the city where the reengagement originated, based on IP lookup. | ✔ | ||
The area code where the reengagement originated, based on IP lookup. | ✔ | ||
The longitude where the reengagement originated, based on IP lookup.
Longitude values are populated based on a 3rd party IP lookup service and are associated with a general city center location. |
✔ | ||
The latitude where the reengagement originated, based on IP lookup.
Latitude values are populated based on a 3rd party IP lookup service and are associated with a general city center location. |
✔ | ||
The tier/segment to which the reengagement is associated. | ✔ | ||
The total number of clicks generated from the QR code during the selected time frame. |
NOTE: Some columns within the report may contain JSON encoded data. These columns will have “*_querystring” versions that will provide a URL QueryString encoded version of these columns. The JSON path for each value in the JSON will be used as the querystring key for that value.
Field Name | Description |
Type
|
May be Null
|
---|---|---|---|
Kochava generated unique identifier associated with the impression which has been received. | |||
Kochava generated Unique ID assigned to device. | |||
Date and time of the reengagement event (Coordinated Universal Time). | (datetime) |
||
Date and time of the reengagement event (Selected Time Zone). | |||
Date and time of the impression (Selected Time Zone). | (datetime) |
||
Date and time of the reengagement impression (Coordinated Universal Time). | (datetime) |
✔ | |
Date and time of the reengagement impression (Selected Time Zone). | (datetime) |
✔ | |
The name of the advertiser defined and integrated event for reengagement. | |||
Indicator to define if the click has been matched to an event for reengagement. | |||
The Kochava-specific ID of the Network to which the reengagement originated. | (int) |
||
The name of the Network to which the reengagement originated. | |||
The Kochava-specific ID of the tracker to which the reengagement originated. | (int) |
||
The user defined name for the tracker to which the reengagement originated. | |||
The Kochava-specific ID of the campaign to which the reengagement was attributed. | |||
The user defined name for the campaign to which the reengagement was attributed. | |||
Identifies the site to which the reengagement was served within the publisher partner | ✔ | ||
Data received on reengagement in the creative_id parameter. | ✔ | ||
2-digit country designation where the reengagement originated, based on IP lookup. | ✔ | ||
Raw IP address where the reengagement originated. | ✔ | ||
The device type and version of the device received on reengagement. | ✔ | ||
The primary device ID received on reengagement. | |||
reengage_original_request | Raw URL which was received for specific reengagement.
NOTE: API call will return data in JSON format. |
✔ | |
reengage_matched_impression | ID representation of the impression which the reengagement was matched to. | (int) |
✔ |
ID representation of the install which matched to the reengagement. | (int) |
||
Identifiers available for attribution on the reengagement. | |||
The ID assigned to duplicate reengagements. | (int) |
||
The total number of impressions generated from the qr code during the selected time frame. | |||
imp_original_request | Raw URL which was received for specific impression.
NOTE: API call will return data in JSON format. |
✔ | |
The tier/segment to which the reengagement is associated. |
Field Name | Description |
Type
|
May be Null
|
---|---|---|---|
The date and time that the restated cost data began being collected. | |||
The date and time that the restated cost data ended being collected. | |||
The Kochava-specific ID of the tracker to which the restated cost was attributed. | |||
The Kochava-specific ID of the network to which the restated cost data is attributed. | ✔ | ||
Unique identifier associated with the network to which the restated cost data is attributed. | |||
The user defined name for the campaign to which the restated cost data is attributed. | ✔ | ||
The type of ad being served. | ✔ | ||
The total restated daily spend day 1. | ✔ | ||
The total restated daily spend day 2. | ✔ | ||
The total restated daily spend day 7. | ✔ | ||
The total restated daily spend day 14. | ✔ | ||
✔ | |||
The total restated daily spend day 30. | ✔ | ||
The total restated daily spend day 60. | ✔ | ||
The users device type. | ✔ | ||
the gender of the user. | ✔ | ||
The geographic region of the device. | ✔ | ||
The campaign or ad group id of the device. | ✔ | ||
The campaign or ad group name of the device. | ✔ | ||
image | The ID/name of the creative which influenced the device. | ✔ | |
Generic placeholder, used if data not grouped by campaign or ad. | ✔ | ||
The ID for the network ad. | |||
✔ | |||
The device platform. | ✔ | ||
target | The user group which the ad or campaign is targeting. | ✔ | |
url | The raw URL which was received from the device. | ✔ | |
The grouping of data returned by the network’s API. | ✔ |
The Campaign Summary Report provides a granular level of reporting and segment by campaign.
Field Name | Description |
Type
|
May be Null
|
---|---|---|---|
The date and time of install (Coordinated Universal Time). | |||
The date and time of install (Selected Time Zone). | |||
The Kochava-specific ID of the Network to which the install is attributed. | ✔ | ||
The name of the Network to which the install is attributed. | ✔ | ||
The Kochava-specific ID of the campaign to which the install was attributed. | |||
The user defined name for the campaign to which the install was attributed. | ✔ | ||
The Kochava-specific ID of the tracker to which the install was attributed. | |||
The user defined name for the tracker to which the install was attributed. | ✔ | ||
The site on which the campaign was run. | ✔ | ||
The user defined name of the creative used in the campaign. | ✔ | ||
The code for the designated marketing area where the install originated, based on IP lookup. | ✔ | ||
An alpha-numeric code identifying the geographic region where the click originated, based on IP lookup. | ✔ | ||
The name of the city to which the install is attributed. | ✔ | ||
2-digit country designation where the click originated, based on IP lookup. | ✔ | ||
cp_0 to cp_9 | Custom parameters passed with the click. | ||
The total number of clicks during the selected time frame. | |||
The total number of clicks matched to impressions. | |||
The total number of duplicate clicks during the selected time frame. | |||
Money spent per click, based on data received on the click. | |||
The number of install of the app during the selected time frame. | |||
The number of clicks matched to installs for the selected time frame. | |||
The number of impressions matched to installs for the selected time frame. | |||
The number of qr codes clicks matched to installs for the selected time frame. | |||
Money spent per install, based on data received on the install. | |||
The number of impressions during the selected time frame. | |||
Money spent per impression, based on data received on the click. | |||
The total number of clicks generated from the QR code during the selected time frame. | |||
total_spend_on_traffic_selected | Assuming you select click and impression or install, this is what we have calculated as the total spent for that network for the given type of traffic | ||
total_spend_network_reported | This is what the network has told Kochava via the API how much was spent in total for the network. It is required to have the Kochava tracker GUIDs entered in the network_campaign_name within the network dashboard, if tracker GUID is not entered, then this field is blank. **need to include “network_spend” as part of the traffic array in order for column to be returned** |
The Network Summary Report provides a summary of network performance across a variety of metrics.
Field Name | Description |
Type
|
May be Null
|
---|---|---|---|
The date and time of install (Coordinated Universal Time). | |||
The date and time of install (Selected Time Zone). | |||
The Kochava-specific ID of the Network to which the install was attributed. | ✔ | ||
The name of the Network to which the install was attributed. | ✔ | ||
The Kochava-specific ID of the campaign to which the install is associated. | |||
The user defined name of the campaign. | ✔ | ||
The Kochava-specific ID of the tracker to which the click was attributed. | |||
The user defined name for the tracker to which the click originated. | ✔ | ||
Identifies the site to which the install was served within the publisher partner. | ✔ | ||
The user defined name of the creative used in the campaign. | ✔ | ||
The code for the designated marketing area where the install originated, based on IP lookup. | ✔ | ||
An alpha-numeric code identifying the geographic region where the click originated, based on IP lookup. | ✔ | ||
The name of the city to which the install is attributed. | ✔ | ||
2-digit country designation where the click originated, based on IP lookup. | ✔ | ||
The total number of clicks during the selected time frame. | |||
The number of impressions matched to clicks for the selected time frame. | |||
The total number of duplicate clicks during the selected time frame. | |||
Total spend data received on the click | ✔ | ||
The number of installs of the app during the selected time frame. | |||
The number of impressions matched to installs for the selected time frame. | |||
The number of impressions matched to installs for the selected time frame. | |||
Money spent per install, based on data received on the install. | |||
The number of impressions of the app during the selected time frame. | |||
The total number of clicks generated from the QR code during the selected time frame. | |||
The number of qr codes clicks matched to installs for the selected time frame. | |||
This is what the network has told Kochava via the API how much was spent in total for the network. It is required to have the Kochava tracker GUIDs entered in the network_campaign_name within the network dashboard, if tracker GUID is not entered, then this field is blank.
**need to include “network_spend” as part of the traffic array in order for column to be returned** |
|||
Assuming you select click and impression or install, this is what we have calculated as the total spent for that network for the given type of traffic |
Identify how many users are active within your app by campaign for various time periods after they have installed. The standard retention query shows active users on each day after install (1, 2, 3, 5, 7, 21, 30).
Field Name | Description |
Type
|
May be Null
|
---|---|---|---|
The Kochava-specific ID of the Network to which the event was attributed. | |||
The name of the Network to which the event originated. | |||
The number of installs of the app during the selected time frame. | |||
Number of active users exactly 1 day after install. | |||
Number of active users exactly 2 days after install. | |||
Number of active users exactly 3 days after install. | |||
Number of active users exactly 5 days after install. | |||
Number of active users exactly 7 days after install. | |||
Number of active users exactly 14 days after install. | |||
Number of active users exactly 21 days after install. | |||
Number of active users exactly 30 days after install. |
Identify how many users are active within your app by campaign for various time periods after they have installed. The windowed retention query shows how many users are active in each window representing days after install (1, 2, 3, 4-5, 6-7, 8-14, 15-21, 22-30).
Field Name | Description |
Type
|
May be Null
|
---|---|---|---|
The Kochava-specific ID of the Network to which the event was attributed. | |||
The name of the Network to which the event originated. | |||
The number of installs of the app during the selected time frame. | |||
Number of active users exactly 1 day after install. | |||
Number of active users exactly 2 days after install. | |||
Number of active users exactly 3 days after install. | |||
Number of active users between 4 and 5 days after install. | |||
Number of active users between 6 and 7 days after install. | |||
Number of active users between 8 and 14 days after install. | |||
Number of active users between 15 and 21 days after install. | |||
Number of active users between 22 and 30 days after install. |
This report provides an aggregated summary of user conversion values sourced from SKAdNetwork signals. Provides meaning of conversion values based on the app’s conversion model setting.
Field Name | Description |
Type
|
May be Null
|
Filter
|
Group
|
---|---|---|---|---|---|
The start date for sk_installs based on install date and impression/click counts. | ✔ | ✔ | |||
The end date for sk_installs based on install date and impression/click counts. | ✔ | ✔ | |||
The name of the advertiser’s account within Kochava. | |||||
The numeric ID of the advertiser’s account in Kochava. | |||||
The numeric ID of the app on the app store. | |||||
The name of the advertiser’s app in Kochava. | |||||
The numeric ID of the advertiser’s app in Kochava. | |||||
The GUID of the advertiser’s app in Kochava. | |||||
The version of the SKAdNetwork API. | |||||
The ID assigned to the media partner by Apple when integrating with SKAdNetwork. | ✔ | ✔ | |||
The name of the integrated media partner in Kochava. | ✔ | ✔ | |||
The numeric ID of the integrated media partner in Kochava. | ✔ | ||||
The numeric ID of the campaign was reported to SKAdNetwork on the loadproduct call. Integer between 1 and 100. | ✔ | ✔ | |||
The name of the campaign as specified in the media partner’s dashboard. | ✔ | ✔ | |||
The name of the conversion model chosen on the SKAdNetwork Settings page in Kochava. | |||||
The length of time the user’s activity was observed (in days). Values can be: Undefined, Install Only, D0, D0-1, D0-2, D0-3, D0-4, D0-5, D0-6, D0-7 D0 = within 24 hrs of install. | |||||
The meaning of the conversion value based on the conversion model used; reflects the user’s activity in the app after install.
Highest Value Event: single event name User Journey: list of comma separated event names Revenue: range of revenue in USD Engagement: number of times the target event occurred and the target event name |
|||||
The user’s numerical conversion value. Integer between 0-63. | |||||
The ID of the ad exchange that served the bid request. | ✔ | ||||
The numeric ID of the app on the app store, where the ad was served. | ✔ | ✔ | |||
The site ID of the app where the ad was served, shared by the media partner on the ad signal. | ✔ | ||||
The sub-site ID of the app where the ad was served, shared by the media partner on the ad signal. | ✔ | ||||
The ID of the campaign as specified in the media partner’s dashboard. | ✔ | ||||
The name of the sub-campaign level layer as specified in the media partner’s dashboard. May represent ad group, ad set, line item, etc. | ✔ | ||||
The ID of the sub-campaign level layer as specified in the media partner’s dashboard. May represent ad group, ad set, line item, etc. | ✔ | ||||
Amount the advertiser bid for the ad to be served. | ✔ | ||||
Currency of bid amount. | ✔ | ||||
bid_strategy | The bid strategy defined by the advertiser in the media partner’s dashboard. | ✔ | |||
bid_type | Bid type set by the media partner. | ✔ | |||
campaign_objective | Objective of campaign set in media partner dashboard. | ✔ | |||
campaign_status | Status of a campaign in the media partner dashboard. | ✔ | |||
The numerical id representing the ad creative served. | ✔ | ||||
The name representing the ad creative served. | ✔ | ||||
The keyword searched by the user that clicked the ad. | ✔ | ||||
Parameter passed by the media partner to Kochava in the payload. | ✔ | ✔ | |||
If the payload has an IP address field, it is the country associated to that IP. If no IP field in the payload, it is the country of the IP from where the payload was sent to Kochava. | ✔ | ||||
For the Revenue model, this is the minimum value set in your conversion model configuration. | ✔ | ||||
For the Revenue model, this is the maximum value set in your conversion model configuration. | ✔ | ||||
engagement_count | For the Engagement model, this is the number of times that specified event has occurred | ✔ | |||
Denotes if the user’s activity driven by a clicked ad interaction. | ✔ | ||||
Denotes if the user’s activity driven by a viewed ad interaction. | ✔ | ||||
sk_source_identifier | Known as the “campaign ID” in previous SKAdNetwork versions, this value relates to the placement detail of the ad-network served inventory. | ✔ | |||
A coarse grained value is a type of hierarchical conversion value and can be low, medium, or high. | ✔ | ||||
In SKAdNetwork v4, a total of (3) user activities can be attributed by SKAdNetwork and this value indicates which of the 3 conversion windows that conversion occurred in. | ✔ | ||||
sk_source_domain | For web ads, the postback may include a source-domain instead of a source-app-id, indicating the conversion resulted from a mobile web ad unit. | ✔ | |||
Count of SKAdNetwork-reported installs. | |||||
Count of SKAdNetwork-reported installs that were flagged as redownloads by SKAdNetwork. |
An aggregated summary of user install data sourced from SKAdNetwork signals.
NOTE: Influencers are not included in the default report. To include influencers in your report, select Customize and be sure to add Influencers within the TRAFFIC INCLUDES section.
Field Name | Description |
Type
|
May be Null
|
Filter
|
Group
|
---|---|---|---|---|---|
The start date for sk_installs based on install date and impression/click counts. | ✔ | ✔ | |||
The end date for sk_installs based on install date and impression/click counts. | ✔ | ✔ | |||
The name of the advertiser’s account within Kochava. | |||||
The numeric ID of the advertiser’s account in Kochava. | |||||
The numeric ID of the app on the app store. | |||||
The name of the advertiser’s app in Kochava. | |||||
The numeric ID of the advertiser’s app in Kochava. | |||||
The GUID of the advertiser’s app in Kochava. | |||||
The ID assigned to the media partner by Apple when integrating with SKAdNetwork. | ✔ | ✔ | |||
The name of the integrated media partner in Kochava. | ✔ | ✔ | |||
The numeric ID of the integrated media partner in Kochava. | ✔ | ||||
The numeric ID of the campaign was reported to SKAdNetwork on the loadproduct call. Integer between 1 and 100. | ✔ | ✔ | |||
The name of the campaign as specified in the media partner’s dashboard. | ✔ | ✔ | |||
The ID of the ad exchange that served the bid request. | ✔ | ||||
The site ID of the app where the ad was served, shared by the media partner on the ad signal. | ✔ | ||||
The sub-site ID of the app where the ad was served, shared by the media partner on the ad signal. | ✔ | ||||
The ID of the campaign as specified in the media partner’s dashboard. | ✔ | ||||
The name of the sub-campaign level layer as specified in the media partner’s dashboard. May represent ad group, ad set, line item, etc. | ✔ | ||||
The ID of the sub-campaign level layer as specified in the media partner’s dashboard. May represent ad group, ad set, line item, etc. | ✔ | ||||
Amount the advertiser bid for the ad to be served. | ✔ | ||||
Currency of bid amount. | ✔ | ||||
bid_strategy | The bid strategy defined by the advertiser in the media partner’s dashboard. | ✔ | |||
bid_type | Bid type set by the media partner. | ✔ | |||
campaign_objective | Objective of campaign set in media partner dashboard. | ✔ | |||
campaign_status | Status of a campaign in the media partner dashboard. | ✔ | |||
The numerical id representing the ad creative served. | ✔ | ||||
The name representing the ad creative served. | ✔ | ||||
The keyword searched by the user that clicked the ad. | ✔ | ||||
Parameter passed by the media partner to Kochava in the payload. | ✔ | ✔ | |||
sk_install_matched_to_click | Denotes if the user’s activity driven by a clicked ad interaction. | ✔ | |||
sk_install_matched_to_impression | Denotes if the user’s activity driven by a viewed ad interaction. | ✔ | |||
sk_source_identifier | Known as the “campaign ID” in previous SKAdNetwork versions, this value relates to the placement detail of the ad-network served inventory. | ✔ | ✔ | ||
sk_coarse_conversion_value | A coarse grained value is a type of hierarchical conversion value and can be low, medium, or high. | ✔ | |||
sk_postback_sequence_index | In SKAdNetwork v4, a total of (3) user activities can be attributed by SKAdNetwork and this value indicates which of the 3 conversion windows that conversion occurred in. | ✔ | |||
sk_source_domain | For web ads, the postback may include a source-domain instead of a source-app-id, indicating the conversion resulted from a mobile web ad unit. | ✔ | ✔ | ||
Count of SKAdNetwork reported influencers. | |||||
Count of SKAdNetwork reported click-through influencers. | |||||
Count of SKAdNetwork reported view-through influencers. | |||||
Count of impressions. | |||||
Count of clicks. | |||||
The click-through rate. | ✔ | ||||
Count of SKAdNetwork-reported installs. | |||||
Percent of SKAdNetwork-reported installs to clicks. Up to 2 decimals | |||||
Installs per Mille. Count of SKAdNetwork-reported installs per 1000 impressions. Up to 4 decimals. | |||||
Count of SKAdNetwork-reported installs that were flagged as redownloads by SKAdNetwork. | |||||
Count of sk_installs where the user triggered an updateConversion call with an in-app action. | |||||
Percent of sk_installs where the user triggered an updateConversion call with an in-app action to total sk_installs. Up to 2 decimals. |
Field Name | Description |
Type
|
May be Null
|
---|---|---|---|
The entitlement label(s) associated to entitlement_id set up by the user in Entitlements. | ✔ | ||
The App Store associated to the entitlement_id. | |||
The name of the advertiser’s app in Kochava and all associated apps in account that have Store Credentials saved. | |||
Indication if subscription is within a free trial period. The logic is based on the date_occured for the event SubscriptionTrialBegin using the Trial duration from the Entitlement setup by the user. | |||
The subscription renewal duration entered by the user in Entitlements. | |||
Cost of the subscription renewal, entered in Entitlements. | ✔ | ||
Reason for subscription being in pending cancel state (billing issue, auto renew turned off). | ✔ | ||
The date the subscription first changed to pending cancel. | |||
The date the subscription will be canceled if not recovered. | ✔ | ||
Any identities sent via SDK with the subscription event. Can be username, email or CRM ID. | |||
The receipt id from the original receipt at the beginning of the subscription |
Field Name | Description |
Type
|
May be Null
|
---|---|---|---|
The entitlement label(s) associated to entitlement_id set up by the user in Entitlements | ✔ | ||
The App Store associated to the entitlement_id. | |||
The name of the app in Kochava and all associated apps in account | |||
Indication if subscription is within a free trial period. The logic is based on the date_occured for the event SubscriptionTrialBegin using the Trial duration from the Entitlement setup by the user. | |||
The subscription renewal duration entered by the user in Entitlements. | |||
Cost of the subscription renewal, entered in Entitlements. | |||
Reason for subscription being in pending cancel state (billing issue, auto renew turned off). | ✔ | ||
The date the subscription first changed to pending cancel. | ✔ | ||
The date the subscription will be canceled if not recovered. | ✔ | ||
The entitlement_ID the user entered in Entitlements that is associated with the receipt from the payment provider. | |||
subscriber_id | |||
The most recent receipt id for the subscription | ✔ | ||
Subscription is still active for the reporting period. | |||
The subscription is in a free trial. | |||
The total sum of revenue generated for this subscription | ✔ | ||
The date of the next renewal. | ✔ | ||
The annual monthly recurring revenue for the renewal. | ✔ | ||
The date the membership first started. | |||
The earliest date for the current subscription started without any lapse. | ✔ | ||
Indicates if the customer has a 1 year subscription. |