Most of the time, you'll want to follow this pattern when creating listeners:
- If needed, create any profile properties that will be populated by the listener
- Create the listener and save it in a disabled state
- Go to Journey Simulator to observe the effects of the listener in a controlled environment
- Only after confirming the listener is capturing data as expected, re-save the listener in an enabled state
There are multiple reasons for using this pattern. When you take the time to review the data collected by the listener, you are helping to ensure that when the listener is enabled it will be collecting useful information. You'll also have the opportunity to see what other data is being stored when you trigger your new listener. It may be the case that another listener was already configured to do something similar, which you may decide to use instead. Or, you may detect a technical problem with the way your listener was configured which could have resulted in other listeners not behaving as expected.