Overview
In some cases, an Amperity Journey workflow may not populate audience data in Google Ads, even though other standard campaigns are sending data successfully. In this scenario, the workflow may appear to execute normally, but no audience is created or updated in Google Ads.
This issue is not limited to a specific journey and can occur in any journey or campaign that sends audience data to Google Ads, depending on Google Ads processing status and journey configuration.
Observed Warning
During journey execution, the following warning may appear in Amperity:
A task in this workflow was skipped because Google Ads is still processing data that was sent by a previous workflow.
It can take Google Ads up to 48 hours to finish processing data.
Amperity will only send data to Google Ads when Google Ads is not processing data.
In this situation, other campaigns may populate successfully, while the affected journey does not send audience data.
What This Warning Means
This warning indicates that:
Google Ads is still processing previously sent audience data
While this processing is ongoing, Amperity temporarily pauses new audience sends
This behavior is expected and helps prevent overlapping or conflicting uploads
This is a temporary condition and does not indicate a permanent error or misconfiguration.
Possible Causes
This issue commonly occurs due to one or both of the following reasons:
Google Ads Processing Delay
Google Ads may take up to 48 hours to process previously sent audience data. During this time, Amperity delays sending new audiences.
Zero-Record Hydration in Journey Nodes
Journey workflows often include multiple nodes that send audiences sequentially.
If a journey node has a hydration result of 0 records, that specific audience will not populate in Google Ads, even if other nodes in the same journey contain valid data.
Recommended Actions
To resolve the issue and prevent it from recurring, the following actions are recommended:
Update Audience Naming in the Data Template
Ensure the Google Ads data template uses the Group Name placeholder so that each journey node sends a unique audience.
Recommended format:
Incredible Audience Amperity - {{Group Name}}
Verify Hydration Results
Confirm that all journey nodes have non-zero hydration results before sending data.
Allow Google Ads Processing to Complete
If Google Ads is processing previously sent data, wait up to 48 hours and then retry the journey workflow.
Additional Notes
This behavior applies to both journeys and campaigns
Campaign data template documentation is also applicable to journeys
The issue is related to external platform processing and audience data conditions, not to workflow failures
Once Google Ads completes processing and all journey nodes contain valid data, the workflow should populate successfully.
Support
If the issue persists after validating hydration results and allowing sufficient processing time, please contact Amperity Support for further assistance.