ConversionTrackerId xmlAttribute for CREATIVE_CONVERSION_REPORT

18 views
Skip to first unread message

Angel Lubenov

unread,
Jan 9, 2018, 9:28:23 AM1/9/18
to AdWords API Forum
Hi!, 
By using the report-definition-service endpoint, when I request information about the CREATIVE_CONVERSION_REPORT table, I got that the XMLAttribute for "ConversionTrackerId" does not match with the API's response for the report-download endpoint. 

Report Definition Service informs (extract): 

  1. <rval>
    1. <fieldName>ConversionTrackerId</fieldName>
    2. <displayFieldName>Free click type</displayFieldName>
    3. <xmlAttributeName>freeClickType</xmlAttributeName>
    4. <fieldType>Long</fieldType>
    5. <fieldBehavior>SEGMENT</fieldBehavior>
    6. <canSelect>true</canSelect>
    7. <canFilter>true</canFilter>
    8. <isEnumType>false</isEnumType>
    9. <isBeta>false</isBeta>
    10. <isZeroRowCompatible>false</isZeroRowCompatible>
    11. </rval>

But Report download endpoint returns (extract): 


  1. <row
     conversionTrackerId="10133" freeClicks="1" freeClickRate="0.00%" impressions="0"/>
  2. <row conversionTrackerId="47" freeClicks="42917" freeClickRate="0.00%" impressions="0"/>
  3. <row conversionTrackerId="10" freeClicks="41886663" freeClickRate="0.00%" impressions="0"/


The xml attribute for conversionTrackerId is "conversionTrackerId" and not "freeClickType". 

I checked with the API documentation (https://developers.google.com/adwords/api/docs/appendix/reports/creative-conversion-report) and the same is informed (also in the CSV available to download).

Since I am using the report definition service for dynamically retrieve information this issue causes inconsistent information. 



Sreelakshmi Sasidharan (AdWords API Team)

unread,
Jan 9, 2018, 1:33:25 PM1/9/18
to AdWords API Forum
Hi Angel,

Thanks for pointing this out. The API is currently returning the display name as "Conversion Tracker Id" instead of "Free click type" for ConversionTrackerId. I will inform the team about this discrepancy so that they can get it corrected.

Thanks,
Sreelakshmi, AdWords API Team
Reply all
Reply to author
Forward
0 new messages