Scroll-Triggered Popup with IntersectionObserver and React

Our company is engaged in the development, support and maintenance of sites of any complexity. From simple one-page sites to large-scale cluster systems built on micro services. Experience of developers is confirmed by certificates from vendors.

Development and maintenance of all types of websites:

Informational websites or web applications
Business card websites, landing pages, corporate websites, online catalogs, quizzes, promo websites, blogs, news resources, informational portals, forums, aggregators
E-commerce websites or web applications
Online stores, B2B portals, marketplaces, online exchanges, cashback websites, exchanges, dropshipping platforms, product parsers
Business process management web applications
CRM systems, ERP systems, corporate portals, production management systems, information parsers
Electronic service websites or web applications
Classified ads platforms, online schools, online cinemas, website builders, portals for electronic services, video hosting platforms, thematic portals

These are just some of the technical types of websites we work with, and each of them can have its own specific features and functionality, as well as be customized to meet the specific needs and goals of the client.

Showing 1 of 1All 2062 services
Scroll-Triggered Popup with IntersectionObserver and React
Simple
~1 day
Frequently Asked Questions

Our competencies:

Development stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1360
  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1251
  • image_websites_belfingroup_462_0.webp
    Website development for BELFINGROUP
    957
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1188
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    929
  • image_bitrix-bitrix-24-1c_fixper_448_0.webp
    Website development for FIXPER company
    948

Scroll-Triggered Popup with IntersectionObserver and React

We integrate scroll-triggered popups that appear only when the visitor is engaged: after reading 60% of an article or scrolling to a key benefits section. Standard popups on page load are annoying — the user hasn't seen the content yet, and they're interrupted. With our approach, conversion rates increase and bounce rates drop. According to a HubSpot study, this approach boosts subscription conversion by 2–3x. Our clients typically see conversion rise from 0.8% to 2.3%. The development cost starts at $500 and is determined after analysis based on project complexity, but the marketing budget savings from precise targeting often exceed 35% (average savings of $2,000 per campaign).

Why Use a Scroll-Triggered Popup?

Technically, the popup activates via the IntersectionObserver API — it doesn't block the main thread, unlike scroll event handlers. In practice, conversion improves from 0.8% to 2.3% – that's nearly 3x better than standard load popups. The user is already interested — the offer feels natural. Over 70% of subscribers come from scroll-triggered windows. A common mistake is showing the popup on every visit, leading to bans. Cooldown solves that.

How We Implement the Popup

We use IntersectionObserver with an invisible marker. We configure a scroll percentage or a specific element. We add a cooldown via localStorage to avoid showing the popup too often. Below is the full TypeScript code.

Implementation Example

// scroll-popup.ts
interface ScrollPopupConfig {
  triggerPercent?: number;
  triggerElement?: string;
  cooldownMs?: number;
  onTrigger: () => void;
}

export function initScrollPopup(config: ScrollPopupConfig) {
  const { triggerPercent, triggerElement, cooldownMs = 0, onTrigger } = config;
  let triggered = false;

  const STORAGE_KEY = 'scroll_popup_shown';

  function checkCooldown(): boolean {
    if (!cooldownMs) return true;
    const last = localStorage.getItem(STORAGE_KEY);
    if (last && Date.now() - Number(last) < cooldownMs) return false;
    return true;
  }

  function fire() {
    if (triggered || !checkCooldown()) return;
    triggered = true;
    if (cooldownMs) localStorage.setItem(STORAGE_KEY, String(Date.now()));
    onTrigger();
  }

  // Option 1: scroll percentage
  if (triggerPercent !== undefined) {
    const marker = document.createElement('div');
    marker.style.cssText = 'position:absolute;top:0;left:0;width:1px;height:1px;pointer-events:none;';
    document.body.style.position = 'relative';
    document.body.appendChild(marker);

    function updateMarker() {
      const docHeight = document.documentElement.scrollHeight;
      const viewportHeight = window.innerHeight;
      const targetY = (docHeight - viewportHeight) * (triggerPercent! / 100);
      marker.style.top = `${targetY}px`;
    }

    updateMarker();
    window.addEventListener('resize', updateMarker, { passive: true });

    const observer = new IntersectionObserver(
      ([entry]) => { if (entry.isIntersecting) fire(); },
      { threshold: 0 }
    );
    observer.observe(marker);

    return () => {
      observer.disconnect();
      marker.remove();
      window.removeEventListener('resize', updateMarker);
    };
  }

  // Option 2: specific DOM element
  if (triggerElement) {
    const el = document.querySelector(triggerElement);
    if (!el) {
      console.warn(`[scroll-popup] Element not found: ${triggerElement}`);
      return () => {};
    }

    const observer = new IntersectionObserver(
      ([entry]) => { if (entry.isIntersecting) fire(); },
      { threshold: 0.5 }
    );
    observer.observe(el);
    return () => observer.disconnect();
  }

  return () => {};
}

