A temporary issue with the Facebook datasources with attribution setting selected (ex. facebookads_insights_adconversion) caused blank attribution settings to be loaded into the table. Because attribution_setting is a part of the index, days that were loaded with and without the issue had duplicate rows inserted.
Resolution:
Identify any days with duplicate rows, one containing a blank attribution setting, and one containing a valid attribution setting. In most cases, these rows were limited to early November 2024. If duplicates are found, set the datasource to “Replace Date Range” and reload the affected range. Set the upload style back to what it was after loading successfully.
March 2025
Google Ads duplication / inflated metrics
Issue:
Google Ads updated Enum values as part of their upgrade from v17 to v18 as explained here. This ad_network_type field is a part of the index in the datasource and a part of the unique IDs in ADL models. When the Alli Data connector was upgraded from v17 to v19 on 3/27/2025, rows that had been loaded before and then were loaded after the version update inserted duplicate rows because of the differing Enum values for the indexed column. This causes duplication from the datasource through the ADL layer.
Resolution:
The ADL team kicked off 30-day, Replace Date Range backfills for googleads_insights_ad and googleads_insights_campaign on 3/28/2025 upon discovery of the issue. This has yielded success for affected customers. If users continue to see Google Ads duplication, they should look into ADL datasources that have ad_network_type selected, run Replace Date Range backfills for the affected date range, and then run a Deployment=true (full-refresh) for the ADL refresh apps. Users should also be aware of the different Enum values in the case where they have specific logic for the values of ad_network_type.
JavaScript errors detected
Please note, these errors can depend on your browser setup.
If this problem persists, please contact our support.
