Behavioral Pop-up Windows: Configuring Triggers to Boost Conversion

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
Behavioral Pop-up Windows: Configuring Triggers to Boost Conversion
Medium
~2-3 days
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

Typical scenario: an e‑commerce store with 2,000 visitors per day and a conversion rate of 0.3%. After implementing behavioral pop-ups with exit intent and scroll depth, conversion rose to 1.2%. Many developers make the mistake of showing a pop-up by timer—this annoys 70% of users. We use a combination of 4–5 behavioral pop-ups that take context into account. Our engineers are JavaScript certified with 5 years of experience and have completed over 150 successful projects. We guarantee quality and 30 days of support.

How to configure an exit intent trigger without false positives?

The most effective trigger for landing pages is exit intent. It fires when a user sharply moves the cursor toward the top edge of the screen. The key parameter is the sensitivity threshold: 10 pixels from the edge and upward velocity >50 px/ms. Without this filter, the pop-up will show on every random movement. For mobile devices, exit intent does not work—there we use the popstate event on the back button.

class ExitIntentDetector {
  private threshold = 10;
  private sensitivity = 50;
  private triggered = false;
  private lastY = 0;
  private lastTime = 0;

  constructor(private onExit: () => void) {
    document.addEventListener('mousemove', this.handleMouseMove.bind(this));
    // Mobile fallback
    history.pushState({ popup: true }, '');
    window.addEventListener('popstate', () => {
      if (!this.triggered) {
        this.triggered = true;
        this.onExit();
        history.pushState({ popup: true }, '');
      }
    });
  }

  private handleMouseMove(e: MouseEvent): void {
    if (this.triggered) return;
    const now = Date.now();
    const deltaY = e.clientY - this.lastY;
    const deltaTime = now - this.lastTime;
    const velocityY = deltaY / deltaTime;
    if (e.clientY < this.threshold && velocityY < -this.sensitivity) {
      this.triggered = true;
      this.onExit();
    }
    this.lastY = e.clientY;
    this.lastTime = now;
  }

  reset(): void {
    this.triggered = false;
  }
}

const detector = new ExitIntentDetector(() => {
  showPopup('exit_offer');
});

Why is it important to manage pop-up queue?

If you do not control the display, a user will see two or three windows at the same time—this is annoying and reduces conversion. The PopupManager state manager solves the problem: it stores shown window markers in localStorage and blocks simultaneous opening. Additionally, a cooldown is set—default 7 days—after which the window can appear again.

class PopupManager {
  private shown = new Set<string>(
    JSON.parse(localStorage.getItem('shown_popups') ?? '[]')
  );
  private currentPopup: string | null = null;

  canShow(id: string, cooldownDays = 7): boolean {
    if (this.currentPopup) return false;
    const key = `popup_shown_${id}`;
    const lastShown = localStorage.getItem(key);
    if (!lastShown) return true;
    const daysSince = (Date.now() - parseInt(lastShown)) / 86400000;
    return daysSince >= cooldownDays;
  }

  show(id: string): void {
    if (!this.canShow(id)) return;
    this.currentPopup = id;
    localStorage.setItem(`popup_shown_${id}`, Date.now().toString());
    this.shown.add(id);
    localStorage.setItem('shown_popups', JSON.stringify([...this.shown]));
    document.getElementById(`popup-${id}`)?.classList.add('popup--visible');
    document.body.classList.add('popup-open');
  }

  close(id: string): void {
    this.currentPopup = null;
    document.getElementById(`popup-${id}`)?.classList.remove('popup--visible');
    document.body.classList.remove('popup-open');
  }
}

const popups = new PopupManager();

Trigger comparison

Exit intent by conversion (up to 5%) outperforms timer pop-ups (0.5-1%) by 5 times. Scroll depth is also 3-4 times more effective than timer on long pages.

Trigger Implementation complexity Effectiveness Typical use
Exit intent Medium High Discount offer on exit
Scroll depth Low Medium Show content after reading
Time on page Low Low General offer
Inactivity Medium Medium Recapture attention
Element visibility Medium High Contextual hints

Step-by-step implementation process

Stage Duration Result
Behavior analytics 1-2 days Trigger and segment map
Trigger development 2-4 days Working exit intent, scroll depth detectors, etc.
Pop-up layout & design 1-2 days Responsive mockups
CRM/ESP integration 1-2 days Automatic lead transfer
A/B testing 2-3 days Conversion optimization
Documentation & training 1 day Instructions for the team

What's included in the work

  • Analytics: heatmaps, segmentation, trigger selection for your audience.
  • Development: all triggers (exit intent, scroll depth, element visibility, inactivity timer) with PopupManager.
  • Design: responsive mockups in your site style—up to 5 variants.
  • Integration: CRM, ESP, analytics systems (Google Analytics, Yandex.Metrica).
  • Tracking: automatic recording of impressions, clicks, closes in dataLayer.
  • Documentation: trigger descriptions, code, marketer instructions.
  • Support: 30 days after launch—fixes, fine-tuning, consultations.

How A/B testing increases conversion?

We run A/B tests: compare a timer pop-up versus a behavioral one. Result—behavioral gives +180% conversion with the same traffic. We test different offers, headlines, colors. Order a pop-up system implementation with A/B testing.

How to configure scroll depth and element visibility

These triggers require minimal code but give a noticeable conversion boost on pages with long content.

function onScrollDepth(percentage: number, callback: () => void): () => void {
  let fired = false;
  const handler = () => {
    if (fired) return;
    const scrolled = window.scrollY + window.innerHeight;
    const total = document.documentElement.scrollHeight;
    if (scrolled / total >= percentage / 100) {
      fired = true;
      callback();
    }
  };
  window.addEventListener('scroll', handler, { passive: true });
  return () => window.removeEventListener('scroll', handler);
}

onScrollDepth(70, () => showPopup('mid_page_offer'));
function onElementVisible(selector: string, callback: () => void): void {
  const el = document.querySelector(selector);
  if (!el) return;
  const observer = new IntersectionObserver(
    (entries) => {
      if (entries[0].isIntersecting) {
        observer.disconnect();
        callback();
      }
    },
    { threshold: 0.5 }
  );
  observer.observe(el);
}

onElementVisible('#pricing-section', () => showPopup('pricing_helper'));

For more details, see IntersectionObserver.

Impression tracking

Each pop-up must record impressions, clicks, and closes. We integrate this via gtag or dataLayer events without additional code—tracking is automatically connected to PopupManager. Get a consultation to assess your project. Contact us for further details.

Economic effect

Replacing timer pop-ups with behavioral ones increases conversion by 3–5 times with the same traffic costs. Payback occurs within the first week due to reduced bounce rate and increased leads. We implement a turnkey system in 3–5 days.

What typical mistakes are made during configuration?

  • Showing pop-up without cooldown—user sees the same thing on every visit.
  • Ignoring mobile devices—exit intent doesn't work; need popstate.
  • Lack of a queue manager—two pop-ups simultaneously.
  • Too aggressive exit intent—fires on normal scrolling.

Avoiding these mistakes will yield conversion growth without hurting UX. We will assess your project for free.

Setup Web Analytics: GA4, GTM, Yandex.Metrica, and Amplitude

We often see: conversion rate 1.2%, traffic grows, but conversion stays flat. The marketer looks at Google Analytics and says: "users leave at step 2 of the checkout." The developer opens the same step — no errors, Sentry is silent. So it's not a JS bug, but a UX issue or skewed data from analytics. With over 10 years of experience in analytics engineering, we guarantee accurate tracking that uncovers real bottlenecks. Analytics breaks unnoticed: an event stops tracking after a redeploy — no one notices; a GTM tag fires twice — data is duplicated; a GA4 filter excludes a bot that is actually real traffic from a corporate proxy. An audit of your current tags will find the cause within a week.

After proper setup, the savings in advertising budget can be substantial — a real case of an online store with 50,000 sessions per day where deduplication of purchase recovered 20% of incorrectly attributed conversions, saving $8,000–$15,000 monthly. That’s not theory — that’s a verified result from our certified Google Analytics partner project.

Why do GA4 events duplicate and how to fix it?

Universal Analytics is gone, replaced by GA4's event-based model. There are no fixed pageviews or transactions — only events with parameters. This is more flexible but requires proper event design. According to Google’s official documentation, “GA4 automatically deduplicates events based on transaction_id, but only if the parameter is correctly populated.” Many implementations miss this.