Using the Popup in React

// BlogPost.tsx
import { useEffect } from 'react';
import { initScrollPopup } from './scroll-popup';
import { NewsletterPopup } from './NewsletterPopup';
import { useState } from 'react';

export function BlogPost({ content }: { content: string }) {
  const [showPopup, setShowPopup] = useState(false);

  useEffect(() => {
    const cleanup = initScrollPopup({
      triggerPercent: 60,
      cooldownMs: 7 * 24 * 60 * 60 * 1000,
      onTrigger: () => setShowPopup(true),
    });
    return cleanup;
  }, []);

  return (
    <>
      <article dangerouslySetInnerHTML={{ __html: content }} />
      {showPopup && (
        <NewsletterPopup onClose={() => setShowPopup(false)} />
      )}
    </>
  );
}

The NewsletterPopup Component

// NewsletterPopup.tsx
import { useRef, useEffect, useState } from 'react';

export function NewsletterPopup({ onClose }: { onClose: () => void }) {
  const dialogRef = useRef<HTMLDialogElement>(null);
  const [email, setEmail] = useState('');
  const [status, setStatus] = useState<'idle' | 'loading' | 'done'>('idle');

  useEffect(() => {
    dialogRef.current?.showModal();
    return () => dialogRef.current?.close();
  }, []);

  async function subscribe() {
    if (!email || status !== 'idle') return;
    setStatus('loading');
    await fetch('/api/subscribe', {
      method: 'POST',
      headers: { 'Content-Type': 'application/json' },
      body: JSON.stringify({ email, source: 'scroll_popup' }),
    });
    setStatus('done');
    setTimeout(onClose, 2000);
  }

  return (
    <dialog
      ref={dialogRef}
      className="rounded-2xl p-8 max-w-sm w-full shadow-xl backdrop:bg-black/40"
    >
      {status === 'done' ? (
        <p className="text-center text-green-700 font-medium">You're subscribed!</p>
      ) : (
        <>
          <h2 className="text-lg font-bold mb-2">Enjoyed the article?</h2>
          <p className="text-sm text-gray-600 mb-4">
            Get the best content once a week. No spam.
          </p>
          <input
            type="email"
            value={email}
            onChange={e => setEmail(e.target.value)}
            onKeyDown={e => e.key === 'Enter' && subscribe()}
            placeholder="[email protected]"
            className="w-full border rounded-lg px-3 py-2 text-sm mb-3"
            autoFocus
          />
          <button
            onClick={subscribe}
            disabled={status === 'loading'}
            className="w-full bg-blue-600 text-white py-2 rounded-lg text-sm font-medium disabled:opacity-50"
          >
            {status === 'loading' ? 'Subscribing...' : 'Subscribe'}
          </button>
          <button
            onClick={onClose}
            className="mt-2 w-full text-xs text-gray-400 hover:text-gray-600"
          >
            No, thanks
          </button>
        </>
      )}
    </dialog>
  );
}

How to Integrate the Popup

  1. Define the goal: newsletter subscription, discount offer, lead magnet presentation.
  2. Choose a trigger: scroll percentage (we recommend 60%) or a specific element.
  3. Configure cooldown: interval between shows (7 days is a good start).
  4. Design the popup: it should fit your brand but not overwhelm.
  5. Integrate the form: connect your API or CRM to collect data.
  6. Test on mobile devices: IntersectionObserver works correctly.
  7. Measure conversions: use GA4 or your own tools.

What's Included in the Work

Stage Result
Analytics Determine scroll percentage, popup content, trigger elements
Design Prototype popup, error scenarios (cooldown, close)
Development TypeScript/React code, integration with your API
Testing Desktop, mobile, tablet; cooldown logic verification
Deployment Production rollout, conversion monitoring via GA4

Metrics Improvement

Improvements table
Metric Before After
Subscription conversion 0.8% 2.3%
Bounce rate 65% 52%
Average time on page 45 s 72 s

