Discover more about Tag Management
Audits are prescriptive, simulations are protective. Audits can tell you about tagging issues that need to be fixed, and simulations can alert you when new tagging problems appear.
Read more on our blog. Site Audit and Simulations: What’s the difference?
ObservePoint is integrated with every major digital marketing technology.
Yes. ObservePoint contributes to an overall data quality practice. Manual page level debugging, automated site audits, tag regression testing, Selenium scripts and so forth can all contribute to improved data quality. It’s important to understand that none of these are one-time events—there has to be an ongoing commitment to achieve high-quality data.
Yes! We support all mobile browsers.
Hard to say. How long has it been since you took the red pill?
No. Websites are complex and always evolving. One audit is great for telling you what is a problem today, but data quality management is a process, most effectively performed on an ongoing basis.
Yes! Tag management systems are great and help teams become more efficient and sophisticated. They also introduce additional tagging to the site and can cause blind spots.
It’s not difficult—there’s no code to deploy! ObservePoint requires a configuration of the audits, simulations and reports rather than any deployment to your site(s).
It can. For example, if the tag is in the bottom portion of the page that is loading slowly, the page view might not be recorded in the web analytics solution. Consequently, this page might falsely show very low page views.
Yes. ObservePoint can simulate visitor actions, such as a user login. We recommend automating this and this is a very common practice among our customers.
A few days. There is no code to deploy, so all setup is done through our user interface.
This depends on your business needs, but generally our customers find the most value aligning with their release cycles, reacting to business conditions that dictate audits, and performing proactive audits in anticipation of large project releases. For more information about audit frequency and timing, read about the Data Quality Management Process.
Yes. ObservePoint supports a variety of browser agents and devices.
Yes. Our patented technology actively interacts with your website’s user interface and most of the time this is self-configured in our platform.
Don’t wait. Auditing now can help you be sure that you have completely removed any old tags from your website and correctly deployed your new solution.
Start with some baseline audits to get an idea of what your data quality challenges are. Once you’ve done that, you can make a plan to measure, improve, and protect your data using our data quality management platform and processes.
ObservePoint TagDebugger™ is an excellent alternative for web analysts who may currently use one or more of the following: WASP, Charles, Fiddler, OmniBug, SiteCat Debugger, Omniture Debugger, DigitalPulse Debugger or Google Tag Assistant.
Use the TagDebugger™:
Use the Tag Debugger
Tag Name / Path: This is the name ObservePoint uses to uniquely identify each vendor and tagging technology. The path is the tag request up to the query string.
Account: This is the SiteCatalyst report suite, Google Analytics profile, Webtrends DCSID, etc. – within ObservePoint we call them accounts.
Category: ObservePoint’s classification of the kind of tag listed. Categories include analytics, advertising, tag management, video, voice of consumer, split testing, eCommerce and lead tracking. For a complete list of all tags we support please visit our supported tag vendors.
Status: The network status code of the tag request. Most should be status 200 (OK).
Request / Response Size: Request is the amount of data sent to the vendor’s collection servers. Response is the data sent back to your web browser by the vendor.
Total Time / Latency: Total time is measured from the initial request for the tag to time it is fully loaded. Latency is the time it takes from the initial request to the first response from the vendor.
Detailed view of SiteCatalyst, showing a listing of each of the variables found as part of the tag.
Yes. Find this in the Duplicate or Multiple Requests report. Duplicate tags may be an indicator of data inflation.
Most of the time yes, but it depends on the tag. For example, we support HBX all the way to the current SiteCatalyst tags. Typically if a tag has version data we will catalog it.
Yes. We follow all redirects and will audit the terminal page if it is allowed by filters defined in the audit. We also catalog all other server status codes such as broken and access denied pages.
Yes. One item that makes ObservePoint unique in this area is that we observe actual image request for a given tag.
Yes! Follow these steps to configure an audit to scan a mobile site.
The ObservePoint tag database is constantly growing and being updated.
Yes, we will typically see tags loading from iframes without a problem. We observe the network traffic for particular page tags that load from an iframe are part of the network requests.
Most people simply use the email feature on their smartphone, but we can send a text as well. If you want us to send you a text instead, follow these guidelines. Replace “phonenumber” with your own phone number, area code first. Do not include dashes, parentheses, or spaces.
We recommend setting page and tag alerts when you may have doubts concerning the reliability of page. Doubts, for example, could be triggered by a page impression report that shows a sudden drop in traffic, even though the tagging audit shows complete tagging implementation. Our alerting functionality can also be used to record a process or form being filled out. We can then replace this at a specified interval and alert you if the process breaks.
This information is privileged and is available to ObservePoint customers only.
If you are a customer please contact us and we’ll be happy to provide you with the information you need.