Skip to content
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

Passing rendering params #741

Open
eysegal opened this issue Jul 31, 2023 · 11 comments
Open

Passing rendering params #741

eysegal opened this issue Jul 31, 2023 · 11 comments

Comments

@eysegal
Copy link

eysegal commented Jul 31, 2023

In native advertising, there is high importance for ads to appear as the same look and feel of the site which they are displayed.
Since the render url is registered on the advertiser side, how can we pass rendering signals when rendering the ad at the publisher?
Passing the publisher name or domain would probably be enough.

@shivanigithub
Copy link
Contributor

Thanks for raising this! Native advertising is indeed something that we are keeping in mind as we solve for more ads use cases while using fenced frames.

In the current state however, if you are using urn based iframes to render the ad, you can get the information from the embedding site via various means:

  • location.ancestorOrigins if the domain is sufficient information, or
  • using postMessage to communicate from the embedding site to the iframe or
  • using deprecatedReplaceInUrn : This also works in fenced frames.

@eysegal
Copy link
Author

eysegal commented Aug 1, 2023

Thanks. Is it safe to use deprecatedReplaceInUrn? Looking at the name it seems to going to be deprecated.

@shivanigithub
Copy link
Contributor

Thanks. Is it safe to use deprecatedReplaceInUrn? Looking at the name it seems to going to be deprecated.

We are working out the timelines for deprecatedReplaceInUrn and will be sharing that in the coming days.

@JensenPaul
Copy link
Collaborator

@eysegal, could you please update your GitHub profile with your name and company affiliation?

@eysegal
Copy link
Author

eysegal commented Aug 13, 2023

@JensenPaul sure, added

@shivanigithub
Copy link
Contributor

The timelines for deprecatedReplaceInUrn are updated here

@talbizit
Copy link

In addition to issue #741, we are concerned that the current solution does not provide a comprehensive resolution for native ads.

Presently, when rendering a native ad, it is encapsulated within the HTML and styles of the publisher, with many styles inherited from the hosting site, mostly without our awareness.

Given that the protected audience winning ad is rendered within a fenced frame/iframe, we would need to apply all styles from the containing HTML page to the fenced frame/iframe.

In essence, the question is whether it would be possible to propagate the external HTML page styles to the internal fenced frame/iframe?

@eysegal
Copy link
Author

eysegal commented Dec 19, 2023

The question above is important, @shivanigithub @JensenPaul do you know what's the answer?

@michaelkleber
Copy link
Collaborator

No, it is not possible to automatically have styling information from the publisher page flow through to any kind of cross-domain frame. This is not about Fenced Frames or Protected Audiences in particular; the thing you're asking for is inherently not possible today in iframes either.

@eysegal
Copy link
Author

eysegal commented Dec 19, 2023

Thank you for you response. Do you have an idea how we can support Native advertising where the fonts and other types of styling are inherited from the publisher?

@omriariav
Copy link
Contributor

What about using postMessage via SafeFrame and having the browser enforce CSS styles only?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants