Data Specification
This document contains the specifications for the Cohort Long-form ingress data processed by the Kohort system. All fields are required unless specified otherwise. Fields marked Optional are only optional where agreed during onboarding, in discussion with your implementation manager.
Field | Type | Description |
Dimensions |
|
|
registration_date | date | The registration date of a cohort in the format yyyy-MM-dd. This is when a customer is registered for the service but not necessarily transacted |
activity_date | date | The activity date for a given cohort is in the format yyyy-MM-dd. |
category_country | string | Optional: The value of the country pertaining to a segment. E.g. will contain values like US or AU |
category_platform | string | Optional: The value of the platform pertaining to a segment. E.g. will contain values like IOS or ANDROID |
category_channel | string | The value of the channel pertaining to a segment. E.g. Have to be one of the values Paid, Organic or Blended |
category_[name] | string | Optional: Additional columns containing the values of categories pertaining to a segment. E.g. a column with the title category_network will contain values like Google Adwords, Facebook etc.
Values must not use the “|” (pipe) character, as this is reserved. |
Measures |
|
|
active_users | int | The number of unique users that have interacted with the product. This also includes users that have transactions occurring where they are not using the app themselves. |
gross_revenue_[name] | float | The gross amount customers spent during transactions (e.g. in-app purchases). This definition should match up to what you use for your revenue budgets.
You can provide multiple revenue types in different fields. E.g. you can provide gross_revenue_iap for in-app purchases and gross_revenue_ads for ad revenue
Standardised names to be used: gross_revenue_iap gross_revenue_ads -> Total revenue from ads gross_revenue_ads_banners gross_revenue_ads_interstitial |
net_revenue_[name] | float | Optional: If the margin varies noticeably by transaction, provide the net revenue for a more detailed analysis on margins |
marketing_spend | float | Optional: The total marketing spend. If you do not receive marketing spend per cohort per day, add the full value for the cohort where registration_date = activity_date and 0 where registration_date != activity_date. |
paying_users | int | The number of unique users that spent money (this value must be less or equal to active_users). |
ad_users | int | Optional: The number of unique users that watched an ad (this value must be less or equal to active_users). |
transactions | int | The number of user transactions |
first_time_payers | int | Optional: The number of first-time payers |
ad_views | int | Optional: The number of ad views by users |
impressions_banners | int | Optional: The number of banner impressions |
impressions_rewarded | int | Optional: The number rewarded impressions |
impressions_interstitial | int | Optional: The number of interstitial impressions |
Categories, Values & Segments
Throughout the file specification, we use categories, category values, and segments.
Categories classify users by attributes like country, platform, or channel. Each category has values (e.g., country: US, UK, IT). Combining values across categories creates segments, such as US|ANDROID|PAID.
During onboarding, we'll discuss mapping and rollup rules (e.g., grouping small countries into 'Other') to create a segmentation structure that balances reporting detail and forecast accuracy.
For more details, see our Introduction to Segmentation article.
For situations where you have additional important information regarding user registrations and marketing spend that does not cleanly map to this data specification, see our Handling SKAdNetwork and Unattributed Spend article.
Examples
registration_date | activity_date | category_country | category_platform | category_channel | active_users | gross_ revenue_ iap |
2023-01-01 | 2023-01-01 | US | ANDROID | PAID | 1068 | 534 |
2023-01-01 | 2023-01-02 | US | ANDROID | PAID | 503 | 498 |
2023-01-01 | 2023-01-01 | US | IOS | ORGANIC | 492 | 557 |
2023-01-01 | 2023-01-01 | SKAN | IOS | BLENDED | 492 | 557 |