API migration issues on reporting offline coversions

[Gdula Łukasz]

Hi,

We have recently implemented offline conversion over the new API and we can not see any conversions in the reports. I've double checked everything, the API request does not report any error and I have no clue where to look for a potential problem.

There were some changes in the payload, previous version of the API used a text label of the conversion target (new one requires ID which I've obtained the corresponding one from API), cant think about anything else except the manager account parameter set as a required for the call.

One of the worrying things is that every time I try to query click_view with one of the click ids, its not finding it there which seems a bit odd.

Any suggestions on how to approach this situation ?

[Google Ads API Forum Advisor]

Hi Gdula,

Could you send us a 'DEBUG' log level request and response log of raw API communications of the click_view report and offline conversion upload?

The request and response appears similar to the JSON Mappings in our REST documentation with additional headers and information such as request Id. Here are logging instructions for our Java, .NET, PHP, Python, Ruby and Perl Ads API Client Libraries.

If you are using our REST interface then the full multi line curl command line is a request log and adding curl command line option '-i' will also generate a response log.

You may send the requested information via "Reply to author" or via googleadsa...@google.com with a link to this forum post added to the new thread.

Regards,

Aryeh Google Ads API Team

P.S. There can be many reasons to have this issue when migrating, you can only upload to the effective conversion account, and the resource name of the conversion action is used to specify the conversion action.

Regarding manager account set as parameter, Here's our login customer Id guide and migration guide.

Any account returned by Get Account Hierarchy when you you don't specify manager ID and login customer ID can be accessed by your refresh token you used to make the API call.

Any account returned by List Accessible Accounts when using a specific refresh token doesn't need the login customer Id.

Another property of those accounts returned by List Accessible Accounts is they are the only accounts that can be a login customer Id for the specific refresh token making the API call.

A visual way to explain this is to imagine that the same Google account that generated the refresh token was to access an account in the Ads UI. They will see all the the accounts that List Accessible Accounts returns in the top right drop down list when you click the circle representation of the user in the UI. These are accounts the user has direct access to. If an account in that list is an MCC with child accounts attached, then to see the child accounts you would select that MCC in the top right of the UI and then the child accounts are accessible in the top left - middle accounts drop down list box in the UI. These are the same accounts that Get Account Hierarchy shows. 

To access accounts that are in the top left - middle accounts drop down list box via the API you would put the selected account in the top right list in the UI as login customer Id, and you would put the selected account in the top left - middle accounts drop down list box as the operating customer.
 

ref:_00D1U1174p._5004Q2cW1cN:ref