Similar to this topic
We have a Google Ads transfer to bring data into BigQuery. Starting August 8, we are missing data in the p_ads_CampaignBasicStats_[customer_id] table for Demand Gen campaigns (formerly Discovery).
We haven't changed anything on the campaigns or our data transfer configuration. Other campaigns are still showing up in the p_ads_CampaignBasicStats_[customer_id] table, and the Demand Gen campaigns are still showing up in p_ads_CampaignStats_[customer_id]. It seems only the BasicStats table is affected with the missing data.
Did anything change on the Google side with the table transfer for Demand Gen campaigns?
Thanks,
Matt
Hello,
Please reach out to Google Ads Support team
Hello,
Thank you for your engagement regarding this issue. We haven’t heard back from you regarding this issue for sometime now. Hence, I'm going to close this issue which will no longer be monitored. However, if you have any new issues, Please don’t hesitate to create a new issue. We will be happy to assist you on the same.
Regards,
Jai Ade
We have the same problem. No data, no errors for one type of campaigns. Data Transfer uses a deprecated API - will there be any change for Data Transfer and when?
Same thing here. Is there any plan to fix it? @jaia
Hi Matt, l et me share some possible reasons and steps you can take to investigate further:
1. Google Ads API Updates
Google occasionally makes changes to its Ads API, which could impact how certain data points are exported to BigQuery. Even if you haven’t modified your campaigns or data transfer settings, a recent API update might be causing the discrepancy. I’d recommend checking the Google Ads API Release Notes for any recent updates related to Demand Gen campaigns or the CampaignBasicStats table.
2. Differences Between CampaignBasicStats and CampaignStats
These two tables often share overlapping data, but there are subtle differences. If Google recently reclassified Demand Gen campaigns or reassigned certain metrics, that could explain why they’re missing from the BasicStats table.
3. Review Your Transfer Configuration
Even if your configuration hasn’t changed, it’s worth taking another look to make sure:
4. Test or Recreate the Transfer
As a troubleshooting step, try recreating the transfer for a small dataset (e.g., just one customer ID). This will help you confirm whether the issue is due to a configuration error or a temporary bug in the transfer process.
5. Consider Third-Party ETL Tools
If the problem persists, you might want to explore a third-party tool like Windsor.ai. Their connectors for Google Ads and BigQuery are quite robust and can help you unify and cross-check your data more effectively. Many of these tools also offer detailed logs and debugging features, which could make it easier to pinpoint issues like this.
Next Steps
Hope this helps!