Issue
When setting or updating event trigger filters within the Destination Mapping Event Tester, you may find that new example events fail to load or populate in the user interface.
Product
Twilio Segment
Environment
Segment Console
Cause
The Mapping Tester pulls a cached sample from recent live events received by the connected source. If an event matching the exact new criteria (such as an
identify event with properties matching your filters) has not been processed by the source recently, or if the Mapping Tester has not refreshed its active reference parameters, the interface will be unable to display a matching sample payload.
Resolution
To successfully test your updated mapping filters, use the following troubleshooting strategies:
- Save the mapping and reload the page: Configure your event trigger conditions and save the mapping. Having the mapping saved and reloading the page with the correct values ensures that only the latest values are referenced by the tester.
- Monitor the source debugger: Monitor the debugger of the destination's associated source. Using filters within the debugger, you can identify relevant payloads coming through your source to either time exactly when you load your destination mapping test event, or to inspect the incoming data structure.
- Manually trigger a test event: Manually trigger a test event from your application or environment to the source. This ensures the source receives an active event matching your exact criteria to test within a specified timeframe, though it does not guarantee that this event will be available within the sampling of events that the Event Tester pulls from.
- Manually paste the raw payload: If an example event still does not auto-load, copy the raw JSON payload directly from your source debugger, and paste it into the Event Tester payload field so that you can directly review how event properties will be mapped.
Additional Information
For more details, see: