Section visibility events

Mark the sections you want to measure in your published HTML. The standard tracker uses the browser’s IntersectionObserver; no second script is needed.

<section data-seean-scroll="pricing_seen"
         data-seean-scroll-threshold="0.5"
         data-seean-scroll-delay="1000">
  <!-- Your pricing content -->
</section>

This sends the custom event pricing_seen once after at least half of this section stays visible for one second. Find it under Events, the activity log and custom-event breakdowns. It counts toward normal event usage. You can use its name in a conversion goal or funnel.

Invalid attributes are ignored. A section taller than the viewport may never meet a high threshold. Choose the element and threshold accordingly. The event describes intersection with the viewport, not whether the person read the content or another element covered it.

Leaving the viewport or hiding the tab cancels a pending delay. Returning starts a fresh delay. Each element sends once per counted page visit; SPA navigation and restored pages reset it. Newly inserted sections are discovered automatically. No continuous scroll position, DOM text or screenshot is collected. Missing IntersectionObserver, privacy signals, opt-out or blocked collection means no event.

Verify

Open the published page with collection allowed, scroll the marked section into view, and hold it there for the configured delay. Check one event in the activity log. Scrolling away and back on the same page must not add another; navigating to another page and returning permits a new event.

See custom events and technical privacy for naming, properties and collection limits.

Something unclear? Contact support.