Re: Exact behavior of ConversionTypeName in reports

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Dorian,

Thanks for pointing that out. I'm always relying on the documentation, and 
I haven't done the math on my own account to verify this, so I appreciate 
the additional data. At the very least, we'll make sure the documentation 
gets updated to be a bit more clear.

Thanks,
Nadine, AdWords API Team

On Wednesday, June 22, 2016 at 4:25:46 AM UTC-4, Dorian Kind wrote:
>
> Hi Nadine,
>
> as always, thanks a lot for your quick response! I understand your point 
> about the difference between "Cost" and "TotalCost", but I'm still 
> surprised about "CostPerConversion" being based on conversion value. I 
> checked by downloading campaign performance reports in a few accounts of 
> ours, and the Totals lines looked like this:
>
> Campaign ID,Cost,Conversions,Total conv. value,Cost / conv.
> ...
> Total,20491557,"13,230.44","13,230.44",15485689
>
> Campaign ID,Cost,Conversions,Total conv. value,Cost / conv.
> ...
> Total,15889310,767.0,"15,048,053.0",207133781
>
> Campaign ID,Cost,Conversions,Total conv. value,Cost / conv.
> ...
> Total,2617570,"44,311.0","226,988.7",590727
>
> Campaign ID,Cost,Conversions,Total conv. value,Cost / conv.
> ...
> Total,2854659,"3,417.0","256,714.2",8354284
>
> The "CostPerConversion" field is always equal to "Cost" divided by 
> "Conversions". In the first example, it's actually also equal to "Cost" / 
> "ConversionValue", but that's because every conversion is worth 1 in this 
> account.
>
> Could it be that this is an inaccuracy in the documentation?
>
> Best regards,
> Dorian
>
>
>
> On Tuesday, June 21, 2016 at 11:27:49 PM UTC+2, Nadine Sundquist (AdWords 
> API Team) wrote:
>>
>> Hi Dorian,
>>
>> There was a recent rename of many of the conversion reporting columns in 
>> v201601, and that's why some of the definitions seem a bit confusing. Let 
>> me see if I can recall a bit of history to help clarify. Back in v201509, 
>> there was a TotalCost 
>> 
>>  field 
>> and there was also a Cost 
>> 
>>  
>> field. *CostPerConversion* was keying off of that field. The *TotalCost* 
>> field was removed because Adwords no longer charges for manual calls to 
>> Google forwarding numbers, and it was decided that this field no longer 
>> needed to be exposed. I'll go check for you to find out if there's a 
>> replacement for that field or a way to calculate the CostPerConversion some 
>> other way.
>>
>> I'll look into the other information you sent me on another thread. 
>> Thanks for sending that over!
>>
>> Regards,
>> Nadine, AdWords API Team
>>
>> On Tuesday, June 21, 2016 at 12:34:11 PM UTC-4, Dorian Kind wrote:
>>>
>>> Hi Nadine,
>>>
>>> thanks for your quick reply. I'm afraid to say I've lost you completely. 
>>> CostPerConversion is based on conversion value? Isn't that a very 
>>> unfortunate name then? Especially seeing as the Adwords web UI apparently 
>>> uses a different definition:
>>>
>>>
>>> 
>>>
>>>
>>> Here, Cost / conv. (which is the display name of the "CostPerConversion" 
>>> field in reports) is exactly equal to Cost (which is the display name of 
>>> the "Cost" field) divided by Conversions (display name of the "Conversions" 
>>> field). Total conv. value (display name of the "ConversionValue" field) is 
>>> not being used for this calculation at all...
>>>
>>>
>>> About the zero conversions rows, I'll send you some customer IDs and 
>>> report definitions in a private reply.
>>>
>>>
>>> Best regards,
>>>
>>> Dorian
>>>
>>>
>>>
>>> On Tuesday, June 21, 2016 at 6:15:43 PM UTC+2, Nadine Sundquist (AdWords 
>>> API Team) wrote:

 Hi Dorian,

 The reason it doesn't depend on *Cost* is because *CostPerConversion* 
 is the *total cost *divided by the *ConversionValue*. The total cost 
 is the total aggregated cost, which includes total click cost and any 
 other 
 costs, including phone cost. The *Cost* field does not include all the 
 additional expenses. That's why just dividing the *Cost* by 
 *ConversionValue* will not get you the *CostPerConversion*. 

 As for getting back 0 conversions in a row when specifying 
 *ConversionTypeName*, could you please click *Reply privately to 
 author* in the forum and send me the customer ID where you're seeing 
 this?

 Thanks,
 Nadine, AdWords API Team

 On Tuesday, June 21, 2016 at 5:10:46 AM UTC-4, Dorian Kind wrote:
>
> Hi Nadine,
>
> thanks for your feedback. I have a hard time understanding how 
> "CostPerConversion" isn't dependant on "Cost". If I have the number of 
> conversions and the cost per conversion, can't I 

Re: Exact behavior of ConversionTypeName in reports

[Dorian Kind]

Hi Nadine,

as always, thanks a lot for your quick response! I understand your point 
about the difference between "Cost" and "TotalCost", but I'm still 
surprised about "CostPerConversion" being based on conversion value. I 
checked by downloading campaign performance reports in a few accounts of 
ours, and the Totals lines looked like this:

Campaign ID,Cost,Conversions,Total conv. value,Cost / conv.
...
Total,20491557,"13,230.44","13,230.44",15485689

Campaign ID,Cost,Conversions,Total conv. value,Cost / conv.
...
Total,15889310,767.0,"15,048,053.0",207133781

Campaign ID,Cost,Conversions,Total conv. value,Cost / conv.
...
Total,2617570,"44,311.0","226,988.7",590727

Campaign ID,Cost,Conversions,Total conv. value,Cost / conv.
...
Total,2854659,"3,417.0","256,714.2",8354284

The "CostPerConversion" field is always equal to "Cost" divided by 
"Conversions". In the first example, it's actually also equal to "Cost" / 
"ConversionValue", 
but that's because every conversion is worth 1 in this account.

Could it be that this is an inaccuracy in the documentation?

Best regards,
Dorian



