Struggling with ad issues but can’t figure out what’s wrong?
Troubleshooting ad performance can be tough, especially when it involves understanding how Prebid.js interacts with your ad requests. Without the right tools, finding the problem can feel like searching for a needle in a haystack.
That’s where Requestly comes in!
Requestly is a browser extension that lets you modify, block, or redirect network requests instantly. With Requestly, you can easily enable Prebid.js debugging logs for your ads.
Solution 1: DIY with Requestly’s Modify Query Param Rule
Here’s how you can set up your own rule in Requestly:
Create a Modify Query Param
Rule:
- Install Requestly browser extension.
- Visit the Requestly dashboard.
- Click on
New Rule
and selectQuery Param
. - Enter your URL, set
pbjs_debug
as the parameter name, andtrue
as the value. - Save the rule
Solution 2: Use a Pre-configured Shared List
For a faster setup, use our pre-configured Requestly shared list that’s ready to enable Prebid.js debugging for nytimes.com ads.
- Click on this shared list link.
2. Use the Shared List:
- Add the shared list to your Requestly account by opening the link.
- Then, click on Import to
My Rules
- Then, add your own website link.
This will automatically apply the
pbjs_debug=true
parameter to your URLs, activating debugging logs without any extra steps.
How the Rule Works
The Modify Query Param rule in Requestly lets you add, change, or remove query parameters from URLs. By adding pbjs_debug=true
to the URLs, you activate detailed Prebid.js logs, essential for developers and advertisers to understand how their ads are served and spot any problems.
Start Debugging Now!
Top comments (0)