From Bounce Redirect to Bounce Intent What's changing and why

On 13 April 2026, Google announced a change to its existing policies that will take effect on 15 June 2026. The use of the History API — an established part of the HTML standard — to modify browser history will no longer be permitted by Google. Until now, only malicious redirects were prohibited. Google has now decided to ban all redirects via the History API entirely.

This technique has been the foundation of our service for ten years. Since this is no longer possible, we are migrating all customers to Bounce Intent by 31 May 2026 at the latest — Bounce Intent uses techniques that overlap with Exit Intent — such as detecting exit signals via DOM events. But Bounce Intent is not Exit Intent. Exit Intent fires at every opportunity, often aggressively and usually on every page. Bounce Intent only reacts when an actual intent to leave is detected. Google’s restrictions target browser history manipulation exclusively — not the detection of user behaviour on the page itself. The underlying techniques are long-established and explicitly permitted by Google. We will complete the migration well ahead of Google’s deadline. With us, you’re on the safe side.

Technical Background What Google is specifically prohibiting

Google’s new policy targets the manipulation of browser navigation via JavaScript. The following functions of the HTML5 History API are specifically affected:

  • history.pushState() – adds a new entry to the browser history without loading the page
  • history.replaceState() – replaces the current history entr
  • Event-listeners on the popstate-Event – intercepts navigation triggered by the back button

These functions were previously used to redirect visitors to an alternative page when they clicked the back button. From 15 June 2026, Google will classify this behaviour as a violation of its “Malicious Practices” policy. The potential consequences are significant:

  • Ranking demotion – your pages will be downgraded in search results
  • Complete removal from the index – your pages will no longer appear in Google search results at all
  • Exclusion from Google Ads (SEA) – since December 2024, Google has linked manual spam actions to advertising eligibility. A penalty in organic search can result in losing the ability to run Google Ads

Any one of these consequences could be existential for an online shop. Together, they would be fatal.

Important for you: Google explicitly addresses third-party code. If a script embedded on your site manipulates browser history, you as the site operator bear responsibility — even if you didn’t write the script yourself. The History API is a widely used technique found in many tools and libraries. It is therefore entirely possible that scripts other than ours on your site also use this technique. We strongly recommend auditing all embedded scripts for the use of pushState, replaceState, and popstate.

For our own code, we will handle this ourselves: we are removing the affected functions entirely and guarantee full compliance after the migration.

If you’re unsure whether other scripts on your site are affected, we’re happy to check for you — just write to us at sales@bounce-commerce.de.

Sources:
Google Search Central Blog
Spam Policies for Google Web Search

What's changing? Previously: Bounce Redirect

Our recommendations were triggered after a visitor clicked the back button. Technically, our snippet used history.pushState() to create an additional history entry. When the visitor clicked back, they were redirected to a landing page in your shop’s design with relevant product and content recommendations.

Going forward: Bounce Intent

We detect the moment a visitor is about to leave — and show them the recommendations right then, directly on your page. Browser history is no longer modified. Recommendations appear inline within your familiar shop design.

Technically, we rely on standards-compliant DOM events:

  • Desktop: Mouseleave – the mouse leaves the viewport upward
  • Mobile: Scroll-Up Speed – the visitor scrolls upward rapidly
  • Mobile: Back-to-Entry – the visitor navigates back to their entry page via the back button (only after visiting at least 2 pages)
  • Mobile: Idle – no interaction within a configurable timeout
  • Mobile: Visibility – the visitor switches tabs or minimises the browser

To avoid disruption, triggers are only fired after a configurable delay and are capped per session.

None of these techniques interfere with browser navigation. The visitor can use the back button freely at any time. Many of these parameters can be configured to suit your needs.

What stays the same?

Our AI engine continues to suggest relevant products and content based on your feed. Your existing configuration (exclusion rules, voucher integrations) will be carried over automatically where applicable. Fully GDPR-compliant, without collecting any personal data. No changes to billing. No effort required on your end.

How does Bounce Intent differ from Exit Intent providers?

Exit Intent solutions already exist. Bounce Intent differs in several key ways:

Desktop and Mobile

Most Exit Intent providers only work on desktop, because they rely exclusively on the mouseleave event — an event that doesn’t exist on touchscreens. Our solution detects exit intent on desktop and mobile alike, combining multiple disengagement signals. We remain true to our user re-engagement core.

AI-based recommendations instead of generic content

Conventional Exit Intent solutions show all visitors the same content — typically a discount code or newsletter popup. Our AI analyses the current page and your product feed in real time and delivers relevant product and content recommendations. What previously appeared on the landing page is now shown in the intent layer.

Performance-based billing via affiliate networks

Other Exit Intent tools are billed as SaaS with a flat monthly fee — regardless of whether they generate revenue. Our solution runs through your existing affiliate network (Awin, AdCell, belboon, Tradedoubler, Webgains, and others) and is billed purely on a performance basis. You only pay when you make a sale.

Fully GDPR-compliant without personal data

We use no user tracking, store no profiles, and collect no personal data. Recommendations are based solely on the current URL and your product feed. No cookie consent required for our solution. No data shared with third parties.

Integration within your shop design

Our recommendations appear seamlessly within your shop’s design — not as a generic overlay that feels out of place. The result integrates naturally into the user experience rather than interrupting it.

