how can MaxCpc and ProxyMaxCpc be the same data?  aren't the
semantically quite different?


On Dec 10, 3:46 pm, AdWords API Advisor <adwordsapiadvi...@google.com>
wrote:
> Hi,
>
> In these cases there are two field names for the same data, which is
> why they map to the same xmlAttributeName.  We'll work on cleaning up
> these duplicates, but for the mean time you can pick one and use it in
> your reports.
>
> Best,
> - Eric Koleda, AdWords API Team
>
> On Dec 10, 12:16 pm, J <j...@recessnetworks.net> wrote:
>
> > so i've defined a keyword report with pretty much all the fields,
> > according to the csv file obtainable via the documentation:
>
> >http://code.google.com/apis/adwords/docs/appendix/keywords_performanc...
>
> > so there's 50 named fields, but of those 50, 5 of them have duplicated
> > xml attribute specifications:
>
> > CriteriaDestinationUrl, DestinationUrl
> > MaxCpc, ProxyMaxCpc
> > ConversionValue, TotalConvValue
> > ValuePerConv, ValuePerConversion
> > ValuePerConvManyPerClick, ValuePerConversionManyPerClick
>
> > and as a result of fetching the defined report, i get back 45 fields
> > in the report file.  clearly, these are being uniq'd at the xml
> > attribute name.
>
> > while some look like synonyms (the conversion related fields), the
> > destination url and max cpc fields have some pretty different
> > semantics.  how are these fields disambiguated?
>
> > does this disambiguation hold for the other reports like the ad
> > report?
>
> > thanks.
>
>

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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

Reply via email to