On Tuesday, June 21, 2016 at 11:27:49 PM UTC+2, Nadine Sundquist (AdWords 
API Team) wrote:
>
> Hi Dorian,
>
> There was a recent rename of many of the conversion reporting columns in 
> v201601, and that's why some of the definitions seem a bit confusing. Let 
> me see if I can recall a bit of history to help clarify. Back in v201509, 
> there was a TotalCost 
> 
>  field 
> and there was also a Cost 
> 
>  
> field. *CostPerConversion* was keying off of that field. The *TotalCost* 
> field was removed because Adwords no longer charges for manual calls to 
> Google forwarding numbers, and it was decided that this field no longer 
> needed to be exposed. I'll go check for you to find out if there's a 
> replacement for that field or a way to calculate the CostPerConversion some 
> other way.
>
> I'll look into the other information you sent me on another thread. Thanks 
> for sending that over!
>
> Regards,
> Nadine, AdWords API Team
>
> On Tuesday, June 21, 2016 at 12:34:11 PM UTC-4, Dorian Kind wrote:
>>
>> Hi Nadine,
>>
>> thanks for your quick reply. I'm afraid to say I've lost you completely. 
>> CostPerConversion is based on conversion value? Isn't that a very 
>> unfortunate name then? Especially seeing as the Adwords web UI apparently 
>> uses a different definition:
>>
>>
>> 
>>
>>
>> Here, Cost / conv. (which is the display name of the "CostPerConversion" 
>> field in reports) is exactly equal to Cost (which is the display name of 
>> the "Cost" field) divided by Conversions (display name of the "Conversions" 
>> field). Total conv. value (display name of the "ConversionValue" field) is 
>> not being used for this calculation at all...
>>
>>
>> About the zero conversions rows, I'll send you some customer IDs and 
>> report definitions in a private reply.
>>
>>
>> Best regards,
>>
>> Dorian
>>
>>
>>
>> On Tuesday, June 21, 2016 at 6:15:43 PM UTC+2, Nadine Sundquist (AdWords 
>> API Team) wrote:
>>>
>>> Hi Dorian,
>>>
>>> The reason it doesn't depend on *Cost* is because *CostPerConversion* 
>>> is the *total cost *divided by the *ConversionValue*. The total cost is 
>>> the total aggregated cost, which includes total click cost and any other 
>>> costs, including phone cost. The *Cost* field does not include all the 
>>> additional expenses. That's why just dividing the *Cost* by 
>>> *ConversionValue* will not get you the *CostPerConversion*. 
>>>
>>> As for getting back 0 conversions in a row when specifying 
>>> *ConversionTypeName*, could you please click *Reply privately to author* 
>>> in the forum and send me the customer ID where you're seeing this?
>>>
>>> Thanks,
>>> Nadine, AdWords API Team
>>>
>>> On Tuesday, June 21, 2016 at 5:10:46 AM UTC-4, Dorian Kind wrote:

 Hi Nadine,

 thanks for your feedback. I have a hard time understanding how 
 "CostPerConversion" isn't dependant on "Cost". If I have the number of 
 conversions and the cost per conversion, can't I just multiply the two to 
 get the total cost?

 Here's an example for the extra lines I've mentioned. I've chosen a 
 different client this time to keep the output small. Consider the 
 following 
 report definition:

 https://adwords.google.com/api/adwords/cm/v201603;>
 
 CampaignId
 ConversionTypeName
 Conversions
 CostPerConversion
 
 Test Report
 CAMPAIGN_PERFORMANCE_REPORT
 THIS_MONTH
 CSV
 

 This leads to this report being generated:

 

Re: Exact behavior of ConversionTypeName in reports

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hi Dorian,

There was a recent rename of many of the conversion reporting columns in 
v201601, and that's why some of the definitions seem a bit confusing. Let 
me see if I can recall a bit of history to help clarify. Back in v201509, 
there was a TotalCost 

 field 
and there was also a Cost 

 
field. *CostPerConversion* was keying off of that field. The *TotalCost* 
field was removed because Adwords no longer charges for manual calls to 
Google forwarding numbers, and it was decided that this field no longer 
needed to be exposed. I'll go check for you to find out if there's a 
replacement for that field or a way to calculate the CostPerConversion some 
other way.

I'll look into the other information you sent me on another thread. Thanks 
for sending that over!

Regards,
Nadine, AdWords API Team