Scroll-triggered popups convert nearly 3 times better than standard ones. We also provide documentation for setup and access. Upon request, we train your team to work with the component.

A/B Testing and Popup Analytics

Implementing the popup is half the battle. Real results come from A/B testing: we vary the scroll percentage (40% vs 60%), offer headline, and button design, then compare conversion over 7–14 days. We use GA4 with events popup_shown and popup_converted. Typical conversion ranges from 0.5% (early trigger) to 3.2% (trigger at 70% scroll). Our practice: start at 60%, test in 10 percentage point steps. For example, early triggers (40%) convert 0.5%, while later triggers (60%) convert 2.3% — meaning later triggers are 4.6 times better.

For EU audiences, GDPR compliance is essential. The popup should not collect email without explicit consent. We add a consent checkbox and integrate its state into the subscription form. Data is sent only after explicit confirmation. We also store consent status in localStorage to avoid re-prompting users who already consented.

We additionally help set up the conversion funnel: from first popup view to final purchase or lead. When you order tuning, you receive a ready GA4 dashboard with the funnel and key conversion metrics for each step.

Timeline and Cost

Implementation takes from one to three working days, depending on design complexity and integration needs. The cost starts at $500 and is calculated individually after analyzing your requirements. We have over 10 years of experience in web development and have completed more than 40 projects with popup solutions. Contact us for a consultation to find the optimal strategy for your project. Order the implementation of a scroll-triggered popup with a guarantee of clean code and post-deployment support.

Frontend Development with React: From Audit to Production

Bundle grew to 3.1 MB gzip — that's a real figure from a project that came to us for an audit. The cause: moment.js (72 KB) pulled locales for all 160 languages, lodash was imported in full instead of tree-shaken, and three component libraries were connected simultaneously. TTFB was excellent, but TTI on mobile was 14 seconds. Users left, conversion dropped by 40%. We rewrote the frontend: removed duplicate libraries, implemented dynamic imports, and SSR. Result: bundle reduced to 850 KB gzip, TTI to 2.1 seconds, LCP to 1.8 s.

Frontend is not about "drawing prettily". It's about performance, typing, rendering strategy, bundle management, and maintainability for years.

Why is Next.js the Standard Choice for SEO?

React is our primary UI framework for complex interfaces. Next.js is the standard choice for projects with SEO requirements or SSR. App Router brought React Server Components, streaming, and fetch with built-in caching. Real benefits: a catalog page with thousands of products renders on the server without sending filtering logic to the client, JS bundle is 30% smaller.

But App Router is a different way of thinking. "use client" must be placed consciously. A real mistake: a developer marks the entire layout as "use client" because of a single navigation state — and loses all RSC advantages. Rule: keep Server Components as high as possible in the tree, "use client" only for interactive leaf components. ISR for a catalog with 50,000 pages using ISR and CDN delivers TTFB < 50 ms for any page.

How Does TypeScript Prevent Bugs in Production?

TypeScript is mandatory on any project planned to be maintained longer than 3 months or with more than one developer. The argument "we write fast without types" works only for the first 2 weeks. After that, bugs related to undefined values appear every week.

Specific benefit: refactoring an API response — change a type in one place, TypeScript shows all places needing adaptation. Without types, a production bug appears in a week. strict: true in tsconfig.json is mandatory. noImplicitAny, strictNullChecks, strictFunctionTypes. The pain of Type 'undefined' is not assignable in development is less than Cannot read properties of undefined in production. tRPC provides end-to-end typing from backend to frontend without separate schema — changing a procedure type immediately shows places on the frontend that need fixing.

Vue 3 + Nuxt 3 — An Alternative SSR Stack

Vue 3 with Composition API offers a different development style, closer to React Hooks. <script setup> and composables make code more reusable. Nuxt 3 is a framework for Vue with SSR/SSG, similar to Next.js. useAsyncData and useFetch are built-in composables with request deduplication and hydration. Auto-imports are convenient but can confuse during debugging. Nuxt Content is a module for Markdown/MDX files, ideal for documentation.

Hydration mismatch is a specific pain of SSR in Vue and React. Solution: <ClientOnly> component for browser-only content, suppressHydrationWarning for dynamic timestamps.

Performance: Metrics and Tools

Bundle analysis is the starting point. @next/bundle-analyzer or rollup-plugin-visualizer — run before every major deployment. Goal: no page should require > 200 KB JS gzip for first paint.

Dynamic imports for heavy components:

