If your event-based Segments stay empty even though you can see the events arriving in Pushwoosh, it is almost always because Pushwoosh cannot tie those events to a user profile in your audience. Segments are built over identified users and devices, so an unattributed event never lands in one.
1. Make sure identity mapping is configured
For platform integrations such as Amplitude, attribution happens through the UserID:
- In the integration settings, map the third-party user identifier to the Pushwoosh User ID field (in Amplitude, pick the user property that holds your Pushwoosh UserID).
- Your app must actually set that same UserID on the device through the Pushwoosh SDK (
setUserId). If a device has no UserID, or the identifier coming with the event matches no user in Pushwoosh, the event cannot be linked to anyone and no segment will pick it up. - Check that the values are identical on both sides — a prefix, a different casing, or an internal numeric ID on one side and an email on the other is enough to break the match.
2. If you post events directly via the API
When you send events yourself with the /postEvent method rather than through a packaged integration, each request must identify its subject explicitly — pass the device's hwid and/or the userId. Events posted without either cannot be attributed.
How to verify
- Open the user or device in the Control Panel and confirm the UserID you expect is present.
- Check the event in the Events section: if it arrives but is not associated with a user, the mapping is the problem, not the segment filter.
- Re-check the segment filter itself (event name spelling, time window, attribute conditions) once attribution is confirmed working.
Reference: Amplitude integration.
Comments
0 comments
Please sign in to leave a comment.