Reasons for the data discrepancy
The Ad service → Google BigQuery pipeline automatically and regularly imports data from your ad account to Google Analytics. Also, OWOX BI actualizes data to keep it fresh and valid. Yet, the discrepancy up to 2% might be expected that is caused by the following reasons:
- An ad service may apply the rounding rules to the advertisement costs.
The usage of rounding rules either at a campaign or an API level may cause data discrepancy between ad account and Google Analytics.
- OWOX BI can’t get the exact currency of your ad account via an
ad service’s API. The ad service’s API may not provide OWOX BI with information about the currency used in the ad account. That is why OWOX BI requests the costs in a default currency (for example, USD). And if the currency used by OWOX BI differs from the currency in your ad account, then the currency conversion based on API’s conversion rate might occur. As a result, you may face data discrepancy between ad account and Google Analytics.
- You specify an additional currency in your pipeline settings.
In this case, OWOX BI automatically converts imported costs into this additional currency based on the API Open Exchange Rates.
- An ad service may update information in an ad account retrospectively.
It can be that the ad service automatically cleans the statistics from bot activity, false clicks, etc. for the previous periods. As a result, you may notice the data discrepancy between ad account and Google Analytics. To prevent this kind of data discrepancy, OWOX BI actualizes data within a preset period.
Monitoring of data discrepancy
OWOX BI automatically tracks data discrepancies between your ad account and Google Analytics. You can see the statistics on the Data monitoring page.
The Data monitoring service is available for all the Ad service → Google BigQuery pipelines, except Facebook → Google BigQuery and LinkedIn → Google BigQuery.