Skip to content
Open Screeb

Cross-origin pages and iframes

Know which Screeb features stop working when your page is split across origins with iframes, and how to remove the boundary.

Screeb runs inside an invisible iframe that it adds to your page. In almost every setup this is transparent and every feature works. This page only matters when the page Screeb is loaded on is split across different origins with iframes.

An origin is the combination of protocol, domain and port: https://app.example.com and https://checkout.example.com:8443 are different origins. When your content lives in an iframe whose origin differs from the one Screeb is loaded on, the browser blocks any access between the two frames.

  • Showing and answering surveys and messages
  • Triggering on time on page, tracked events and page URL
  • Identity, user properties, groups and event tracking
  • AI copilots

These features need to read the host page (its DOM, scroll position, address or title), which the browser forbids across origins:

Feature Across origins
Trigger on scroll percentage Unavailable
Trigger on scroll to an element Unavailable
Trigger on the presence or visibility of a CSS element Unavailable
Trigger on a click on a CSS element Unavailable
Exit intent trigger Unavailable
Inactivity trigger Unavailable
Session replay Not recorded
Page URL and title captured with events Empty
Live preview of the survey editor on your site Unavailable
Exact screen size of the host page Best effort, from the device screen

Only your setup can remove the boundary between Screeb and the content it needs to see:

  • Install Screeb on the page that contains the content you target, not on a parent page that embeds it in an iframe from another origin.
  • If your app is made of nested iframes, serve the frame running Screeb and the content you target from the same origin.

If you are unsure whether your setup is affected, run the debug command described in Check your setup on that page, or contact support@screeb.app.