On Tuesday, June 21, 2016 at 12:34:11 PM UTC-4, Dorian Kind wrote:
>
> Hi Nadine,
>
> thanks for your quick reply. I'm afraid to say I've lost you completely. 
> CostPerConversion is based on conversion value? Isn't that a very 
> unfortunate name then? Especially seeing as the Adwords web UI apparently 
> uses a different definition:
>
>
> 
>
>
> Here, Cost / conv. (which is the display name of the "CostPerConversion" 
> field in reports) is exactly equal to Cost (which is the display name of 
> the "Cost" field) divided by Conversions (display name of the "Conversions" 
> field). Total conv. value (display name of the "ConversionValue" field) is 
> not being used for this calculation at all...
>
>
> About the zero conversions rows, I'll send you some customer IDs and 
> report definitions in a private reply.
>
>
> Best regards,
>
> Dorian
>
>
>
> On Tuesday, June 21, 2016 at 6:15:43 PM UTC+2, Nadine Sundquist (AdWords 
> API Team) wrote:
>>
>> Hi Dorian,
>>
>> The reason it doesn't depend on *Cost* is because *CostPerConversion* is 
>> the *total cost *divided by the *ConversionValue*. The total cost is the 
>> total aggregated cost, which includes total click cost and any other costs, 
>> including phone cost. The *Cost* field does not include all the 
>> additional expenses. That's why just dividing the *Cost* by 
>> *ConversionValue* will not get you the *CostPerConversion*. 
>>
>> As for getting back 0 conversions in a row when specifying 
>> *ConversionTypeName*, could you please click *Reply privately to author* 
>> in the forum and send me the customer ID where you're seeing this?
>>
>> Thanks,
>> Nadine, AdWords API Team
>>
>> On Tuesday, June 21, 2016 at 5:10:46 AM UTC-4, Dorian Kind wrote:
>>>
>>> Hi Nadine,
>>>
>>> thanks for your feedback. I have a hard time understanding how 
>>> "CostPerConversion" isn't dependant on "Cost". If I have the number of 
>>> conversions and the cost per conversion, can't I just multiply the two to 
>>> get the total cost?
>>>
>>> Here's an example for the extra lines I've mentioned. I've chosen a 
>>> different client this time to keep the output small. Consider the following 
>>> report definition:
>>>
>>> https://adwords.google.com/api/adwords/cm/v201603;>
>>> 
>>> CampaignId
>>> ConversionTypeName
>>> Conversions
>>> CostPerConversion
>>> 
>>> Test Report
>>> CAMPAIGN_PERFORMANCE_REPORT
>>> THIS_MONTH
>>> CSV
>>> 
>>>
>>> This leads to this report being generated:
>>>
>>> Campaign ID,Conversion name,Conversions,Cost / conv.
>>> 227533244,,0.0,0
>>> 233123084,,4.0,78832500
>>> 227533244,2.0,675585000
>>> 234932444,,1.0,10133
>>> Total, --,7.0,445571429
>>>
>>> If I add a predicate like so:
>>>
>>> https://adwords.google.com/api/adwords/cm/v201603;>
>>> 
>>> CampaignId
>>> ConversionTypeName
>>> Conversions
>>> CostPerConversion
>>> 
>>> Conversions
>>> GREATER_THAN
>>> 0
>>> 
>>> 
>>> Test Report
>>> CAMPAIGN_PERFORMANCE_REPORT
>>> THIS_MONTH
>>> CSV
>>> 
>>>
>>> the output looks different:
>>>
>>> Campaign ID,Conversion name,Conversions,Cost / conv.
>>> 233123084,,4.0,78832500
>>> 227533244,,2.0,675585000
>>> 234932444,,1.0,10133
>>> Total, --,7.0,252547143
>>>
>>> This seems to contradict the documentation's statement "Prevents 
>>> zero-conversion rows from being returned." for the field 
>>> "ConversionTypeName".
>>>
>>> Best regards,
>>> Dorian
>>>
>>> On Monday, June 20, 2016 at 11:48:55 PM UTC+2, Nadine Sundquist (AdWords 
>>> API Team) wrote:

 Hello Dorian,

 So, it looks like you caught an issue in our documentation. We'll be 
 updating *ConversionCategoryName* to be listed as a segment. Thanks 
 for catching that and telling us about it!

 As for the answer to your second question, the *CostPerConversion* 
 does not directly depend on 

Re: Exact behavior of ConversionTypeName in reports

[Dorian Kind]

Hi Nadine,

thanks for your quick reply. I'm afraid to say I've lost you completely. 
CostPerConversion is based on conversion value? Isn't that a very 
unfortunate name then? Especially seeing as the Adwords web UI apparently 
uses a different definition:




Here, Cost / conv. (which is the display name of the "CostPerConversion" 
field in reports) is exactly equal to Cost (which is the display name of 
the "Cost" field) divided by Conversions (display name of the "Conversions" 
field). Total conv. value (display name of the "ConversionValue" field) is 
not being used for this calculation at all...


About the zero conversions rows, I'll send you some customer IDs and report 
definitions in a private reply.


Best regards,

Dorian



On Tuesday, June 21, 2016 at 6:15:43 PM UTC+2, Nadine Sundquist (AdWords 
API Team) wrote:
>
> Hi Dorian,
>
> The reason it doesn't depend on *Cost* is because *CostPerConversion* is 
> the *total cost *divided by the *ConversionValue*. The total cost is the 
> total aggregated cost, which includes total click cost and any other costs, 
> including phone cost. The *Cost* field does not include all the 
> additional expenses. That's why just dividing the *Cost* by 
> *ConversionValue* will not get you the *CostPerConversion*. 
>
> As for getting back 0 conversions in a row when specifying 
> *ConversionTypeName*, could you please click *Reply privately to author* 
> in the forum and send me the customer ID where you're seeing this?
>
> Thanks,
> Nadine, AdWords API Team
>
> On Tuesday, June 21, 2016 at 5:10:46 AM UTC-4, Dorian Kind wrote:
>>
>> Hi Nadine,
>>
>> thanks for your feedback. I have a hard time understanding how 
>> "CostPerConversion" isn't dependant on "Cost". If I have the number of 
>> conversions and the cost per conversion, can't I just multiply the two to 
>> get the total cost?
>>
>> Here's an example for the extra lines I've mentioned. I've chosen a 
>> different client this time to keep the output small. Consider the following 
>> report definition:
>>
>> https://adwords.google.com/api/adwords/cm/v201603;>
>> 
>> CampaignId
>> ConversionTypeName
>> Conversions
>> CostPerConversion
>> 
>> Test Report
>> CAMPAIGN_PERFORMANCE_REPORT
>> THIS_MONTH
>> CSV
>> 
>>
>> This leads to this report being generated:
>>
>> Campaign ID,Conversion name,Conversions,Cost / conv.
>> 227533244,,0.0,0
>> 233123084,,4.0,78832500
>> 227533244,2.0,675585000
>> 234932444,,1.0,10133
>> Total, --,7.0,445571429
>>
>> If I add a predicate like so:
>>
>> https://adwords.google.com/api/adwords/cm/v201603;>
>> 
>> CampaignId
>> ConversionTypeName
>> Conversions
>> CostPerConversion
>> 
>> Conversions
>> GREATER_THAN
>> 0
>> 
>> 
>> Test Report
>> CAMPAIGN_PERFORMANCE_REPORT
>> THIS_MONTH
>> CSV
>> 
>>
>> the output looks different:
>>
>> Campaign ID,Conversion name,Conversions,Cost / conv.
>> 233123084,,4.0,78832500
>> 227533244,,2.0,675585000
>> 234932444,,1.0,10133
>> Total, --,7.0,252547143
>>
>> This seems to contradict the documentation's statement "Prevents 
>> zero-conversion rows from being returned." for the field 
>> "ConversionTypeName".
>>
>> Best regards,
>> Dorian
>>
>> On Monday, June 20, 2016 at 11:48:55 PM UTC+2, Nadine Sundquist (AdWords 
>> API Team) wrote:
>>>
>>> Hello Dorian,
>>>
>>> So, it looks like you caught an issue in our documentation. We'll be 
>>> updating *ConversionCategoryName* to be listed as a segment. Thanks for 
>>> catching that and telling us about it!
>>>
>>> As for the answer to your second question, the *CostPerConversion* does 
>>> not directly depend on *Cost*. That's why the two fields are 
>>> compatible. As a follow-up to this, I have a question for you. You 
>>> mentioned that adding *CostPerConversion* results in more lines. Is the 
>>> same *CostPerConversion* returned for the same *ConversionTypeName*, or 
>>> are they different? I just want to verify that everything is working as 
>>> expected.
>>>
>>> Thanks,
>>> Nadine, AdWords API Team
>>>
>>> On Monday, June 20, 2016 at 5:35:19 PM UTC-4, Nadine Sundquist (AdWords 
>>> API Team) wrote:

 Hi Dorian,

 Thanks for checking in. Let me ping one of my teammates again because I 
 haven't gotten the answer back, yet. I've always found 
 *ConversionCategoryName* unique, and I just want to make sure I have 
 it right before giving you a definitive answer.

 Cheers,
 Nadine, AdWords API Team 

 On Monday, June 20, 2016 at 11:10:47 AM UTC-4, Dorian Kind wrote:
>
> Hi Nadine,
>
> any news on this subject? I just noticed that "ConversionCategoryName" 
> actually is defined as having behavior "Segment", so it seems that 
> "ConversionCategoryName" should be a segment, too.
>
> I would also be very interested in any feedback to the second part of 

Re: Exact behavior of ConversionTypeName in reports

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hi Dorian,

The reason it doesn't depend on *Cost* is because *CostPerConversion* is 
the *total cost *divided by the *ConversionValue*. The total cost is the 
total aggregated cost, which includes total click cost and any other costs, 
including phone cost. The *Cost* field does not include all the additional 
expenses. That's why just dividing the *Cost* by *ConversionValue* will not 
get you the *CostPerConversion*. 

As for getting back 0 conversions in a row when specifying 
*ConversionTypeName*, could you please click *Reply privately to author* in 
the forum and send me the customer ID where you're seeing this?

Thanks,
Nadine, AdWords API Team

On Tuesday, June 21, 2016 at 5:10:46 AM UTC-4, Dorian Kind wrote:
>
> Hi Nadine,
>
> thanks for your feedback. I have a hard time understanding how 
> "CostPerConversion" isn't dependant on "Cost". If I have the number of 
> conversions and the cost per conversion, can't I just multiply the two to 
> get the total cost?
>
> Here's an example for the extra lines I've mentioned. I've chosen a 
> different client this time to keep the output small. Consider the following 
> report definition:
>
> https://adwords.google.com/api/adwords/cm/v201603
> ">
> 
> CampaignId
> ConversionTypeName
> Conversions
> CostPerConversion
> 
> Test Report
> CAMPAIGN_PERFORMANCE_REPORT
> THIS_MONTH
> CSV
> 
>
> This leads to this report being generated:
>
> Campaign ID,Conversion name,Conversions,Cost / conv.
> 227533244,,0.0,0
> 233123084,,4.0,78832500
> 227533244,2.0,675585000
> 234932444,,1.0,10133
> Total, --,7.0,445571429
>
> If I add a predicate like so:
>
> https://adwords.google.com/api/adwords/cm/v201603
> ">
> 
> CampaignId
> ConversionTypeName
> Conversions
> CostPerConversion
> 
> Conversions
> GREATER_THAN
> 0
> 
> 
> Test Report
> CAMPAIGN_PERFORMANCE_REPORT
> THIS_MONTH
> CSV
> 
>
> the output looks different:
>
> Campaign ID,Conversion name,Conversions,Cost / conv.
> 233123084,,4.0,78832500
> 227533244,,2.0,675585000
> 234932444,,1.0,10133
> Total, --,7.0,252547143
>
> This seems to contradict the documentation's statement "Prevents 
> zero-conversion rows from being returned." for the field 
> "ConversionTypeName".
>
> Best regards,
> Dorian
>
> On Monday, June 20, 2016 at 11:48:55 PM UTC+2, Nadine Sundquist (AdWords 
> API Team) wrote:
>>
>> Hello Dorian,
>>
>> So, it looks like you caught an issue in our documentation. We'll be 
>> updating *ConversionCategoryName* to be listed as a segment. Thanks for 
>> catching that and telling us about it!
>>
>> As for the answer to your second question, the *CostPerConversion* does 
>> not directly depend on *Cost*. That's why the two fields are compatible. 
>> As a follow-up to this, I have a question for you. You mentioned that 
>> adding *CostPerConversion* results in more lines. Is the same 
>> *CostPerConversion* returned for the same *ConversionTypeName*, or are 
>> they different? I just want to verify that everything is working as 
>> expected.
>>
>> Thanks,
>> Nadine, AdWords API Team
>>
>> On Monday, June 20, 2016 at 5:35:19 PM UTC-4, Nadine Sundquist (AdWords 
>> API Team) wrote:
>>>
>>> Hi Dorian,
>>>
>>> Thanks for checking in. Let me ping one of my teammates again because I 
>>> haven't gotten the answer back, yet. I've always found 
>>> *ConversionCategoryName* unique, and I just want to make sure I have it 
>>> right before giving you a definitive answer.
>>>
>>> Cheers,
>>> Nadine, AdWords API Team 
>>>
>>> On Monday, June 20, 2016 at 11:10:47 AM UTC-4, Dorian Kind wrote:

 Hi Nadine,

 any news on this subject? I just noticed that "ConversionCategoryName" 
 actually is defined as having behavior "Segment", so it seems that 
 "ConversionCategoryName" should be a segment, too.

 I would also be very interested in any feedback to the second part of 
 my question, i.e. why "CostPerConversion" is compatible with 
 "ConversionTypeName" while "Cost" is not. I have a feeling that all 
 click-related metrics (impression-related, actually) should be 
 incompatible 
 with "ConversionTypeName" (and "ConversionCategoryName" for that matter) 
 as 
 a single click can lead to multiple conversions of different 
 categories/types. But I could be wrong.

 Thanks and best regards,
 Dorian

 On Friday, June 10, 2016 at 10:56:59 PM UTC+2, Nadine Sundquist 
 (AdWords API Team) wrote:
