Browsers push enabled rate

Question: Why is the push-enabled rate very low for Google Chrome but around 99% for Safari?

Answer: The two numbers are calculated over different denominators, because the browsers historically reported subscription attempts differently.

For Chrome, Total Devices counts every unique visitor who interacted with the subscription prompt — whether they pressed "Allow", pressed "Block", or dismissed the dialog. Only those who pressed "Allow" get a push token, so a large share of Total Devices ends up Push Disabled and the push-enabled rate looks low.

For Safari on macOS 10.14–12 (the legacy Apple Website Push flow), Total Devices counted only devices that had a token at some point: users who pressed "Allow" plus users who later unsubscribed manually. Visitors who declined the prompt were never registered at all, so the push-enabled rate is close to 100%.

Important: this Safari-specific difference is legacy. Since Safari 16.4 (macOS 13.3 Ventura) Safari uses the standard Web Push API, exactly like Chrome and Firefox, so for current Safari versions the rate is calculated on the same basis as Chrome and you should expect comparable numbers. A high Safari push-enabled rate in your statistics therefore reflects historical, legacy-flow subscribers rather than a real difference in opt-in behaviour.

When comparing opt-in across platforms, use the device-type definitions described in Push Alerts Enabled devices so you know exactly which population each metric covers.