Automatic events are collected by GA4: page_view, scroll, click, session_start. Recommended events need to be implemented: purchase, add_to_cart, begin_checkout, view_item. Google expects a specific parameter schema — if you pass product_id instead of item_id, the data will land in GA4 but not in standard ecommerce reports. Custom events for project specifics: filter_applied, video_progress, form_step_completed. Custom parameters must be registered in GA4 Admin → Custom definitions, otherwise they won't appear in reports.

A common mistake is the purchase event being duplicated. Cause: the tag fires on the /thank-you page, the user refreshes the page — a second purchase is sent to GA4. Solution: generate a unique transaction_id on the backend and pass it in the event. In our experience, 80% of e-commerce stores have this issue. GA4 deduplicates based on it (in theory — verify with DebugView). Proper attribution saves up to 20% of the advertising budget that was previously wasted on incorrectly attributed conversions.

How to set up the data layer to avoid data loss?

GTM is a tool for managing tags without code deployment. But "no code" doesn't mean "no architecture." The data layer is the foundation. We pass data from the application to GTM via dataLayer.push(). Structure: event + contextual data. For e-commerce: before opening a product page — push with product data. GTM tag reads from the data layer, not from the DOM.

window.dataLayer = window.dataLayer || [];
dataLayer.push({
  event: 'view_item',
  ecommerce: {
    items: [{
      item_id: 'SKU-12345',
      item_name: 'Product name',
      price: 1990.00,
      currency: 'USD'
    }]
  }
});

Bad practice: GTM tag parses the DOM — looks for the price in span.price, the name in h1. This breaks with any layout change. Good practice: always use the data layer. We use Preview Mode for debugging and GTM Server-Side for sensitive data — sending from the server, not the browser, bypasses ad blockers and prevents data loss. A properly implemented data layer reduces tracking errors by 95%.

How does Yandex.Metrica complement web analytics?

For a Russian audience, Metrica is a must — especially Webvisor. Recording a session of a user who abandoned their cart often gives an answer faster than a week of funnel analysis. Goals in Metrica: event-based (via ym(COUNTER_ID, 'reachGoal', 'GOAL_NAME')) or automatic (button click, page visit). Integration with CRM via Metrica Plus — passing offline conversions. Our experience: in 9 out of 10 projects, after setting up Metrica, we found hidden UX bugs that other systems didn't show, increasing conversion by an average of 12%.

What does product analytics give in Amplitude?

Amplitude is a product tool, unlike marketing-oriented GA4 and Metrica. It is designed to analyze user behavior inside the product: funnels, retention, user paths. Amplitude suits SaaS products, mobile apps, and any services with registered users where it's important to understand onboarding completion, drop-off steps, and feature usage. Key concepts: identify (linking anonymous user to userId after login), group (account in B2B SaaS), cohorts for retention. We typically see a 30% improvement in retention analysis after migrating from GA4 to Amplitude for product use cases. Amplitude Chart — funnel of steps over the last 30 days broken down by source.

Monitoring Data Quality

Analytics without monitoring is a black box. We set up:

  • GA4 Realtime — check after every deploy that key events are coming in
  • Alerting in GA4 — anomaly in the number of purchase events (sharp drop = something broke)
  • GTM Preview in staging before production
  • Manual funnel tests once a week — simply go through the buyer journey and verify everything is tracked
What we check after each deploy
  • All recommended events present in DebugView
  • No duplicates (count purchase per 100 sessions)
  • Data layer structure unchanged after frontend update

What the work includes

Component Description
Audit of existing tags Check current GTM tags, data layer, duplicates, and errors
Event schema design Documentation: event list, parameters, triggers
GA4 + GTM setup Create configuration, tags, custom definitions
Yandex.Metrica Install counter, create goals, set up Webvisor
Amplitude (optional) Set up client and server SDK, cohorts
QA and monitoring Testing in Preview Mode, alerting
Training and handover Access, instructions for adding new events, console

Process and timeline

  1. Audit of existing tags and data (2 days)
  2. Event schema design (2 days)
  3. Data layer development and tag setup (3–5 days)
  4. QA in Preview Mode and staging (2 days)
  5. Deploy and dashboard setup (1 day)
Scenario Timeline
Basic GA4 + GTM setup 1 week
Full e-commerce tracking + Metrica 2–3 weeks
Server-side GTM + Amplitude 3–5 weeks

Cost is calculated individually. Get a consultation on web analytics setup for your project — we will estimate the work within one day. Contact us to get started with a free audit of your current tracking.