>
> Hi Dorian,
>
> I've taken a look at this, and I thought for some reason it was a 
> segmenting field as well at some point. Perhaps, the documentation is out 
> of date or something has changed. Sometimes, we do have implicit 
> segmentation that happens, but I'm not sure if that is what is happening 
> here. Let me check with a couple of teammates here, and I'll get back to 
> you.
>
> Best,
> Nadine, AdWords API Team 
>
> On Friday, June 10, 2016 at 4:08:11 AM UTC-4, Dorian Kind wrote:

Re: Exact behavior of ConversionTypeName in reports

[Dorian Kind]

Hi Nadine,

thanks for your feedback. I have a hard time understanding how 
"CostPerConversion" isn't dependant on "Cost". If I have the number of 
conversions and the cost per conversion, can't I just multiply the two to 
get the total cost?

Here's an example for the extra lines I've mentioned. I've chosen a 
different client this time to keep the output small. Consider the following 
report definition:

https://adwords.google.com/api/adwords/cm/v201603;>

CampaignId
ConversionTypeName
Conversions
CostPerConversion

Test Report
CAMPAIGN_PERFORMANCE_REPORT
THIS_MONTH
CSV


This leads to this report being generated:

Campaign ID,Conversion name,Conversions,Cost / conv.
227533244,,0.0,0
233123084,,4.0,78832500
227533244,2.0,675585000
234932444,,1.0,10133
Total, --,7.0,445571429

If I add a predicate like so:

https://adwords.google.com/api/adwords/cm/v201603;>

CampaignId
ConversionTypeName
Conversions
CostPerConversion

Conversions
GREATER_THAN
0


Test Report
CAMPAIGN_PERFORMANCE_REPORT
THIS_MONTH
CSV


the output looks different:

Campaign ID,Conversion name,Conversions,Cost / conv.
233123084,,4.0,78832500
227533244,,2.0,675585000
234932444,,1.0,10133
Total, --,7.0,252547143

This seems to contradict the documentation's statement "Prevents 
zero-conversion rows from being returned." for the field 
"ConversionTypeName".

Best regards,
Dorian

On Monday, June 20, 2016 at 11:48:55 PM UTC+2, Nadine Sundquist (AdWords 
API Team) wrote:
>
> Hello Dorian,
>
> So, it looks like you caught an issue in our documentation. We'll be 
> updating *ConversionCategoryName* to be listed as a segment. Thanks for 
> catching that and telling us about it!
>
> As for the answer to your second question, the *CostPerConversion* does 
> not directly depend on *Cost*. That's why the two fields are compatible. 
> As a follow-up to this, I have a question for you. You mentioned that 
> adding *CostPerConversion* results in more lines. Is the same 
> *CostPerConversion* returned for the same *ConversionTypeName*, or are 
> they different? I just want to verify that everything is working as 
> expected.
>
> Thanks,
> Nadine, AdWords API Team
>
> On Monday, June 20, 2016 at 5:35:19 PM UTC-4, Nadine Sundquist (AdWords 
> API Team) wrote:
>>
>> Hi Dorian,
>>
>> Thanks for checking in. Let me ping one of my teammates again because I 
>> haven't gotten the answer back, yet. I've always found 
>> *ConversionCategoryName* unique, and I just want to make sure I have it 
>> right before giving you a definitive answer.
>>
>> Cheers,
>> Nadine, AdWords API Team 
>>
>> On Monday, June 20, 2016 at 11:10:47 AM UTC-4, Dorian Kind wrote:
>>>
>>> Hi Nadine,
>>>
>>> any news on this subject? I just noticed that "ConversionCategoryName" 
>>> actually is defined as having behavior "Segment", so it seems that 
>>> "ConversionCategoryName" should be a segment, too.
>>>
>>> I would also be very interested in any feedback to the second part of my 
>>> question, i.e. why "CostPerConversion" is compatible with 
>>> "ConversionTypeName" while "Cost" is not. I have a feeling that all 
>>> click-related metrics (impression-related, actually) should be incompatible 
>>> with "ConversionTypeName" (and "ConversionCategoryName" for that matter) as 
>>> a single click can lead to multiple conversions of different 
>>> categories/types. But I could be wrong.
>>>
>>> Thanks and best regards,
>>> Dorian
>>>
>>> On Friday, June 10, 2016 at 10:56:59 PM UTC+2, Nadine Sundquist (AdWords 
>>> API Team) wrote:

 Hi Dorian,

 I've taken a look at this, and I thought for some reason it was a 
 segmenting field as well at some point. Perhaps, the documentation is out 
 of date or something has changed. Sometimes, we do have implicit 
 segmentation that happens, but I'm not sure if that is what is happening 
 here. Let me check with a couple of teammates here, and I'll get back to 
 you.

 Best,
 Nadine, AdWords API Team 

 On Friday, June 10, 2016 at 4:08:11 AM UTC-4, Dorian Kind wrote:
>
> Hi Umesh,
>
> thanks for your reply. I'm really not sure whether ConversionTypeName 
> is an attribute. As an example, for a given account and the following 
> report definition:
>
> https://adwords.google.com/api/adwords/cm/v201603;>
>   
> CampaignId
> 
>   Conversions
>   GREATER_THAN
>   0
> 
> 
>   20150126
>   20150201
> 
>   
>   Test Report
>   CAMPAIGN_PERFORMANCE_REPORT
>   CUSTOM_DATE
>   CSV
> 
>
> the returned report contains 99 lines. If I add ConversionTypeName:
>
> https://adwords.google.com/api/adwords/cm/v201603;>
>   
> CampaignId
> ConversionTypeName
> 
>   Conversions
>   GREATER_THAN
>   0
> 
> 
>   20150126
>   20150201
> 
>   
>   Test Report
>   

