Conversion goals often fail to track because users exit the journey before they complete the target action. If a journey does not have a delay block after a message and lacks a defined conversion period, the system stops tracking that user the moment they receive the final communication.
When a user performs a conversion event after they have exited the journey, the system does not attribute that event to the journey. You can fix this using two methods:
Set a conversion period Open your journey settings and define a conversion period. This tells the system to keep listening for the conversion event for a set amount of time after the user reaches the exit point.
Add a delay block Place a time delay block after your last message but before the exit node. This keeps the user active in the journey for a few hours or days, providing enough time for them to complete the conversion event while still inside the flow.
Comments
0 comments
Please sign in to leave a comment.