Adobe Analytics property audit

[AEPAA]

Hi everyone,

Can anyone suggest tips and best practices for auditing.

 If I have global page load rule. With some eVars and props for the rule.

So, should I need to debug every pages of website manually for pageview and s.tl calls and to check variables??

Isn't that header would be mostly same for all pages?

 Any informative tips,  thanks.

[Jennifer_Dungan]

Safest bet would be to check all pages... but it really depends on how complex the Data Element or other parts of the code are....

For instance, if you have a Data Element that is running a complex extraction and manipulation, it may work fine on 95% of your pages, but completely break tracking on the other 5%....

It really depends on your implementation and complexity to know how confident you feel, and if a full regression test is needed vs spot checking... 

[AEPAA]

Hi thanks, , Regression test in the sense need to go over few 100's of pages and every links.?

[abhinavbalooni]

Hi @AEPAA 

As @Jennifer_Dungan mentioned, it depends on the complexity of your implementation.

One thing I think you can start with is, look at the analytics numbers for the important metrics first across pages and try to trend thos numbers. If you spot an anomaly, you can identify pages where there might be an issue.

Do keep in mind thought that you would also need to account for any other business reason a particular page metrics might be low. Also, grab a list of urls for your website and may be lookup those urls in the reports for metrics.

Then you can proceed accordingly.

Hope the above helps.

Regards,

Abhinav

[anu_abraham]

Great responses from @Jennifer_Dungan  and @abhinavbalooni!

As they both mentioned, complexity of your Analytics implementation and your website structure would be the key here. Here are few more aspects to consider.

- If there are eVars or props that are fired on all page loads and are only present during page loads, cross check in Analytics reports to see if there are significant 'Unspecified' values for these variables when Page Views metric is used. If you've complex logic for your variables that are dependent on Data Layer or any Page elements and if the Analytics tracking calls are fired before that logic finishes executing, those variables may not populate as expected. If such an anomaly is found in the report for any of your eVars or props, consider breaking it down by 'Page' or your 'Page URL' dimensions to identify the pages that are most affected and then manually verify.

- Make sure to thoroughly check page loads and s.tl() on most important pages of your site including the Home page, Search, Contact us, and pages with important conversion CTAs or forms.

- You might not need to check all the pages that use similar templates especially when templates are static. In such cases, identify the templates and pick few pages using that template and verify that everything is working as expected in those pages.

- Cross check your Analytics Page URL report with the website URL list and see if any pages are missing in the Analytics report. If there are missing pages, those pages might not have been viewed by the anyone yet or it could be a case of the Launch code missing in those pages.

Hope this helps!