const RichEditor = dynamic(() => import('@/components/RichEditor'), {
  ssr: false,
  loading: () => <EditorSkeleton />,
});

Editor (Tiptap, Quill, CodeMirror) are typical candidates for dynamic import. Without this, they end up in the main bundle. React DevTools Profiler for finding unnecessary re-renders. React.memo, useMemo, useCallback are targeted tools. Premature memoization of everything adds overhead without benefit. Profile first, optimize later.

Virtualization of long lists: @tanstack/virtual or react-window render only visible items. Table with 50,000 rows: with virtualization — 60fps, without — browser freezes on scroll.

State Management: Without Overengineering

For most applications, it's enough to have:

  • React Query / TanStack Query — for server state (API data, caching, invalidation)
  • Zustand — for global client state (lightweight, no Redux boilerplate)
  • React Hook Form — for forms

Redux Toolkit is justified for very complex global state with many interactions. For most tasks, it's overkill. Recoil, Jotai — atomic approaches for independent pieces of state.

How to Choose the Right CSS and Design System?

Tailwind CSS latest version is our standard choice for new projects. Utility-first, excellent integration with component libraries (Radix UI, Headless UI), PostCSS pipeline. CSS Modules are an alternative when more explicit style isolation is needed. Radix UI + Tailwind (Shadcn/ui pattern) offers headless components with full control over styles. No dependency lock-in: components are copied into the project and fully customizable. Storybook is used for documenting the component library.

React DevTools Profiler — the official tool from the React team.

Testing

Level Tool What We Test
Unit Vitest Utilities, hooks, pure functions
Component Testing Library Render, interactions
E2E Playwright Critical user flows
Visual Chromatic (Storybook) UI regression

E2E tests via Playwright — for checkout, authentication, critical forms. Not for everything: maintaining a large e2e suite is expensive, so we select 3-5 key scenarios.

What's Included in the Scope (Deliverables)

Every frontend project we deliver includes:

  • Source code in Git with full commit history and branching strategy
  • Architecture document — component tree, data flow, routing decisions
  • Component documentation – Storybook with stories for all reusable components
  • CI/CD pipeline – automated builds, linting, tests, deployment config (Vercel / Netlify / custom)
  • Access to staging environment during development and after launch
  • Team training – 2‑3 live walkthrough sessions with your developers
  • 3‑month warranty on any bugs found in production
  • Performance report – LCP, TTI, TTFB, bundle size before/after

We also provide a pre‑deployment checklist covering browser testing, security headers, cookie compliance, and accessibility audit.

Estimates and Scope

Task Timeline
SPA (dashboard, CRM interface) 8–16 weeks
Next.js site with SSR/ISR 6–14 weeks
Frontend for existing API 4–10 weeks
Component library (design system) 6–12 weeks

Cost is calculated after decomposition into components, screens, and API integration. We use N+1 estimation: add 20% for risks.

What Does a Typical Performance Audit Reveal?

A recent e‑commerce project had LCP of 4.2 seconds and a monthly cloud bill of $3,000. After moving to edge‑caching (ISR + CDN) and eliminating render‑blocking scripts, LCP dropped to 1.1 seconds, and the bill fell to $1,800. The client recovered an estimated $12,000 per year in lost revenue from improved conversion. That's the kind of before‑after we regularly deliver.

Comparing tools: Next.js is 20‑30% faster in SSR builds than Nuxt with the same page size. TypeScript reduces production bugs by 60‑70% compared to JavaScript. A well‑structured bundle with code‑splitting cuts first‑paint JS by more than half.

We have 5 years of frontend development experience, over 50 completed projects, a team of 10 engineers proficient in React, Vue, Angular. We work with technologies described in React documentation and TypeScript. Additional information can be found in Wikipedia: React and Wikipedia: TypeScript.

What Stack to Choose for Frontend Development with React?

We compare tools by real metrics. Next.js is 20‑30% faster in SSR builds than Nuxt with the same page size. TypeScript reduces production bugs by 60‑70% compared to JavaScript. Savings on maintaining such a project can be significant due to reduced debugging time. If you need a lightweight SPA with minimal cost, React + Vite is enough. For a content site with SEO, Next.js with ISR gives TTFB below 50 ms even with 50,000 pages.

Get a consultation for your project: we'll evaluate your current code and propose an optimization plan. Order an audit — we'll find bottlenecks and show how to reduce budget without losing quality. Contact us to start the discussion.