The True Consent Mode (TCM) feature is the solution we have developed in Adtriba to provide attributions to those conversions we are not able to track because of not-given consent.
This solution is able to give attribution to the conversions for which we are not able to have a customer journey, based on those that we are able to track. The TCM is made with an extrapolation technique.
How does TCM works?
We require the information regarding how many conversions are registered in the backend of our customers. This information needs to be shared with Adtriba using our Data Exchange service. Comparing the numbers from the backend with the tracking logs we are able to obtain the number of conversions that was not tracked due to consent. Then these conversions are distributed proportionally (with an extrapolation method) to the attributions on the day the conversion took place.
Example:
Imagine that for the time period between 01.01.2023 and 15.01.2023 we track 5.000 conversions, and we know from you backend that there were 1.000 extra conversions for a specific report. After adding those non-tracked conversions, the distribution of attribution per campaign (obviously also per channel) remains the same because we gave attribution to those non-tracked conversions according to what the data says about the tracked conversions.
How is the format?
In order to send us the correct data format, please read this section carefully and adequate your export according to your conditions.
Column Name | Data Type | Notes/Specifications |
date | date | YYYY-MM-DD format. MANDATORY |
costumer_type | string | new/returning. OPTIONAL* |
device_type | string | onsite/mobile. OPTIONAL.** |
total_conversions | int | Mandatory. Number of conversion for that date. |
total_revenue | double |
|
brand | string | MANDATORY. It is used to segment between brands |
country | string | MANDATORY. Example: DE. Used to segment between countries |
conversion_name | string | example: 'Transaction' |
currency | string | By default we assume EUR |
*costumer_type: In case the performance report is split into new and returning customers, must appear 2 rows for each date. 1 row with customer_type = new, and the second row with customer_type = returning.
In case there is no split in the performance report, all clients (rows) will treated as new.
**device_type: Same procedure as previous parameter, if the performance report makes difference between devices (it all depends on the structure you have in Adtriba). Be default, we assume they are ‘web’ type.
How is the data exchange done?
To provide Adtriba your data conversions from your backend, you will need export data via S3. Check out more information about data exchange with S3 in our Help Center: https://help.adtriba.com/en/articles/4879179-hosted-managed-data-exchange
The specific destination for this purpose will be:
s3://adtriba-import-{DATA_EXCHANGE_ID}/dwh/backend_conversions
Note: Remember that {DATA_EXCHANGE_ID} refers to you account ID in Adtriba.
Format required: It can be .csv, .json or .parquet
The export must be made before 23:59 (example: 22:00PM)
If you need more information, don’t hesitate and contact us in support@adtriba.com.