You may see a message like:
“A task in this workflow was skipped because Google Customer Match is still processing data that was sent by a previous workflow. It can take Google up to 48 hours to finish processing data. Amperity will only send data to Google Customer Match when Google Customer Match is not processing data.”
This usually appears when sending audiences to Google Customer Match, and sometimes manual resend attempts don’t work either.
This article explains why this happens and how to fix it.
Problem:
Some users noticed that their Google Ads campaign failed to upload audiences to Google Customer Match.
Even after trying to resend the audience manually from the Campaigns page, the uploads still didn’t go through.
In a few cases, users also saw unusual audience-size differences — for example, an audience of about 360K in Amperity showing up as only 130K in Google Ads.
Root Cause:
There are two common reasons for this behavior:
1. Google Is Still Processing a Previous Upload
- When Google’s Customer Match job is still in a RUNNING state, Amperity pauses new uploads to avoid conflicts.
- This is normal — Google’s API can take up to 48 hours to fully process an audience.
- During this time, any new uploads to the same audience will be skipped automatically.
2. Multiple Subaudiences Share the Same Audience Name
- In some cases, different subaudiences may map to the same audience name in Google Ads.
- This happens when the Google Ads destination is configured to use only the destination name in audience naming, without a unique identifier (like campaign name or subaudience ID).
- Because Google’s Customer Match replaces existing lists instead of appending to them, this can cause subaudiences to overwrite each other’s data.
Solution:
Here’s what you can do to prevent upload failures and overwriting issues:
1. Wait for Google’s processing to finish
- Before resending, check that the previous upload is no longer showing as RUNNING. It can take up to 48 hours for Google to finish processing.
2. Update the audience naming logic
- Edit your Google Ads destination configuration to include a unique identifier in the audience name, such as: Campaign name, Group name, Subaudience ID
- This ensures each upload creates its own distinct audience and avoids conflicts.
Helpful Tips:
- Always use unique naming conventions for audiences sent to replace-type destinations like Google Customer Match.