Re: Exact behavior of ConversionTypeName in reports

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Dorian,

So, it looks like you caught an issue in our documentation. We'll be 
updating *ConversionCategoryName* to be listed as a segment. Thanks for 
catching that and telling us about it!

As for the answer to your second question, the *CostPerConversion* does not 
directly depend on *Cost*. That's why the two fields are compatible. As a 
follow-up to this, I have a question for you. You mentioned that adding 
*CostPerConversion* results in more lines. Is the same *CostPerConversion* 
returned for the same *ConversionTypeName*, or are they different? I just 
want to verify that everything is working as expected.

Thanks,
Nadine, AdWords API Team

On Monday, June 20, 2016 at 5:35:19 PM UTC-4, Nadine Sundquist (AdWords API 
Team) wrote:
>
> Hi Dorian,
>
> Thanks for checking in. Let me ping one of my teammates again because I 
> haven't gotten the answer back, yet. I've always found 
> *ConversionCategoryName* unique, and I just want to make sure I have it 
> right before giving you a definitive answer.
>
> Cheers,
> Nadine, AdWords API Team 
>
> On Monday, June 20, 2016 at 11:10:47 AM UTC-4, Dorian Kind wrote:
>>
>> Hi Nadine,
>>
>> any news on this subject? I just noticed that "ConversionCategoryName" 
>> actually is defined as having behavior "Segment", so it seems that 
>> "ConversionCategoryName" should be a segment, too.
>>
>> I would also be very interested in any feedback to the second part of my 
>> question, i.e. why "CostPerConversion" is compatible with 
>> "ConversionTypeName" while "Cost" is not. I have a feeling that all 
>> click-related metrics (impression-related, actually) should be incompatible 
>> with "ConversionTypeName" (and "ConversionCategoryName" for that matter) as 
>> a single click can lead to multiple conversions of different 
>> categories/types. But I could be wrong.
>>
>> Thanks and best regards,
>> Dorian
>>
>> On Friday, June 10, 2016 at 10:56:59 PM UTC+2, Nadine Sundquist (AdWords 
>> API Team) wrote:
>>>
>>> Hi Dorian,
>>>
>>> I've taken a look at this, and I thought for some reason it was a 
>>> segmenting field as well at some point. Perhaps, the documentation is out 
>>> of date or something has changed. Sometimes, we do have implicit 
>>> segmentation that happens, but I'm not sure if that is what is happening 
>>> here. Let me check with a couple of teammates here, and I'll get back to 
>>> you.
>>>
>>> Best,
>>> Nadine, AdWords API Team 
>>>
>>> On Friday, June 10, 2016 at 4:08:11 AM UTC-4, Dorian Kind wrote:

 Hi Umesh,

 thanks for your reply. I'm really not sure whether ConversionTypeName 
 is an attribute. As an example, for a given account and the following 
 report definition:

 https://adwords.google.com/api/adwords/cm/v201603;>
   
 CampaignId
 
   Conversions
   GREATER_THAN
   0
 
 
   20150126
   20150201
 
   
   Test Report
   CAMPAIGN_PERFORMANCE_REPORT
   CUSTOM_DATE
   CSV
 

 the returned report contains 99 lines. If I add ConversionTypeName:

 https://adwords.google.com/api/adwords/cm/v201603;>
   
 CampaignId
 ConversionTypeName
 
   Conversions
   GREATER_THAN
   0
 
 
   20150126
   20150201
 
   
   Test Report
   CAMPAIGN_PERFORMANCE_REPORT
   CUSTOM_DATE
   CSV
 

 I get back 110 lines. The additional lines are from campaigns that had 
 conversions of multiple types during the reporting period. This seems 
 consistent with the hypothesis that ConversionTypeName is a segmenting 
 field.

 About the zero-conversion lines, I realized that these only show up if 
 you add certain other fields. If you take the last example, remove the 
 predicate and add 'CostPerConversion':

 https://adwords.google.com/api/adwords/cm/v201603;>
   
 CampaignId
 ConversionTypeName
 CostPerConversion
 
   20150126
   20150201
 
   
   Test Report
   CAMPAIGN_PERFORMANCE_REPORT
   CUSTOM_DATE
   CSV
 

 Now 226 lines are returned. The additional lines are all for conversion 
 type "Other" and have zero conversions.
 It's a bit strange that this field is compatible with the 
 "ConversionTypeName" field anyway, because the "Cost" field (which seems 
 to 
 be required to be able to calculate cost per conversion) is *not* 
 compatible 
 with "ConversionTypeName".

 To summarize:
 1. Would you agree that "ConversionTypeName" is a segmenting field? (If 
 so, the documentation should be updated.)
 2. Why is "CostPerConversion" compatible with "ConversionTypeName" when 
 "Cost" is not? And why does adding the "CostPerConversion" field result in 
 the returned report having more lines (namely the "Other" ones)?

Re: Exact behavior of ConversionTypeName in reports

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hi Dorian,

Thanks for checking in. Let me ping one of my teammates again because I 
haven't gotten the answer back, yet. I've always found 
*ConversionCategoryName* unique, and I just want to make sure I have it 
right before giving you a definitive answer.

Cheers,
Nadine, AdWords API Team 

On Monday, June 20, 2016 at 11:10:47 AM UTC-4, Dorian Kind wrote:
>
> Hi Nadine,
>
> any news on this subject? I just noticed that "ConversionCategoryName" 
> actually is defined as having behavior "Segment", so it seems that 
> "ConversionCategoryName" should be a segment, too.
>
> I would also be very interested in any feedback to the second part of my 
> question, i.e. why "CostPerConversion" is compatible with 
> "ConversionTypeName" while "Cost" is not. I have a feeling that all 
> click-related metrics (impression-related, actually) should be incompatible 
> with "ConversionTypeName" (and "ConversionCategoryName" for that matter) as 
> a single click can lead to multiple conversions of different 
> categories/types. But I could be wrong.
>
> Thanks and best regards,
> Dorian
>
> On Friday, June 10, 2016 at 10:56:59 PM UTC+2, Nadine Sundquist (AdWords 
> API Team) wrote:
>>
>> Hi Dorian,
>>
>> I've taken a look at this, and I thought for some reason it was a 
>> segmenting field as well at some point. Perhaps, the documentation is out 
>> of date or something has changed. Sometimes, we do have implicit 
>> segmentation that happens, but I'm not sure if that is what is happening 
>> here. Let me check with a couple of teammates here, and I'll get back to 
>> you.
>>
>> Best,
>> Nadine, AdWords API Team 
>>
>> On Friday, June 10, 2016 at 4:08:11 AM UTC-4, Dorian Kind wrote:
>>>
>>> Hi Umesh,
>>>
>>> thanks for your reply. I'm really not sure whether ConversionTypeName is 
>>> an attribute. As an example, for a given account and the following 
>>> report definition:
>>>
>>> https://adwords.google.com/api/adwords/cm/v201603;>
>>>   
>>> CampaignId
>>> 
>>>   Conversions
>>>   GREATER_THAN
>>>   0
>>> 
>>> 
>>>   20150126
>>>   20150201
>>> 
>>>   
>>>   Test Report
>>>   CAMPAIGN_PERFORMANCE_REPORT
>>>   CUSTOM_DATE
>>>   CSV
>>> 
>>>
>>> the returned report contains 99 lines. If I add ConversionTypeName:
>>>
>>> https://adwords.google.com/api/adwords/cm/v201603;>
>>>   
>>> CampaignId
>>> ConversionTypeName
>>> 
>>>   Conversions
>>>   GREATER_THAN
>>>   0
>>> 
>>> 
>>>   20150126
>>>   20150201
>>> 
>>>   
>>>   Test Report
>>>   CAMPAIGN_PERFORMANCE_REPORT
>>>   CUSTOM_DATE
>>>   CSV
>>> 
>>>
>>> I get back 110 lines. The additional lines are from campaigns that had 
>>> conversions of multiple types during the reporting period. This seems 
>>> consistent with the hypothesis that ConversionTypeName is a segmenting 
>>> field.
>>>
>>> About the zero-conversion lines, I realized that these only show up if 
>>> you add certain other fields. If you take the last example, remove the 
>>> predicate and add 'CostPerConversion':
>>>
>>> https://adwords.google.com/api/adwords/cm/v201603;>
>>>   
>>> CampaignId
>>> ConversionTypeName
>>> CostPerConversion
>>> 
>>>   20150126
>>>   20150201
>>> 
>>>   
>>>   Test Report
>>>   CAMPAIGN_PERFORMANCE_REPORT
>>>   CUSTOM_DATE
>>>   CSV
>>> 
>>>
>>> Now 226 lines are returned. The additional lines are all for conversion 
>>> type "Other" and have zero conversions.
>>> It's a bit strange that this field is compatible with the 
>>> "ConversionTypeName" field anyway, because the "Cost" field (which seems to 
>>> be required to be able to calculate cost per conversion) is *not* 
>>> compatible 
>>> with "ConversionTypeName".
>>>
>>> To summarize:
>>> 1. Would you agree that "ConversionTypeName" is a segmenting field? (If 
>>> so, the documentation should be updated.)
>>> 2. Why is "CostPerConversion" compatible with "ConversionTypeName" when 
>>> "Cost" is not? And why does adding the "CostPerConversion" field result in 
>>> the returned report having more lines (namely the "Other" ones)?
>>>
>>> Thanks and cheers,
>>> Dorian
>>>
>>> On Thursday, June 9, 2016 at 7:12:05 PM UTC+2, Umesh Dengale wrote:

 Hi Dorian,

 The ConversionTypeName 
 
  field prevents 
 zero-conversions rows from being returned as you mentioned above. The 
 ConversionTypeName is field of type *attribute* and not a *segment* type. 
 It may happen that you might be using some other segment field in the 
 report selector. If you getting records for ConversionCategoryName 
 
  (Other) 
 for zero conversions then provide me *privately* the report query and 
 clientCustomerId. Just click *Reply privately to author* in the forum 

Re: Exact behavior of ConversionTypeName in reports

[Dorian Kind]

Hi Nadine,

any news on this subject? I just noticed that "ConversionCategoryName" 
actually is defined as having behavior "Segment", so it seems that 
"ConversionCategoryName" should be a segment, too.

I would also be very interested in any feedback to the second part of my 
question, i.e. why "CostPerConversion" is compatible with 
"ConversionTypeName" while "Cost" is not. I have a feeling that all 
click-related metrics (impression-related, actually) should be incompatible 
with "ConversionTypeName" (and "ConversionCategoryName" for that matter) as 
a single click can lead to multiple conversions of different 
categories/types. But I could be wrong.

Thanks and best regards,
Dorian

