Debugging the conversion tracker created from the API

[s...@nuntiolabs.com]

Hi all, 

we are in the process of testing if the conversion tracker created through the ConversionTrackerService works properly and how one can go about debugging it. 

We ran campaigns and observed over 2.4K clicks but 0 conversions, which is suspicious considering our historical conversion rate of 3%. 

Should we provide the conversion tracker code that the ConversionTrackerService API returns through the mutate operation or the new website conversion tracking tag that looks very different compared to the snippet from the API?

How to debug this?

Thanks,

Sam

[Vincent Racaza (AdWords API Team)]

Hi Sam,

Based on this guide, most conversion types (e.g. AdWordsConversionTracker, AppConversion, etc.) requires you to add a code snippet called a tag that you need to add to your conversion page on your website. So in regards to your question if you need to add the code snippet in your new website, then the answer is yes.

You can check this guide on how to track and import conversions in the API. You can also check this Help Center Article guide on how to add a conversion tracking tag to your website.

Kindly add the conversion tracking tag first in your website and let me know if this solves your issue by recording the conversions already.

Thanks,

Vincent

AdWords API Team

[s...@nuntiolabs.com]

Thanks, Vincent, 

the actual issue is that the code needs to be embedded in the client side website. We've already tested the code snippet on our side and that works. 

They have a dynamic confirmation page for a purchase, so the snippet will load and the html will be generated only after a purchase is made. 

Is there a guide to help us check if the tracking works properly in this case?

Thanks,

Sam

[Vincent Racaza (AdWords API Team)]

Hi Sam,

Since the concern is already more on tracking the code snippet if it works properly on your client's website (since I believe that you don't have access to your client's web pages), and not AdWords API specific, then I suggest to post this concern in the AdWords Community Forum as their team can further assist you on this.