gamAdServerVideo: Add GPP consent information to the DFP video url

[robin-crazygames]

Type of change

• Bugfix

• Feature

• New bidder adapter

• Updated bidder adapter

• Code style update (formatting, local variables)

• Refactoring (no functional changes, no api changes)

• Build related changes

• CI related changes

• Does this change affect user-facing APIs or examples documented on http://prebid.org?

• Other

Description of change

When using pbjs.adServers.dfp.buildVideoUrl, the url would contain GDPR related information in GDPR countries, but not the GPP related information in GPP countries.

I cannot find any links to the official Google Ad Manager docs on how to provide this information. However, when using the googletag script for banner ads, you see it using 'gpp_string' and 'gpp_sid' to pass the GPP related information.

Inspecting the obfuscated/minimized googletag script, you can also find that it is using:

a.pingData.gppString

and

a.pingData.applicableSections.join(',')

So I added those gpp_string and gpp_sid to the buildVideoUrl function, and to the bidViewability (because that one was mentioned in issue 9364 as well)

Other information

fixes #9364

[patmmccann]

Thanks for you submission! I contacted Google and they certainly do not have this feature documented at https://support.google.com/admanager/answer/10678356 yet although there may be unstable and unofficial support before a release. Does this feature solve some issue for you?

[robin-crazygames]

Solving an issue might be a big word. What we do for videos is first having a Prebid auction. And then we use the URL generated by Prebid to hold another auction on GAM.

I would assume that, for the auction on GAM, passing in the GPP consent string will result in better bids

[patmmccann]

We contacted Google, we're not sure adding this would improve monetization in the short term. We expect them to release official support soon and we can try and merge then so we don't subject publishers to a sudden behavior change when Google announces official support.

[jimee02]

Per https://support.google.com/admanager/answer/10678356?sjid=8899252983232341054-NC, gpp params are not supported, but I have seen them on there before. Adjacent to this we should add us_privacy to our targeting as well. I'll create a ticket on our side to add this

[jimee02]

@patmmccann ran an experiment on our side and it did not provide any revenue lift from what we can tell. I'd continue holding off on this PR

[coveralls]

Pull Request Test Coverage Report for Build 22874035328

Details

• 7 of 7 (100.0%) changed or added relevant lines in 2 files are covered.
• 46 unchanged lines in 2 files lost coverage.
• Overall coverage increased (+33.2%) to 96.327%

---

Files with Coverage Reduction	New Missed Lines	%
src/adloader.js	9	76.92%
src/utils.js	37	90.51%

Totals
Change from base Build #3:	33.2%
Covered Lines:	217517
Relevant Lines:	225811

---

💛 - Coveralls

[patmmccann]

@copilot resolve the merge conflicts in this pull request

[patmmccann]

https://developers.google.com/ad-manager/dynamic-ad-insertion/sdk/html5/ccpa and https://developers.google.com/ad-manager/dynamic-ad-insertion/sdk/roku/ccpa seem to officially document this parameter

I would say this is unblocked

[patmmccann]

@robin-crazygames it seems it is gpp instead of gpp_string?

[barecheck]

Barecheck - Code coverage report

Total: 96.58%

Your code coverage diff: 0.00% ▴

Uncovered files and lines

File	Lines
modules/gamAdServerVideo.js	254, 297, 307, 324, 358-359

[robin-crazygames]

At the moment, even when only GPP consent info is present, the gamAdServerVideo code derives a value for us_privacy based on the GPP info.

Since the gpp string is still not present on https://support.google.com/admanager/answer/10678356?hl=en#zippy=%2Cquickly-navigate-to-any-vast-parameter, I wonder whether we should pass both the gpp and derived us_privacy, or just stick to gpp only.

[patmmccann]

hopefully our friends at gam will weigh in :) I know the tachlab team is frustrated