I believe the issue arises from using a GCLID that does not belong to the customer id provided.
The API seems to resolve internally TO WHICH MCC that glcid belongs to and then matches the conversionActionId against that customer id. That conversionAction we use is actually NOT DEFINED in the MCC that the glcid belongs to - hence the error is "correct" yet entirely misleading. Adding the conversionAction to the MCC that the glcid and taking THAT conversionActionId will actually work. I've described the whole problem + solution in more detail at https://github.com/googleads/google-ads-php/issues/496#issuecomment-743047543 --- It would be highly appreciated if this behavior would be document somewhere. Cheers Pascal Pascal Landau schrieb am Freitag, 11. Dezember 2020 um 07:12:08 UTC+1: > Hey Xiaoming , > > I'm encountering the exact same problem as Christiano. > > You can find a more extensive explanation in this Github issue > <https://github.com/googleads/google-ads-php/issues/496> (including code > samples and details regarding our account setup). > > Summary: > - conversion action was created through the UI > - I can retrieve the action via API and get it's exact ID, the owners ID > (the MCC account) and the exact resource name in the format "customers/MY > CUSTOMER ID/conversionActions/458214867" > - using this exact id yields the error "This customer does not have an > import conversion action that matches the conversion action provided" > > What's more: Using the another library that does not require the action id > but uses the action name instead works as expected (bases on this example > <https://github.com/googleads/googleads-php-lib/blob/master/examples/AdWords/v201809/Remarketing/UploadOfflineConversions.php> > ). > > PS: I'm happy to send detailed request logs, but the email adress you > posted appears shortened as " googleadsa...@google.com > <https://groups.google.com/> " and the underlying link points to > https://groups.google.com/ > > Cheers > Pascal > > > adsapiforumadvisor schrieb am Dienstag, 1. Dezember 2020 um 20:15:31 UTC+1: > >> Hi Cristiano, >> >> Thank you for reaching out. Could you please send the requested >> information to our email alias googleadsa...@google.com directly for us >> to further investigate? >> >> Thanks and regards, >> Xiaoming, Google Ads API Team >> >> >> [image: Google Logo] >> Xiaoming >> Google Ads API Team >> >> >> ref:_00D1U1174p._5004Q27wUda:ref >> > -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog: https://googleadsdeveloper.blogspot.com/ =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/7bc48e28-16ab-4953-bfa3-58b6e6542e28n%40googlegroups.com.
