We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
bug
gptPreAuction
mcmEnabled
gptPreAuction: { mcmEnabled: true }
/123,456/my-ad-unit
456
Prebid.js/modules/gptPreAuction.js
Lines 119 to 124 in 24306f3
finds the correct ad slot and does not run in the "this should never happen" case
The slot.getAdUnitPath() method returns /123,456/my-ad-unit , while adServerSlot is /123/my-ad-unit , which are not equal.
slot.getAdUnitPath()
adServerSlot
/123/my-ad-unit
Setting mcmEnabled: false solves the issue.
mcmEnabled: false
Prebid 9.8.0
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Type of issue
bug
Description
Steps to reproduce
gptPreAuction
module ( https://docs.prebid.org/dev-docs/modules/gpt-pre-auction.html )mcmEnabled
/123,456/my-ad-unit
. Where456
is the network child idExpected results
Prebid.js/modules/gptPreAuction.js
Lines 119 to 124 in 24306f3
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
, whileadServerSlot
is/123/my-ad-unit
, which are not equal.Setting
mcmEnabled: false
solves the issue.Platform details
Prebid 9.8.0
The text was updated successfully, but these errors were encountered: