{targetid} parameter - keyword IDs in exact/phrase match doesn't show

[Arek Gaładyk]

Hi,

I have set up URL tracking on the keyword level using ValueTrack parameters: "utm_source=google&utm_medium=cpc&utm_campaign={adgroupid}&utm_term={campaignid}&utm_content={creative}-{targetid}"

If the keyword is a broad match, there is no problem, and the results look as in the attachment "targetid." However, if the keyword is exact or phrase match, there are no results for {targetid} parameter, as shown in the attachment 'no targetid.'

Please help me with this issue. I'm unsure about what to do.

[Arek Gaładyk]

Could I please get a response?

[Google Ads API Forum Advisor]

Hi,

Thank you for reaching out to the Google Ads API support team.

Could you please confirm whether you are using Google Ads API? If yes, please provide us with the complete API logs (request and response with request-id and request header) generated at your end.

If you are using a client library and haven't enabled the logging yet, I would request you to enable logging for the specific client library that you are using. You can refer to the guides Java, .Net, PHP, Python, Ruby or Perl to enable logging at your end. For REST interface requests, you can enable logging via the curl command by using the -i flag.

 

This message is in relation to case "ref:!00D1U01174p.!5004Q02qUUYV:ref"

Thanks,
 

Google Ads API Team

 

[Google Ads API Forum Advisor]

Hi,

Thank you for reaching out to the Google Ads API support team. Please ignore my previous response.

Could you please confirm whether you are using Google Ads API? If yes, please provide us with the complete API logs (request and response with request-id and request header) generated at your end.

If you are using a client library and haven't enabled the logging yet, I would request you to enable logging for the specific client library that you are using. You can refer to the guides Java, .Net, PHP, Python, Ruby or Perl to enable logging at your end. For REST interface requests, you can enable logging via the curl command by using the -i flag.

You can send the details via Reply privately to the author option, or direct private reply to this email.