On Friday, June 10, 2016 at 10:56:59 PM UTC+2, Nadine Sundquist (AdWords 
API Team) wrote:
>
> Hi Dorian,
>
> I've taken a look at this, and I thought for some reason it was a 
> segmenting field as well at some point. Perhaps, the documentation is out 
> of date or something has changed. Sometimes, we do have implicit 
> segmentation that happens, but I'm not sure if that is what is happening 
> here. Let me check with a couple of teammates here, and I'll get back to 
> you.
>
> Best,
> Nadine, AdWords API Team 
>
> On Friday, June 10, 2016 at 4:08:11 AM UTC-4, Dorian Kind wrote:
>>
>> Hi Umesh,
>>
>> thanks for your reply. I'm really not sure whether ConversionTypeName is 
>> an attribute. As an example, for a given account and the following 
>> report definition:
>>
>> https://adwords.google.com/api/adwords/cm/v201603;>
>>   
>> CampaignId
>> 
>>   Conversions
>>   GREATER_THAN
>>   0
>> 
>> 
>>   20150126
>>   20150201
>> 
>>   
>>   Test Report
>>   CAMPAIGN_PERFORMANCE_REPORT
>>   CUSTOM_DATE
>>   CSV
>> 
>>
>> the returned report contains 99 lines. If I add ConversionTypeName:
>>
>> https://adwords.google.com/api/adwords/cm/v201603;>
>>   
>> CampaignId
>> ConversionTypeName
>> 
>>   Conversions
>>   GREATER_THAN
>>   0
>> 
>> 
>>   20150126
>>   20150201
>> 
>>   
>>   Test Report
>>   CAMPAIGN_PERFORMANCE_REPORT
>>   CUSTOM_DATE
>>   CSV
>> 
>>
>> I get back 110 lines. The additional lines are from campaigns that had 
>> conversions of multiple types during the reporting period. This seems 
>> consistent with the hypothesis that ConversionTypeName is a segmenting 
>> field.
>>
>> About the zero-conversion lines, I realized that these only show up if 
>> you add certain other fields. If you take the last example, remove the 
>> predicate and add 'CostPerConversion':
>>
>> https://adwords.google.com/api/adwords/cm/v201603;>
>>   
>> CampaignId
>> ConversionTypeName
>> CostPerConversion
>> 
>>   20150126
>>   20150201
>> 
>>   
>>   Test Report
>>   CAMPAIGN_PERFORMANCE_REPORT
>>   CUSTOM_DATE
>>   CSV
>> 
>>
>> Now 226 lines are returned. The additional lines are all for conversion 
>> type "Other" and have zero conversions.
>> It's a bit strange that this field is compatible with the 
>> "ConversionTypeName" field anyway, because the "Cost" field (which seems to 
>> be required to be able to calculate cost per conversion) is *not* compatible 
>> with "ConversionTypeName".
>>
>> To summarize:
>> 1. Would you agree that "ConversionTypeName" is a segmenting field? (If 
>> so, the documentation should be updated.)
>> 2. Why is "CostPerConversion" compatible with "ConversionTypeName" when 
>> "Cost" is not? And why does adding the "CostPerConversion" field result in 
>> the returned report having more lines (namely the "Other" ones)?
>>
>> Thanks and cheers,
>> Dorian
>>
>> On Thursday, June 9, 2016 at 7:12:05 PM UTC+2, Umesh Dengale wrote:
>>>
>>> Hi Dorian,
>>>
>>> The ConversionTypeName 
>>> 
>>>  field prevents 
>>> zero-conversions rows from being returned as you mentioned above. The 
>>> ConversionTypeName is field of type *attribute* and not a *segment* type. 
>>> It may happen that you might be using some other segment field in the 
>>> report selector. If you getting records for ConversionCategoryName 
>>> 
>>>  (Other) 
>>> for zero conversions then provide me *privately* the report query and 
>>> clientCustomerId. Just click *Reply privately to author* in the forum 
>>> when responding.
>>>
>>> Thanks,
>>> Umesh, 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 

Re: Exact behavior of ConversionTypeName in reports

[Dorian Kind]

Hi Umesh,

thanks for your reply. I'm really not sure whether ConversionTypeName is an 
attribute. As an example, for a given account and the following report 
definition:

https://adwords.google.com/api/adwords/cm/v201603;>
  
CampaignId

  Conversions
  GREATER_THAN
  0


  20150126
  20150201

  
  Test Report
  CAMPAIGN_PERFORMANCE_REPORT
  CUSTOM_DATE
  CSV


the returned report contains 99 lines. If I add ConversionTypeName:

https://adwords.google.com/api/adwords/cm/v201603;>
  
CampaignId
ConversionTypeName

  Conversions
  GREATER_THAN
  0


  20150126
  20150201

  
  Test Report
  CAMPAIGN_PERFORMANCE_REPORT
  CUSTOM_DATE
  CSV


I get back 110 lines. The additional lines are from campaigns that had 
conversions of multiple types during the reporting period. This seems 
consistent with the hypothesis that ConversionTypeName is a segmenting 
field.

About the zero-conversion lines, I realized that these only show up if you 
add certain other fields. If you take the last example, remove the 
predicate and add 'CostPerConversion':

https://adwords.google.com/api/adwords/cm/v201603;>
  
CampaignId
ConversionTypeName
CostPerConversion

  20150126
  20150201

  
  Test Report
  CAMPAIGN_PERFORMANCE_REPORT
  CUSTOM_DATE
  CSV


Now 226 lines are returned. The additional lines are all for conversion 
type "Other" and have zero conversions.
It's a bit strange that this field is compatible with the 
"ConversionTypeName" field anyway, because the "Cost" field (which seems to 
be required to be able to calculate cost per conversion) is *not* compatible 
with "ConversionTypeName".

To summarize:
1. Would you agree that "ConversionTypeName" is a segmenting field? (If so, 
the documentation should be updated.)
2. Why is "CostPerConversion" compatible with "ConversionTypeName" when 
"Cost" is not? And why does adding the "CostPerConversion" field result in 
the returned report having more lines (namely the "Other" ones)?

Thanks and cheers,
Dorian

On Thursday, June 9, 2016 at 7:12:05 PM UTC+2, Umesh Dengale wrote:
>
> Hi Dorian,
>
> The ConversionTypeName 
> 
>  field prevents 
> zero-conversions rows from being returned as you mentioned above. The 
> ConversionTypeName is field of type *attribute* and not a *segment* type. 
> It may happen that you might be using some other segment field in the 
> report selector. If you getting records for ConversionCategoryName 
> 
>  (Other) 
> for zero conversions then provide me *privately* the report query and 
> clientCustomerId. Just click *Reply privately to author* in the forum 
> when responding.
>
> Thanks,
> Umesh, 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+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 Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@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/816e4832-e22c-4e29-aa44-ea5250853c8a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Exact behavior of ConversionTypeName in reports

['Umesh Dengale' via AdWords API Forum]

Hi Dorian,

The ConversionTypeName 

 field prevents 
zero-conversions rows from being returned as you mentioned above. The 
ConversionTypeName is field of type *attribute* and not a *segment* type. 
It may happen that you might be using some other segment field in the 
report selector. If you getting records for ConversionCategoryName 

 (Other) 
for zero conversions then provide me *privately* the report query and 
clientCustomerId. Just click *Reply privately to author* in the forum when 
responding.

Thanks,
Umesh, 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+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 Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@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/7bb77489-2337-4c76-bb20-401cc885023b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.