These values are unlikely to change for a specific API version release, but across releases it is very likely that they will change. Even non enum fields have caused me this type of headache in the past. Generally it is better to design your report processing so it would handle any new values gracefully(default enum value to unknown when you cannot encode something to a known value, default un-parseable numeric values to an error value like -1 and always print out a conspicuous warning in your logs) since in reality strange things happen all the time elsewhere in the Googleverse which cause the documentation to no longer reflect what shows up in a report.
The last time I remember this happening was in 201101 when "Auto" and "Auto: xx.xx" started appearing in an otherwise purely numeric cpc bid column of reports for budget optimized campaigns. This was a change that was undocumented and I assume occurred upstream of the API. Needless to say, there was special processing required to get these values into a double field in mysql. -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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
