Easy Steps to Tracking Your Analytics Code Version for Rich Insights

If you are running an Adobe Analytics implementation, you may already be aware of the challenges associated with using multiple platforms or content management systems, multiple domains and subdomains, and outsourced content. The complexity can grow over time, and you need tools to account for all these pages, primarily for two reasons:

• You need to maintain code and update your libraries on a regular basis.
• You usually need to be able to segment on specific properties. Once you have these dimensions available to you, you can monitor your code on all pages and create Virtual Report Suites very easily.

AppMeasurement Code Version makes the job easier

AppMeasurement Code Version, a piece of information available in all image requests, allows you to effectively track your code version. Available out of the box through processing rules, AppMeasurement Code Version allows you to get the data related to your Analytics implementation, including pages you were not aware of, without much effort**.**

When you combine this information with your Page Domain (or App ID — if you are tracking mobile apps), you can monitor all your hits on all your properties, including mobile apps and XML calls.

Doing it right

Start by creating a workspace and visualize the percentage for your different Analytics library version on a pie chart. If you have a fragmented implementation, it’s time to get working on aligning your different codes. It’s critical to maintain consistency and recency for your library, so you can take advantage of bug fixes and new features. Also, keep track of your different libraries to take advantage of anomaly detection.

Schedule this workspace so that it’s available to you before your governance meeting. From there, you can confidently talk about your implementation status for key requirements that are needed for several integrations. Ensure you have, on all your pages, the minimum required version needed for the “Analytics for Target” (A4T) integration, Video Heartbeat, and Adobe Audience Manager server-side integration.

The obvious next step is to include the other Adobe libraries if you also deploy them. But this will require you to add some additional JavaScript in your Analytics implementation. Being accountable with actual data for all your pages, and not just the few that you check on a regular basis, will ensure you keep the cadence and discipline required for a successful Analytics program.

[Note: The details in this post are fairly technical so if you’re not the person responsible for tracking and validating your app analytics, you should pass on the details to the lead responsible for validation.]