Re: Optional Path fields in Expanded Text Ads and CSV Reports

Hi Oliver, You mentioned the following earlier: We believe path1 and path2 used to be blank until early last week. The " > --" is something we started seeing only last week as our parsing code broke > for exactly this reason. Would you mind sharing the AdGroupId

Re: Optional Path fields in Expanded Text Ads and CSV Reports

Hi, Thanks for the additional details. I'm following up with the reporting team specifically on the change in how nulls are represented in reports and will get back to you as soon as I have more information. Best regards, Josh, AdWords API Team On Thursday, October 27, 2016 at 7:36:31 AM

Re: Optional Path fields in Expanded Text Ads and CSV Reports

I noticed this too - see this related thread where I ask for more documentation on report fields. A few thoughts: 1. We download XML, the null value is represented as "--" 2. I agree with Oliver, this null value was

Re: Optional Path fields in Expanded Text Ads and CSV Reports

Hi Josh, no, as I mentioned I don't think that's a very likely scenario, and we have already adapted our parsing/validation logic. I was just a bit surprised by the fact that there are two different representations of the "Not set" value for attributes, i.e. some like CreativeDestinationUrl

Re: Optional Path fields in Expanded Text Ads and CSV Reports

Hi Oliver, Dorian, Can either of you think of a valid reason why a user would *want* "--" as *path1* or *path2*? If not, then perhaps the solution here is to simply change the validation of those fields to prevent that value. Thanks, Josh, AdWords API Team On Tuesday, October 18, 2016 at

Re: Optional Path fields in Expanded Text Ads and CSV Reports

We believe path1 and path2 used to be blank until early last week. The " --" is something we started seeing only last week as our parsing code broke for exactly this reason. Oliver On Tuesday, October 18, 2016 at 10:41:45 AM UTC+1, Dorian Kind wrote: > > Hi Anash, > > thanks for your

Re: Optional Path fields in Expanded Text Ads and CSV Reports

Hi Anash, thanks for your response. Just as an addendum, there are already fields that are formatted as empty in CSV reports (meaning just two commas in a row) when they are not set—"CreativeDestinationUrl" is an example. So there seems to be a certain inconsistency. Best regards, Dorian On

Re: Optional Path fields in Expanded Text Ads and CSV Reports

Hi Dorian, Thanks for reporting, I'll ask the reporting team to take a look. Cheers, Anash P. Oommen, AdWords API Advisor. On Monday, October 17, 2016 at 12:51:38 PM UTC-4, Dorian Kind wrote: > > Hi, > > I just noticed that with ETAs, the path1 and path2 fields are optional—you > can create an

Optional Path fields in Expanded Text Ads and CSV Reports

Hi, I just noticed that with ETAs, the path1 and path2 fields are optional—you can create an ad without either of these two fields set. This is in contrast to the previously used text ads, where every field is required. This has an interesting effect, as the CSV reports show unset path fields