YouTube Video ID in Video Performance Report Does Not Match

[Mark Rogoyski]

The Video ID field of the Video Performance Report does not match the ID found form other sources for a specific video.

For example, in the Web URL, the video ID is found at the end of the URL: https://www.youtube.com/watch?v={VIDEO_ID}

For a certain video we are using and querying with the API, the Video ID queried using the Video Performance Report does not match. Specifically, when querying using the API, there is a leading space in the Video ID, but that space does not appear in other places where the Video ID appears, such as in the Web URL.

Due to client privacy concerns, I'd prefer to send the details to an AdWords representative in private. Please provide a reply to this thread to allow me to reply in private to provide the details to reproduce the issue for this specific case.

Thanks.

Mark

[Anthony Madrigal]

Hi Mark,

I'll be glad to take a look at what is going on here. You can send me the details privately via reply privately to author. Please provide the report definition, clientCustomerId and some video Ids you expect to see.

Thanks,

Anthony

AdWords API Team

[Josh Radcliff (AdWords API Team)]

Hi Mark,

I'm responding here just in case others encounter this issue. I'm following up with the reporting team and will get back to you as soon as I have more information.

In the meantime, I suggest trimming leading and trailing spaces from VideoId field values as a workaround.

Thanks,

Josh, AdWords API Team

[Josh Radcliff (AdWords API Team)]

Hi Mark,

I found a bit more background on this one. The reason reporting adds a leading space for that particular VideoId in CSV format is if a user imports the CSV into Excel and the value begins with a hyphen (-), Excel will interpret the field as a formula unless it has a leading space. To avoid this problem, the reporting service adds a leading space to any field value that would cause issues in Excel without the space.

Thanks,

Josh, AdWords API Team

[Mark Rogoyski]

Hi Josh,

Thank you for the explanation.

I could understand if this leading space was added to any CSV reports downloaded from the UI, but the API is meant for computers and automated systems to consume data, so it seems kind of unnecessary to implement workarounds for a human loading into Excel when this isn't the use case for the API.

Could this behavior be removed from the API?

Thanks.

Mark

[Thanet Knack Praneenararat (AdWords API Team)]

Hello Mark,

I would like to update that we're aware of the issue and discussing about the feasibility/timing of the change.

Could you please wait a bit more before we reach the conclusion?

We'll update this thread as soon as possible.

Cheers,

Thanet, AdWords API Team

[Josh Radcliff (AdWords API Team)]

Hi Mark,

We're still discussing whether to make this change. If we do change the behavior, it will most likely happen starting with a specific AdWords API version to avoid creating problems for anyone who is relying on the current behavior.

Thanks,

Josh, AdWords API Team

[Mark Rogoyski]

Hi Josh,

Thanks for the update.

Mark

[Nadine Sundquist (AdWords API Team)]

Hello Mark,

I have good news! With the release of v201607, there was a change made to reporting outlined under the section Quoting of values in comma-separated output where fields that begin with the special characters - (minus) or + (plus) will be double-quoted without a leading space in the CSV, CSVFOREXCEL, and TSV download formats. To get this new behavior, you would have to start using v201607. Versions v201605 and older still behave the same as it did previously as to not break people's current reports.

Cheers,

Nadine, AdWords API Team

[Mark Rogoyski]

Hi Nadine,

Thank you for the update. I can see in the release notes this change is there.

Thanks again.

Mark