Tuesday, 27 September 2016

Re: ConversionTrackerId cannot be used in combination with ConvertedClicks in v201605?!

Thanks for your answer. I have a question about this sentence:

> The Conversions field in v201607 version of API reports is equivalent to ConvertedClicks.

Can you confirm, that in v201607 the following changes will take effect:
  • The v201603 field "Conversions" disappears, such information is no longer be available in v201607;
  • The v201603 field "ConvertedClicks" will be available in v201607, but its name will be "Conversions".
Please confirm again - all other documentation about Conversions and ConvertedClicks suggest otherwise, i.e. ConvertedClicks just disappears.

If my interpretation of your sentence is wrong, then what do you mean by "equivalent" in your sentence? When I get a v201607 report with "Conversions", is that the same as a v201603 report with "Conversions"? Or "ConvertedClicks"?


Please understand that we can't just stop reporting such information to our customers, and we need time to get replacement measuring ready. I told them they probably have until the end of the year or early next year, with the sunset of v201605. It would be bad news for everyone if ConvertedClicks -segmented by ConversionTrackers- stops in four weeks.
Note: if ConvertedClicks will be called Conversions in the future and just live on through that name, that would be great news for our customers.


On Tuesday, September 27, 2016 at 8:41:40 PM UTC+2, Shwetha Vastrad (AdWords API Team) wrote:
Hi,

The Conversions field in v201607 version of API reports is equivalent to ConvertedClicks. This field is compatible with the ConversionTrackedId field. You could continue using v201603 version of the API to preserve your historical converted clicks data and migrate to v201607 version of the API and start using fields based on Conversions instead. I apologize that this change wasn't documented in the v201605 migration guide. 

Please note that API version v201603 will be sunset on 25 October, 2016. Please be sure to migrate prior to the sunset to ensure your API access is unaffected.

Regards,
Shwetha, AdWords API Team.

--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
 
You received this message because you are subscribed to the Google
Groups "AdWords 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+unsubscribe@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 Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/c8de9b10-d156-4511-a43a-0351242b1a32%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment