Open ahmadlob opened 1 year ago
What is an example of the blocked url? Which browser blocked it?
we feel it more in Edge and Firefox
urls for example: https://trc.taboola.com/articlesmansion-hb/log/3/visible?route=AM%3AAM%3AV<i=new-test-inc-vis-2_ctrl
On Wed, Jun 21, 2023 at 2:42 PM Patrick McCann @.***> wrote:
What is an example of the blocked url? Which browser blocked it?
— Reply to this email directly, view it on GitHub https://github.com/prebid/Prebid.js/issues/10126#issuecomment-1600683301, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2BIRRBTILQYWBW6GGVMYNTXMLM3RANCNFSM6AAAAAAZOOXA2I . You are receiving this because you authored the thread.Message ID: @.***>
Is there any update or figures regarding this issue? @patmmccann
No one else has reproduced or reports this issue so far. It seems unique to Taboola.
@patmmccann I see, actually strict mode browsers distribution isn't that high. Currently we are checking if it is due to ad blockers maybe. We noticed some block prebid and some though prebid rendering iframe blocked still sent a request to our bidder service. If you have more information regarding this or any tips, will appreciate that
@ahmadlob I am not sure how to proceed on this - could you provide steps to reproduce? (for example, which browser should I use, how should I set it up, and what is the behavior I should see on the pages you gave?)
To enable Strict Mode in Firefox for desktop, you can: Mozilla Support, MakeUseOf, +1 more Click the shield icon to the left of the address bar Mozilla Support, MakeUseOf, +1 more Click "Protection Settings" Mozilla Support, MakeUseOf Under "Enhanced Tracking Protection", select "Strict"
@ahmadlob are you able to detect this mode on your requests somehow? How were you able to identify this gap?
One idea is if we can somehow detect it, we could put it in the request object or cancel all auctions as prebid ssps will not be able to pay.
@patmmccann to find a contact at mozilla
@patmmccann we noticed the gap as discrepancy between our "nurl" win count vs publishers ad server impressions. Lets distinguish between the two issues:
If you could detect it will be great
@ahmadlob to be clear, you want to detect an ad blocker, not strict mode, and append the flag to the request object?
@patmmccann exactly 100%
Type of issue
We are suffering from significant discrepancies with different publishers, conducted analysis and noticed it looks to be a result of a certain browsers tracking prevention/protection. When browser is in strict mode, taboola tracker is blocked.
This results in discrepancy between the publisher numbers ( counting ad server impressions where taboola win ) and our impressions and visible numbers (not rendered or fired so on our side not counted)
Are you familiar with this issue? (it should affect many bidders and not just taboola) Suggested solutions are appreciable