Purchases on mobile Chrome dropped to zero for two straight days (Jul 9–10) while every other browser and device segment improved over the same window. This report breaks down overall conversion rate by browser and lays out what we need the dev team to check.
US paid search & paid social sessions, Jun 15 – Jul 12 (4 weeks)
Blended (all browsers)
2.82%
11,648 sessions · 329 purchases
Chrome
3.64%
Above blended average
Safari
2.26%
Below blended average
Samsung Internet
3.92%
Small sample (102 sessions)
| Browser | Sessions | Purchases | Conversion rate | Bounce rate | Engagement rate |
|---|---|---|---|---|---|
| Chrome | 4,869 | 177 | 3.64% | 31.3% | 68.7% |
| Safari | 6,411 | 145 | 2.26% | 37.5% | 62.6% |
| Samsung Internet | 102 | 4 | 3.92% | 28.4% | 71.6% |
| Edge | 125 | 3 | 2.40% | 23.2% | 76.8% |
| Firefox | 94 | 0 | 0.00% | 34.0% | 66.0% |
| Other (Opera, in-app browsers, etc.) | 47 | 0 | 0.00% | – | – |
| Total | 11,648 | 329 | 2.82% | – | – |
Over the full 4-week window, Chrome actually converts above the blended average — this confirms the mobile Chrome issue below is a localized, dated event rather than Chrome underperforming as a browser generally.
The core finding
On July 9 and July 10, mobile Chrome visitors browsed the site normally (bounce rate and engagement rate unchanged) but zero of them completed a purchase — out of 205 combined sessions across those two days. No other segment showed this pattern.
| Date | Sessions | Purchases | Purchase rate |
|---|---|---|---|
| Jul 2 | 89 | 7 | 7.9% |
| Jul 3 | 92 | 0 | 0.0% |
| Jul 4 | 109 | 3 | 2.8% |
| Jul 5 | 83 | 2 | 2.4% |
| Jul 6 | 134 | 1 | 0.7% |
| Jul 7 | 95 | 1 | 1.1% |
| Jul 8 | 97 | 2 | 2.1% |
| Jul 9 | 107 | 0 | 0.0% |
| Jul 10 | 98 | 0 | 0.0% |
| Jul 11 | 110 | 2 | 1.8% |
| Jul 12 | 132 | 1 | 0.8% |
Bounce rate and engagement rate for mobile Chrome didn't change on Jul 9–10 versus surrounding days. People are landing and browsing normally.
Meta and Google Ads performance didn't dip on these dates. Desktop Chrome and both Safari variants improved over the same window.
Chrome's major version update (v150) rolled out July 9 — the same day. Circumstantial, but the timing lines up closely enough to test directly.
Run the full booking flow on an Android device using Chrome, start to finish: amazingco.me/us/experiences/mystery-picnics/dates/upper-east-side → select date → guest details → payment → confirmation.
Open Chrome DevTools (Console + Network tabs) during that flow, specifically watching the payment submission step for JS errors or failed (4xx/5xx) requests.
Check whether anything was deployed to checkout or payment code around July 8–9, and check payment gateway logs for declined or failed transactions from Chrome mobile specifically on Jul 9–10.
If session recordings (e.g. Clarity/Hotjar) are available, pull mobile Chrome sessions from Jul 9–10 specifically to see exactly where users stopped.
Note: daily volumes here are under 150 sessions, so treat this as a strong, specific lead worth testing directly — not statistical proof on its own. Over the full 4-week window (table above), Chrome converts at or above average, which is why this looks like a dated, localized event rather than an ongoing browser-level problem.