Automate your data delivery and eliminate manual exports. Keep your data warehouse always up to date without any manual effort.
Each export can be configured according to several parameters:
Frequency
Data set
Table granularity
Attribution model(s)
View
Automatic exports can be configured directly from the interface (admin access required).
Our team can assist you with the initial setup if needed.
Daily
Exports are run daily, at around 2 a.m. local time for the customer, based on the previous day's data, recommended for most use cases.
Bi-hourly
Export data every two hours for the current day, for near real-time monitoring (please contact the ThankYou Analytics team).
Exported data reflects the latest processed data available in ThankYou Analytics.
Weekly
Landing pages (optional)
Every Saturday at 10 a.m. UTC, exports are run on data from the previous 7 days. This frequency allows for manual cost updates and advertising connector data, which may change over time, to be updated.
Acquisition (optional)
Every Sunday at 10 a.m. UTC, data from the previous 7 days is exported. This frequency allows for the updating of manually added costs and advertising connector data, which may change over time.
Monthly
Landing pages (optional)
Every second Saturday of the month at 10 a.m. UTC, data from the last 60 days is exported. This frequency allows manually added costs to be updated.
Acquisition (optional)
Every second Sunday of the month at 10 a.m. UTC, data from the last 60 days is exported. This frequency allows manually added costs to be updated.
6 datasets can be exported:
Global
Acquisition
Conversion paths
Landing pages
Conversion dimensions
Products list (E-commerce object)
Channels (Obsolete and not maintained from March 1, 2025)
Each dataset is described in the "Data structure" section.
The tables are specific to each data set and each customer. By default, each table groups data for all exported dates.
It is also possible to break them down further and have one table per day, depending on your analysis needs.
The “Acquisition,” “Conversion Paths,” and “Conversion Dimensions” data exports can be configured to export data using one or more attribution models.
If no attribution model is configured, the data is exported using the default attribution model.
Exports of the “Acquisition,” “Conversion Paths,” and “Conversion Dimensions” data sets can be configured to export data with a specific view.
If no view is configured, the data is exported with the view named “Main View.”
Table naming convention: <client_id>[_<prefix>][_<view_id>]_global
Attribute | Type | Description |
date | DATE | Date in yyyy-mm-dd format in the customer's time zone configured in ThankYou Analytics. |
visits | INT | Visits depend on the identification configured in the solution settings. Visits are the sum of deterministic visits (with consent) and probabilistic visits (without consent). |
total_conversions | FLOAT | Total conversions collected with or without consent. |
entrances | INT | An entrance is the first page viewed by a user when coming from an external traffic source. Detection is based on URL parameters (e.g., utm_source) or the previous page's domain name (e.g., google.com). |
responses | INT | A response corresponds to an entrance for which the user has shared their consent status, whether positive (consent) or negative (refusal). Unlike an entrance, a response excludes users who leave the site without sharing their consent status. The response is sent when the user chooses their consent status, and also for each subsequent new entrance. |
optins | INT | An opt-in corresponds to an entrance for which the user has given a positive response to the consent banner. The opt-in is sent when the user gives consent, and also for each subsequent new entrance. |
total_revenue | FLOAT | Sales revenue depends on the attribution model chosen in the solution settings. Sales revenue is the sum of deterministic and probabilistic sales revenue. |
average_shopping_cart | FLOAT | Sales revenue / conversions. |
total_margin | FLOAT | Attributed margin depends on the attribution model chosen in the solution settings. Margin is the sum of deterministic and probabilistic sales revenue. |
Table naming convention: <client_id>[_<prefix>][_<view_id>]_acquisition
Attribute | Type | Description |
client_id | STRING | Unique client identifier. |
client_name | STRING | Client name. |
view_name | STRING | Name of the view used (default "Main view"). |
date | DATE | Date in yyyy-mm-dd format in the client's time zone configured in ThankYou Analytics. |
attribution_model_id | STRING | Unique identifier of the selected attribution model. One of: last, first, linear, custom. |
attribution_model_name | STRING | Name of the selected attribution model. |
channel_id | STRING | Unique identifier of the channel. |
channel_name | STRING | Channel name. |
subChannel_id | STRING | Unique identifier of the sub-channel. |
subChannel_name | STRING | Sub-channel name. |
detail_name | STRING | First-level detail name. |
detail2_name | STRING | Second-level detail name. |
detail3_name | STRING | Third-level detail name. |
detail4_name | STRING | Detail ID name. |
device_id | STRING | Unique device identifier. |
deterministic_visits | FLOAT | Deterministic visits are measured via a tracker placed on the user's browser when consent is given. Visits are then attributed to the acquisition channel according to the configured identification. |
probabilistic_visits | FLOAT | Probabilistic visits result from modeling the volume of visits made by users who refuse consent. |
total_visits | FLOAT | Visits attributed to acquisition channels depend on the identification configured in the solution settings. Attributed visits are the sum of deterministic (with consent) and probabilistic (without consent) visits. |
entrances | INT | An entrance is the first page viewed by a user when coming from an external traffic source. Detection is based on URL parameters (e.g., utm_source) or the previous page's domain name (e.g., google.com). |
responses | INT | A response corresponds to an entrance for which the user has shared their consent status, whether positive (consent) or negative (refusal). Unlike an entrance, a response excludes users who leave the site without sharing their consent status. The response is sent when the user chooses their consent status, and also for each subsequent new entrance. |
optins | INT | An opt-in corresponds to an entrance for which the user has given a positive response to the consent banner. The opt-in is sent when the user gives consent, and also for each subsequent new entrance. |
deterministic_conversions | FLOAT | Deterministic conversions are measured via a tracker placed on the user's browser when consent is given. Conversions are then attributed to the acquisition channel according to the configured attribution model. |
probabilistic_conversions | FLOAT | Probabilistic conversions result from modeling the volume of conversions made by users who refuse consent. |
total_conversions | FLOAT | Total conversions collected with or without consent. |
deterministic_revenue | FLOAT | Deterministic sales revenue is measured via a tracker placed on the user's browser when consent is given. Sales revenue is then attributed to the acquisition channel according to the configured attribution model. |
probabilistic_revenue | FLOAT | Probabilistic sales revenue results from modeling the sales revenue generated by users who refuse consent. |
total_revenue | FLOAT | Attributed sales revenue depends on the attribution model chosen in the solution settings. Sales revenue is the sum of deterministic and probabilistic sales revenue. |
average_shopping_cart | FLOAT | Sales revenue / conversions. |
impressions | FLOAT | An impression is counted each time your ad is displayed. |
clicks | FLOAT | When a user clicks on your ad. |
cost | FLOAT | Costs correspond to the sum of manual and advertising expenses. |
cpc | FLOAT | Cost Per Click. Cost / Clicks. |
cpe | FLOAT | Cost Per Entrance. Cost / Entrance. |
roas | FLOAT | Return On Ads Spend. Sales revenue / Cost x 100. This indicator shows the sales revenue generated in relation to the cost. |
cpa | FLOAT | Cost Per Acquisition. Cost / Conversions. |
response_rate | FLOAT | Response rate is total responses / total entrances. It helps ensure the quality of traffic generated by campaigns. A low response rate indicates a high bounce rate when the consent banner is displayed. |
addressability_rate | FLOAT | Addressability rate is total opt-ins / total entrances. It shows the ability to address a marketing message to your audience, via email marketing, retargeting, etc. |
optin_rate | FLOAT | Opt-in rate is total opt-ins / total responses. |
cos | FLOAT | Cost Of Sales. Costs / Sales revenue x 100. This indicator shows the average cost per sale. |
click_rate | FLOAT | Click rate is total clicks / total impressions. |
cpm | FLOAT | Cost Per Mille. Costs / Impressions x 1000. This indicator shows the cost per 1000 impressions. |
cpv | FLOAT | Cost Per Visit. Cost / Visits. |
deterministic_margin | FLOAT | Deterministic margin is measured via a tracker placed on the user's browser when consent is given. Margin is then attributed to the acquisition channel according to the configured attribution model. |
probabilistic_margin | FLOAT | Probabilistic margin results from modeling the margin generated by users who refuse consent. |
total_margin | FLOAT | Attributed margin depends on the attribution model chosen in the solution settings. Margin is the sum of deterministic and probabilistic margin. |
poas | FLOAT | Profit on Ad Spend. Calculates the real profit generated by advertising, after deducting the cost of the products. Formula: Margin / Advertising cost. This indicator measures the net profit of your campaigns. |
view_id | STRING | Unique view identifier. |
Table naming convention: <client_id>[_<prefix>][_<view_id>]_orders_attribution
Attribute | Type | Description |
order_id | STRING | Unique conversion identifier. |
revenue | FLOAT | Conversion sales revenue. |
consent | BOOL | Consent status associated with the conversion. |
date | TIMESTAMP | Conversion date in ISO 8601 format and UTC time zone. |
date_with_tz | TIMESTAMP | Conversion date in ISO 8601 format and the time zone defined by the client in ThankYou Analytics settings. |
device | STRING | Unique device identifier associated with the conversion (desktop, smartphone, tablet, etc.). |
os | STRING | Unique operating system identifier associated with the conversion (Android, iOS, Windows, Mac, etc.). |
client_type | STRING | Unique client type identifier (browser, mobile app). |
client_name | STRING | Client name from user-agent analysis (Chrome, Safari, Firefox, Mobile Safari, etc.). |
viewport | STRING | Display area in pixels ("height x width"). For mobile, corresponds to screen size; for desktop, to browser window size. |
voucher | STRING | Discount voucher used during the conversion. |
attribution_model | STRING | Attribution model applied for calculating "touch_weight" and "touch_amount". |
touch_index | INT | Chronological index of interactions (index 0 is the first touch, index 1 the next, etc.). |
touch_weight | FLOAT | Weight given to each interaction. Calculated based on the "attribution_model" defined in ThankYou Analytics settings. |
touch_channel_id | STRING | Unique channel identifier associated with the interaction. |
touch_subchannel_id | STRING | Unique sub-channel identifier associated with the interaction. |
touch_cutting_id | STRING | Unique first-level detail identifier associated with the interaction. |
touch_cutting2_id | STRING | Unique second-level detail identifier associated with the interaction. |
touch_cutting3_id | STRING | Unique third-level detail identifier associated with the interaction. |
touch_cutting4_id | STRING | Unique detail ID associated with the interaction. |
touch_amount | FLOAT | Portion of the conversion amount associated with the interaction. |
touch_landing_page | STRING | Landing page associated with the interaction. |
margin | FLOAT | Conversion margin associated to the interaction. |
touch_margin | FLOAT | Portion of the conversion margin associated with the interaction. |
custom_attributes | VARIANT (SF) / JSON (BQ) | Various conversion dimensions associated with the interaction. |
ecommerce_objects | VARIANT (SF) / JSON (BQ) | Array containing the elements of the e-commerce object. |
Table naming convention: <client_id>[_<prefix>][_<view_id>]_targets
Attribute | Type | Description |
id | STRING | Landing page URL. |
date | DATE | Date in yyyy-MM-dd format in the client's time zone configured in ThankYou Analytics. |
attribution_model | STRING | Unique identifier of the selected attribution model. One of: last, first, linear, custom. |
device_id | STRING | Unique device identifier associated with the element. The value "all" groups all other possible identifiers |
entrances | INT | An entrance is the first page viewed by a user when coming from an external traffic source. Detection is based on URL parameters (e.g., utm_source) or the previous page's domain name (e.g., google.com). |
responses | INT | A response corresponds to an entrance for which the user has shared their consent status, whether positive (consent) or negative (refusal). Unlike an entrance, a response excludes users who leave the site without sharing their consent status. The response is sent when the user chooses their consent status, and also for each subsequent new entrance. |
optins | INT | An opt-in corresponds to an entrance for which the user has given a positive response to the consent banner. The opt-in is sent when the user gives consent, and also for each subsequent new entrance. |
deterministic_conversions | FLOAT | Deterministic conversions are measured via a tracker placed on the user's browser when consent is given. Conversions are then attributed to the acquisition channel according to the configured attribution model. |
probabilistic_conversions | FLOAT | Probabilistic conversions result from modeling the volume of conversions made by users who refuse consent. |
total_conversions | FLOAT | Total conversions collected with or without consent. |
deterministic_revenue | FLOAT | Deterministic sales revenue is measured via a tracker placed on the user's browser when consent is given. Sales revenue is then attributed to the acquisition channel according to the configured attribution model. |
probabilistic_revenue | FLOAT | Probabilistic sales revenue results from modeling the sales revenue generated by users who refuse consent. |
total_revenue | FLOAT | Attributed sales revenue depends on the attribution model chosen in the solution settings. Sales revenue is the sum of deterministic and probabilistic revenue. |
impressions | FLOAT | An impression is counted each time your ad is displayed. |
clicks | FLOAT | When a user clicks on your ad. |
click_rate | FLOAT | Clicks / Impressions. |
response_rate | FLOAT | Response rate is total responses / total entrances. It helps ensure the quality of traffic generated by campaigns. A low response rate indicates a high bounce rate when the consent banner is displayed. |
addressability_rate | FLOAT | Addressability rate is total opt-ins / total entrances. It shows the ability to address a marketing message to your audience, via email marketing, retargeting, etc. |
conversion_rate | FLOAT | Conversion rate is total conversions / total entrances. |
optin_rate | FLOAT | Opt-in rate is total opt-ins / total responses. |
deterministic_visits | FLOAT | Deterministic visits are measured via a tracker placed on the user's browser when consent is given. Visits are then attributed to the acquisition channel according to the configured identification. |
probabilistic_visits | FLOAT | Probabilistic visits result from modeling the volume of visits made by users who refuse consent. |
total_visits | FLOAT | Visits attributed to acquisition channels depend on the identification configured in the solution settings. Attributed visits are the sum of deterministic (with consent) and probabilistic (without consent) visits. |
deterministic_margin | FLOAT | Deterministic margin is measured via a tracker placed on the user's browser when consent is given. Margin is then attributed to the acquisition channel according to the configured attribution model. |
probabilistic_margin | FLOAT | Probabilistic margin results from modeling the margin generated by users who refuse consent. |
total_margin | FLOAT | Attributed margin depends on the attribution model chosen in the solution settings. Margin is the sum of deterministic and probabilistic margin. |
Table naming convention: <client_id>[_<prefix>][_<view_id>]_custom_attributes[_<customAttributes>]
Attribut | Type | Description |
client_id | STRING | Unique client identifier |
client_name | STRING | Client name |
view_id | STRING | Unique view identifier |
view_name | STRING | Name of the view used (default "Main view") |
date | DATE | Date in yyyy-mm-dd format in the client's time zone configured in ThankYou Analytics |
attribution_model_id | STRING | Unique identifier of the selected attribution model. One of: last, first, linear, custom |
custom_attributes | STRING | Various conversion or audience dimensions associated with the interaction. Each dimension is shown in its own column. |
total_conversions | FLOAT | Total conversions collected. |
consented_conversions | FLOAT | Conversions collected with consent. |
not_consented_conversions | FLOAT | Conversions collected without consent. |
total_revenue | FLOAT | Attributed sales revenue depends on the attribution model chosen in the solution settings. |
Table naming convention: <client_id>[_<prefix>][_<view_id>]_ecommerceProductsList
Attribut | Type | Description |
client_id | STRING | Unique client identifier |
client_name | STRING | Client name |
view_id | STRING | Unique view identifier |
view_name | STRING | Name of the view used (default "Main view") |
date | DATE | Date in yyyy-mm-dd format in the client's time zone configured in ThankYou Analytics |
device_id | STRING | Unique device identifier associated with the element. The value "all" groups all other possible identifiers |
ecommerce_object_name | STRING | E-commerce object name defined in ThankYou Analytics settings |
ecommerce_object_id | STRING | Unique identifier for the E-commerce object |
product_id | STRING | Unique product identifier |
product_name | STRING | Product name |
product_orders | FLOAT | Number of conversions in which the product is included |
product_quantity | FLOAT | Number of products included in conversions |
product_price | FLOAT | Unit price of the product |
product_amount | FLOAT | Product revenue |
Table naming convention: <client_id>[_<prefix>][_<view_id>]_channels
Attribute | Type | Description |
id | STRING | Unique identifier of the element. |
name | STRING | Name given to the element. |
date | DATE | Date in yyyy-mm-dd format in the client's time zone configured in ThankYou Analytics. |
attributionModel | STRING | Unique identifier of the selected attribution model. |
type | STRING | Element granularity. One of: "channel" for a channel, "sub_channel" for a sub-channel, "detail" for a detail. |
parent_channel_id | STRING | If the element is of type "sub_channel" or "detail", this is the unique identifier of the associated channel. |
parent_subchannel_id | STRING | If the element is of type "detail", this is the unique identifier of the associated sub-channel. |
device_id | STRING | Unique device identifier associated with the element. The value "all" groups all other possible identifiers. |
entrances | INT | An entrance is the first page viewed by a user when coming from an external traffic source. Detection is based on URL parameters (e.g., utm_source) or the previous page's domain name (e.g., google.com). |
responses | INT | A response corresponds to an entrance for which the user has shared their consent status, whether positive (consent) or negative (refusal). Unlike an entrance, a response excludes users who leave the site without sharing their consent status. A response is sent when the user selects their consent status, and also for each subsequent new entrance. |
optins | INT | An opt-in corresponds to an entrance for which the user has given a positive response to the consent banner. The opt-in is sent when the user gives consent, and also for each subsequent new entrance. |
deterministic_conversions | FLOAT | Deterministic conversions are measured via a tracker placed on the user's browser when consent is given. Conversions are then attributed to the acquisition channel according to the configured attribution model. |
probabilistic_conversions | FLOAT | Probabilistic conversions result from modeling the volume of conversions made by users who refuse consent. |
total_conversions | FLOAT | Total conversions collected with or without consent. |
deterministic_revenue | FLOAT | Deterministic sales revenue is measured via a tracker placed on the user's browser when consent is given. Sales revenue is then attributed to the acquisition channel according to the configured attribution model. |
probabilistic_revenue | FLOAT | Probabilistic sales revenue results from modeling the sales revenue generated by users who refuse consent. |
total_revenue | FLOAT | Attributed sales revenue depends on the attribution model chosen in the solution settings. Sales revenue is the sum of deterministic and probabilistic sales revenue. |
impressions | FLOAT | An impression is counted each time your ad is displayed. |
clicks | FLOAT | When a user clicks on your ad. |
cost | FLOAT | Costs correspond to the sum of manual and advertising expenses. |
cpc | FLOAT | Cost / Clicks. |
cpe | FLOAT | Cost / Entrance. |
roas | FLOAT | Return On Ads Spend. Sales revenue / Cost x 100. This indicator shows the sales revenue generated in relation to the cost. |
cpa | FLOAT | Cost / Conversions. |
average_shopping_cart | FLOAT | Sales revenue / conversions. |
addressability_rate | FLOAT | Addressability rate is total opt-ins / total entrances. It shows the ability to address a marketing message to your audience, via email marketing, retargeting, etc. |
response_rate | FLOAT | Response rate is total responses / total entrances. It helps ensure the quality of traffic generated by campaigns. A low response rate indicates a high bounce rate when the consent banner is displayed. |
optin_rate | FLOAT | Opt-in rate is total opt-ins / total responses. |
deterministic_visits | FLOAT | Deterministic visits are measured via a tracker placed on the user's browser when consent is given. Visits are then attributed to the acquisition channel according to the configured identification. |
probabilistic_visits | FLOAT | Probabilistic visits result from modeling the volume of visits made by users who refuse consent. |
total_visits | FLOAT | Visits attributed to acquisition channels depend on the identification configured in the solution settings. Attributed visits are the sum of deterministic (with consent) and probabilistic (without consent) visits. |
cos | FLOAT | Cost Of Sales. Costs / Sales revenue x 100. This indicator shows the average cost per sale. |
deterministic_margin | FLOAT | Deterministic margin is measured via a tracker placed on the user's browser when consent is given. Margin is then attributed to the acquisition channel according to the configured attribution model. |
probabilistic_margin | FLOAT | Probabilistic margin results from modeling the margin generated by users who refuse consent. |
total_margin | FLOAT | Attributed margin depends on the attribution model chosen in the solution settings. Margin is the sum of deterministic and probabilistic margin. |
Automatic exports access is managed by admins. Admins can grant access to non-admin users with specific restrictions.
Administrators | Non-admin | |
View exports |
|
|
Set up a new export |
|
|
Disable an export |
|
|
Delete an export |
|
|
Non-admin users can be restricted to:
Specific export destinations (BigQuery, Snowflake, sFTP)
Specific views (data access limited to selected views)
When restricted to specific views, users can only access exports related to those views.
Your data, ready to be activatedThankYou Analytics automatic exports are already available for Google BigQuery and Snowflake.
By connecting your data to your data warehouse, you get direct access to all your marketing journeys, ready to be combined with your business, CRM, and product data.
This allows you to build :
Feed your BI tools (Looker, Power BI, Tableau)
Share data with partners (agencies, affiliates)
Build custom dashboards in your data warehouse
Combine ThankYou data with CRM or internal data
All that’s left is to configure your destination 
