Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gptPreAuction module doesn't respect MCM parameter in default mode #12355

Closed
muuki88 opened this issue Oct 22, 2024 · 0 comments · Fixed by #12356
Closed

gptPreAuction module doesn't respect MCM parameter in default mode #12355

muuki88 opened this issue Oct 22, 2024 · 0 comments · Fixed by #12356

Comments

@muuki88
Copy link
Collaborator

muuki88 commented Oct 22, 2024

Type of issue

bug

Description

Steps to reproduce

  1. Build a prebid distribution with the gptPreAuction module ( https://docs.prebid.org/dev-docs/modules/gpt-pre-auction.html )
  2. Configure it with mcmEnabled
gptPreAuction: {
   mcmEnabled: true
}
  1. Request an ad slot with an MCM flavoured ad unit path, e.g. /123,456/my-ad-unit . Where 456 is the network child id

Expected results

// find all GPT slots with this name
var gptSlots = window.googletag.pubads().getSlots().filter(slot => slot.getAdUnitPath() === adServerAdSlot);
if (gptSlots.length === 0) {
return; // should never happen
}

finds the correct ad slot and does not run in the "this should never happen" case

Actual results

The slot.getAdUnitPath() method returns /123,456/my-ad-unit , while adServerSlot is /123/my-ad-unit , which are not equal.

Setting mcmEnabled: false solves the issue.

Platform details

Prebid 9.8.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging a pull request may close this issue.

1 participant