-
Notifications
You must be signed in to change notification settings - Fork 25
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
Support for native advertising #69
Comments
Hi, thanks for bringing this up- we plan on discussing this at our next public call on Thurs 10/17 at 8 AM PST. See more details here. |
Thurs 10/17 is a Jewish holiday and the team here will be away. Can we discuss this in the 10/30 meeting? Thanks |
Got it! We will be discussing this in the 10/30 meeting |
Confirming we're going to review this on the 31st, right? Thank you |
Yup confirmed for 10/31. To see agenda + join info see here |
Hi all,
I oversee user data as the product manager at @taboola, leading our preparations for a cookieless world. Over the past year, we have actively collaborated with the Privacy Sandbox teams (Chrome and Android) to advocate for the full support of native advertising.
Native ads blend into the website's content, matching the platform's look, feel, and function. These ads appear part of the user’s natural browsing experience, making them less intrusive. We use our JS library, which publishers integrate into the page. We render mid-article widgets and the below article's endless feed (example). In Taboola, next to ads, we also recommend organic items of the publisher, aiming to boost engagement metrics. The blend between ads differs per impression according to our content recommendation decisions.
Taboola supports various campaigns, including different forms of retargeting. We provide our own JavaScript library (pixel) that advertisers can place on their landing pages to enable these features.
We have the highest respect for the work done so far, but we think it didn't consider native advertising, focusing only on display advertising needs.
We would like to highlight the following main gaps in regards to retargeting and audiences:
renderURL
to use publisher page look and feel styles (Passing rendering params turtledove#741).We will be happy to collaborate and engage to promote these needs.
Thanks!
The text was updated successfully, but these errors were encountered: