|
||||||
Hi PaidMedia Team,
Thanks for getting back to us.
Kindly see below responses to your queries:
1. Is there any way we can do a positive scenario testing, where without using production data we can upload few hundreds of transactions and we get back a SUCCESS response if the formatting is as per documentations?
>> Kindly note that test accounts do not have any clicks to match against when they uploaded and they may encounter "INSUFFICIENT_MATCHED_TRANSACTIONS" error since as mentioned in this tip section which specifically mentioned that in order to avoid the job failing with OfflineUserDataJobFailureReason.INSUFFICIENT_MATCHED_TRANSACTIONS, there must be at least 50 matched transactions in a job. Having said that, you need to upload at least a few hundred transactions so that at least 50 match customers in only the production account. However, only 50 transactions can be uploaded at one time, so multiple uploads to the same job are required. In addition, you need to ensure the conditions mentioned in the above link must be met.
However, in uploading to a test account we can verify that metadata, transaction details and UserData types can be sent successfully. Once this looks OK, you may go with the uploading to a production account using production data of your store sales.
2. What is the max time taken for the OfflineUserDataJob to complete and give back the response?
>> OfflineUserDataJob may take up to 24 hours to complete, however, it may also possible it take upto 72 hours when remove_all and add operation added in same job. That said, you can periodically check the job's status through GoogleAdsService.SearchStream.
3. Can you please give the code sample to refer for validate_only ?
>> We do not have a sample where validate_only is included, however, you may use validate_only in your RunOfflineUserDataJobRequest while running an asynchronous request to run the offline user data job.
Let us know if you have any further questions.
Regards,
|
||||||
|
||||||