-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Inject a mock bid #12261
Comments
You can use |
@EskelCz it seems we should add an example forced bid to this page: https://docs.prebid.org/dev-docs/modules/debugging.html#replace-rules Are you looking for an example to change the bidder of an existing response? |
@patmmccann Banner example would be a good addition. But from my understanding the intercept system has two limitations:
I have worked around this using magnite demand simulator or other tools to mock network requests, but it's not a convenient. Prebid debugging code can be more easily shared with a third party for example. |
It works by intercepting bid requests and mocking the normal adapter request/response flow (but I realize now that the documentation is not clear on this). Stylized, the normal flow is:
When an So you should be able to use it to simulate a bid when the actual exchange won't bid. The limitation is that you need a bid request to start with (but you can always just add another entry in |
@dgirardi Ok thanks for the explanation. Not sure why it didn't work for me. I'll close this for now and maybe reopen once I come across it again and have some details to share. |
Type of issue
Question
Description
Is there a way to inject my own testing bid via the debugging module? I know about intercept, but that just changes the current bids.
In ad ops there are many issues downstream (in rendering) that often need fixing/testing before we start getting bids, and that leaves us stuck. It would save us a lot of time/work to have such capability.
I have found some discussion on the topic here, but can't find if it resulted in anything real: #4461
Thanks for consideration.
The text was updated successfully, but these errors were encountered: