Overview
ObservePoint has been running millions of Journeys annually since day 1. We have been experiencing issues and situations that led us to continuous learning through all these years.
ObservePoint can answer in many ways to the question "Why Web Journeys?" and here are some of them:
You can continuously monitor the availability of your eCommerce application.
You can ensure a loan application submits the correct data.
You can confirm tags collect funnel data during a checkout flow.
Best Practices
Do not create rules that test multiple tags. Create rules that test a single tag instead.
Do not create long journeys that test entire workflows. Create short journeys that test
a single point of interest instead.
Note: This is applicable unless the workflow is context dependent and you cannot inject data to the session.
3. Do not navigate by clicking. Navigate directly using the Navigate to action instead.
Note: This is applicable unless deep links are unavailable.
4. Do not ratchet up wait times. Trust ObservePoint to wait for network silence after each step instead.
Note: This is applicable unless there is an explicit delay in your event.
5. Do not assume dynamic content is static. Establish test products or facilities instead. You can compensate by creating actions that detect dynamic content.
6. Do not use unreliable selectors. Use reliable selectors instead.
Unreliable Selectors | Better selectors | Reliable selectors |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
7. Work with the responsible teams to add ObservePoint to allowlists to avoid your infrastructure blocks ObservePoint.
8. Do not schedule all your Journeys to run at the same time. Stagger your Journeys to run at different times instead.
9. Do not click everything on a page within a Journeys set up. You can work with your CSM to implement the ClickAll+ solution in an Audit.
10. Do request support from our team by filling the "Journey Support Request Form" and someone from our support team will get back to you to help.
