This discrepancy typically occurs because the audience calculated for a push campaign only includes devices that are currently subscribed and have a valid push token. The segment preview, on the other hand, estimates the number of users or devices that match your filter criteria regardless of their subscription status.
For example, you may have many users who match your Tag criteria but never opted in to push notifications, or whose token was invalidated (app uninstalled, notification permission revoked). Those devices are excluded from the final calculated count, making it look smaller than the estimate.
What to check
- Compare the two numbers with subscription status in mind — a large gap usually just reflects the share of your matching audience that has no valid push token.
- If you need the raw number of everyone matching your filters regardless of token, export the segment via the API: call
/exportSegmentwith"includeWithoutTokens": true, then readdevicesCountfrom/exportSegment/result. See the Segmentation (Filters) API reference. - If your goal is to reach the other devices of a user who matched the filter, enable Include all of a user's devices when editing the segment. If any of a user's devices matches the conditions, all of that user's devices are added to the segment; if the option is off, only the matching devices are included.
Please Note: no segment option makes an unsubscribed device reachable. Devices without a valid push token still cannot receive push notifications; reach them over another channel (email, SMS, in-app) instead.
Comments
0 comments
Please sign in to leave a comment.