Timeline

Date What happens
13 Apr 2026 Google announces policy change
By 31 May 2026 Bounce Commerce migrates all customers to Bounce Intent
After 31 May 2026 History API functions are removed entirely from our code
15 Jun 2026 Google’s enforcement deadline – all customers will have been migrated long before this date

New Products

Alongside the migration, we are expanding our portfolio with three complementary solutions. Each works independently — but together with Bounce Intent, they cover the entire visitor journey: from the first page view through product browsing to error pages. All three are powered by the same AI engine and are fully GDPR-compliant without collecting personal data.

Situation Solution
Visitor shows intent to leave Bounce Intent
Visitor lands on a 404 error page 404 Rescue
Visitor browses product or category pages On-Page Recommendations
Visitor doesn’t know what they’re looking for KI Shopping Assistant

404 Rescue

Every dead link, every deleted product page, every mistyped URL costs you visitors and revenue. 404 Rescue detects the error in real time and instead serves the visitor with relevant product and content recommendations — in your familiar shop design, based on the original search intent. Performance-based billing via your affiliate network.

The context: On average, around 1–2% of traffic lands on 404 error pages. In sectors with frequently changing inventory — fashion, seasonal items, promotional goods — the rate is significantly higher: fashion shops replace 30–50% of their inventory each season. Every discontinued product leaves dead links in search engines, price comparison sites, and affiliate networks. After a year without redirect maintenance, a large number of dead URLs can accumulate.

The loss is largely permanent: Google deindexes 404 pages within days to weeks. All link equity — the ranking power built up by a product page through backlinks over its lifetime — is lost in the process. 74% of visitors who land on a 404 page leave your shop and never return. Without active redirect maintenance, this loss compounds with every inventory change. A case study from the Google Merch Shop puts the annual revenue loss from 404 errors on desktop alone at 1.3% of total revenue. That’s revenue permanently disappearing today — and 404 Rescue can win it back.

On-Page Recommendations

AI-curated product suggestions directly on your product and category pages: similar items, complementary combinations, alternatives. The engine matches in real time against your feed and increases basket value and conversion — without the visitor having to leave the page. Performance-based billing via your affiliate network.

The context: Product recommendations account for just 7% of traffic but generate 24% of orders and 26% of revenue. Visitors who click on recommendations buy 4.5x more often. 49% of customers purchase products they would not have considered without the recommendation. At Amazon, over 35% of all purchases originate from product recommendations. Recommendations tailored to the purchase phase can increase conversion rates by up to 8x.

AI Shopping Assistant

A conversational AI sales advisor that guides visitors individually to the right product or answers their questions. Ideal for advice-intensive categories such as beauty, fashion, tech, or outdoor. Fixed pricing tiered by page impressions — details on pricing tiers to follow shortly.

The context: Visitors who interact with an AI chat convert around 4x more often — 12.3% compared to 3.1% without AI interaction. 95% of users who use AI while shopping report that it improved their shopping experience.

FAQ

Do I need to do anything?

No. The migration happens automatically via your affiliate network.

What happens if I’m already using an Exit Intent provider?

We will check before the migration whether you already have an Exit Intent solution in place. If so, we will not proceed with the migration — running two solutions in parallel makes no sense. In that case, we will discontinue our service for you.

We do welcome the opportunity to show you that Bounce Intent is at least equal — with AI-based recommendations, desktop and mobile detection, performance-based billing, and no personal data collected. Get in touch if you’d like to compare.

Will my exclusion rules and voucher configurations be carried over?

Where applicable: yes. If individual settings need to be adjusted, we will inform you in advance.

Does Bounce Intent work on desktop and mobile?

Yes. On desktop, we detect classic exit signals such as mouse movement towards the browser toolbar. On mobile, we use disengagement signals such as scroll behaviour and inactivity. Details on the individual signals can be found above in the “Going forward: Bounce Intent” section.

Is anything changing about billing?

For Bounce Intent, 404 Rescue, and On-Page Recommendations: no. Billing continues as usual on a performance basis via your affiliate network. The AI Shopping Assistant is billed at fixed prices, tiered by page impressions.

Is the new solution GDPR-compliant?

Yes. As before, we collect no personal data. Our recommendations are based solely on the current URL and your product feed. No cookie consent required for our solution. No data shared with third parties.

Will my shop be safe from Google’s policy change after the migration?

Yes. Bounce Intent operates exclusively with DOM events and does not interfere with browser history. None of the functions addressed by Google (pushState, replaceState, popstate) will be used after the migration. We are removing them entirely from our code. Your shop will be fully compliant and safe after the migration.

Does the Google policy affect other tools on my site?

Possibly. Google explicitly notes that third-party code (libraries, advertising platforms, tag manager scripts) can also use the History API — and that you as the site operator are responsible for this. We recommend auditing all embedded scripts for the use of pushState, replaceState, and popstate listeners. For our own code, we guarantee full compliance after the migration.

Can I opt out of the migration?

Yes. You have a special right of termination and can object to the migration informally by email to sales@bounce-commerce.de by 31 May 2026.

I have a question that isn’t answered here.

Write to us at sales@bounce-commerce.de — we’ll get back to you promptly.