Starting June 23, 2022, attempting to create a CampaignSharedSet with a shared_set that has a status of REMOVED will cause a MutateError.RESOURCE_NOT_FOUND error in the Google Ads API.

There will also be a one-time change to automatically update CampaignSharedSet entities to a status of REMOVED if they contain a shared_set with a status of REMOVED. Because the shared_set already has a REMOVED status, this won’t impact any active campaigns since we’re only changing CampaignSharedSet entities that don’t currently serve.

Where can I get support?

If you have questions, please reach out to us on the forum or at [email protected]. - Devin Chasanoff, on behalf of the Google Ads API Team

Starting June 23, 2022, attempting to create a CampaignSharedSet with a shared_set that has a status of REMOVED will cause a MutateError.RESOURCE_NOT_FOUND error in the Google Ads API.

There will also be a one-time change to automatically update CampaignSharedSet entities to a status of REMOVED if they contain a shared_set with a status of REMOVED. Because the shared_set already has a REMOVED status, this won’t impact any active campaigns since we’re only changing CampaignSharedSet entities that don’t currently serve.

Where can I get support?

If you have questions, please reach out to us on the forum or at googleadsapi-support@google.com.

- Devin Chasanoff, on behalf of the Google Ads API Team

Correct usage	operations: { create: { user_identifiers { hashed_email: hash(“[email protected]”) }, user_identifiers { hashed_email: hash(“[email protected]”) } } } operations: { create: { user_identifiers { hashed_email: hash(“[email protected]”) }, user_identifiers { hashed_email: hash(“[email protected]”) } } }
Incorrect usage	operations: { create: { user_identifiers { hashed_email: hash(“[email protected]”) }, user_identifiers { hashed_email: hash(“[email protected]”) }, user_identifiers { hashed_email: hash(“[email protected]”) }, user_identifiers { hashed_email: hash(“[email protected]”) } } }

UserData is used for Customer Match and store sales uploads. In a given create/remove UserData operation, each set of user_identifiers should be for a single user.

Note that the same total amount of data can be sent in a single request, but each set of user_identifiers must represent a single person.

If the number of user_identifiers for a single set exceeds the new limit of 20, a TOO_MANY_USER_IDENTIFIERS error will be generated.

This will be applied to the two Google Ads API methods that provide UserData uploads:

• OfflineUserDataJobService.AddOfflineUserDataOperations
• UserDataService.UploadUserDataRequest

If you have any questions or need additional help, contact us via the forum.

David Wihl, Google Ads API Team