Hi Viktor,
Thank you for posting your concern.
Let me discuss first the ConversionActionOperation. This operation is indeed
supported in Batch Processing according to this guide. However, this operation
is focused on managing conversion action such as creating/adding/removing it
and not for up
the mutate operation
ConversionActionOperation. Is it possible to use this mutation to upload
multiple Offline Conversions? If not possible I have to develop my own
async logic right?
Best Regards Viktor
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our b
Hi Anton,
By default either *all* operations succeed in a given *mutate* request or
*all* operations fail. Using your example, if a single *mutate* request
contains 100 operations and one of them fails, then *none* of the
operations will be applied.
The good news is that you can change this be
I'm uploading multiple offline conversions at once using
OfflineConversionFeedService (operation: mutate).
I started uploading 100 conversions at once but some of them are expired
and I'm getting this error message: OfflineConversionError.EXPIRED_CLICK.
This is perfectly OK, because some of the
