Clarification on data readiness time in Campaign Manager 360 API

[Devel Vivaki]

We have a scheduled batch process that calls several platform APIs (including Campaign Manager, DV360, Google Ads, etc.).

The batch is scheduled to run daily at 5 AM CET, and the Campaign Manager API is the first to be called. We request data for the last 30 days, using explicit start and end dates (we're not using date keywords like YESTERDAY, LAST_30_DAYS, etc.).

Everything works consistently for dates older than 2 days ago.
However, for yesterday’s data, results are inconsistent — sometimes the API returns the expected data, other times it returns zero rows, without any errors.

In the Campaign Manager UI, our time zone is set to Italian time (CET), and we’re also passing this time zone when calling the API.

When we re-run the same batch later in the morning (e.g., after 10 AM CET), the API returns the correct data for yesterday.

Question:
Could you please clarify what time the data for the previous day becomes fully available in Campaign Manager?
What is the recommended time to run the batch to ensure complete and reliable data for the day before?

[DCM API (DoubleClick Campaign Mgr)]

Hi,

Thank you for reaching out to the DCM API support team.

Find the answers below for your queries.

Could you please clarify what time the data for the previous day becomes fully available in Campaign Manager?

• In Campaign Manager 360, impression and click data for the previous day is typically updated every 3-4 hours, while conversion data is updated roughly every 6 hours.
• Cross-environment conversion data is updated every 24 hours, according to the help center article. 
• While data is generally processed quickly, there can be rare instances where additional data becomes available later due to complex processing, but this is usually within 30 days. 

What is the recommended time to run the batch to ensure complete and reliable data for the day before?

• CM360 often experiences higher latency between ~2 AM to 8 AM US Eastern Time. Reports submitted during that window may take longer or fail due to system load.
• Scheduled reports make the best use of reporting resources because they are run in bulk and are guaranteed not to execute until the previous day's data has completed processing. This means that using scheduled (asynchronous) reporting ensures that the data for the prior day is finalized and available before the report runs. We would recommend following our Reporting Best Practices guide for more information.

I hope it helps.

Thanks,
 

DCM API Team

Feedback
How was our support today?

               
[2025-08-04 21:53:18Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01sy0PZ:ref" (ADR-00328189)