Push Opt-Out Tracking - Workarounds 🤓?

One additional option, if you have access to Query Builder (under Analytics) , is to bypass workarounds entirely and query push token state changes directly.

You can use the query below to identify cases where foreground push was explicitly disabled at the device level, and then reuse the same logic in Dashboard Builder for ongoing tracking:

SELECT 
    TO_DATE(DATE_TRUNC('day', TO_TIMESTAMP_NTZ(TIME))) AS DATE,
    COUNT(*) AS COUNT
FROM 
    USERS_BEHAVIORS_PUSHNOTIFICATION_TOKENSTATECHANGE_SHARED
WHERE 
    TIME > (DATE_PART(EPOCH_SECOND, CURRENT_TIMESTAMP()) - 2592000)
    AND PUSH_TOKEN_FOREGROUND_PUSH_DISABLED = TRUE
GROUP BY 
    DATE
ORDER BY 
    DATE ASC;

This will give you a daily count of users who have flipped foreground push to disabled over the last 30 days. (Tailor the query according to your needs)

If this table is available in your workspace, it’s generally the cleanest and most direct signal for push opt-outs. The Canvas / Message Engagement Events approach is mainly useful when this table isn’t accessible due to a more limited Currents or analytics setup.