Slide 1: Intro Slide

Slide 2: Statistics about ObservePoint

Statistic 1: Based on the outcomes of a real business case where Texas Instruments used ObservePoint to identify and fix broken tags.
Statistic 2: Based on the outcomes of a real business case where Intouch Solutions went from spending 16 hours to test a site to only 5-10 minutes.
Statistic 3: Based on the fact that automated testing is 6x as fast as manual, assuming audits are only used once. Outcomes are even better when audits reused, which is almost always the case.

Have you experienced the pain of your site updating and it breaking your tracking technologies?
Do all decision makers understand this problem?
What is the current strategy to solve this?
Are there concerns about tracking breaking on key conversion flows?
Are there tag governance concerns?

Explain that ObservePoint uses an alert based methodology to flag any breakage of the tracking.
ObservePoint runs automated scans to collect the data that is being tracked on our visit and matches it to your expectations of what should have been collected from our scan.
ObservePoint uses automated regressions tests to test conversion flows
ObservePoint uses sitewide crawls to automate sitewide tag governance
ObservePoint can also use these tests to validate compliance standards are met or for any ad hoc problem solving needs as well.

Automated testing allows you to:

Walk through the story of how we typically see customers mature in the process of understanding the need to build out a testing practice around web tracking.
What are your key conversion flows are on your site?
How many domains do you manage?
Are you responsible for tag governance across all these domains as well?