DG and Privacy UX
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Monitoring Solutions Knowledge Base

Trackermap Protocol Changes

Trackermap historical scans results are based off the domain protocol.  An interruption of historical scan data results may occur if the protocol that was initial implemented changed on the clients site.  If a client does not have historical Trackermap results for the latest scan week, but the previous weeks display data.  We highly recommend following the steps below to verify what is the cause.


Initial URL implementation


If the clients domain protocol were to change to secure(https),  the associated Trackermap results will not generate. To resolve this issue please update the "Seed Url" and "Target Path" fields with the correct domain protocol within Scan Manager.
Updated URL Implementation





Labels (1)
Version history
Revision #:
3 of 3
Last update:
‎05-15-2019 07:23 PM
Updated by:
Looking for more?
Ask in Discussions

Peer-to-peer support  and answers on developing CMS templates, modifying privacy scripts or building integrations.

Digital Experience Management

Find answers and ask questions on content management, personalization and targeting.

Digital Quality Management

Find answers and ask questions on WCAG and SEO quality management.

Digital Governance

Find answers and ask questions on consent and monitoring solutions.