Overview
There are a lot of reasons and ways to use ObservePoint. When getting started, it helps if you are able to track down exactly what your business is using the platform for.
Here are some tips on how a new user can work with their team to orient themselves in your company’s unique goals with ObservePoint.
Questions you should ask your colleagues:
What do we use ObservePoint for? (Privacy & compliance validation, analytics or tagging validation, digital marketing validation, or something else?)
Which digital properties do we currently test and monitor with ObservePoint?
How often are we Auditing our web pages? Is our scanning frequency high enough to catch issues in a timely manner?
Are we satisfied with the way we are using ObservePoint now, or is there room to grow?
Which aspects of the website am I responsible for?
Who else is using ObservePoint?
Who is subscribed to ObservePoint notifications, in the event that ObservePoint identifies a problem on one of our digital properties? Will the correct individuals be notified?
How does your organization take action on problems as they are identified in ObservePoint, such as the following:
Broken Pages
Tagging Issues
Cookie Issues
Data Layer Issues
Privacy compliance violations
Consent technology failures
Digital Marketing technology failures
Landing page failures
Permissions
You'll need to identify which level of user permission makes the most sense for you. Visit our help documentation here to learn more about each permission level, as listed below:
Admin
Standard User
Read-Only User
To learn more about ways to use ObservePoint, check out our Use Case Library.