In the event of encountering any issues during the Audit process, this help documentation outlines the prescribed general steps that should be undertaken within your browser and the corresponding order for diagnostic testing.
1. Open an incognito window:
Launch an incognito window in your browser. This ensures a clean and isolated session, preventing potential interference from cached data or cookies.
2. Ensure Browser Location Alignment:
Confirm that the browser is set to the specified Audit environment e.g. vpn from a remote location.
3. Reproduce Pre-Audit Action Steps:
Execute the Pre-Audit action steps added in the Audit.
4. Navigate to the desired Page:
Use the browser to navigate to the specific page that you want to check.
5. Replicate On-Page Action Steps:
Follow the on-page action steps outlined in the Audit.
Upon completion of the specified steps in the browser, it is expected that your results align with the results obtained during the Audit. However, in the event of any disparities between your browser findings and the Audit outcomes, please take note of the following:
a. Contact Us for Assistance:
If you encounter discrepancies or require clarification, do not hesitate to reach out to our support team at [email protected]
b. Check the following common issues:
Alternatively, consult the following common issues for insight into resolving the most frequently encountered issues. This resource is designed to guide common challenges and potential solutions.
Reasons why a tag could be missing in an Audit
Understanding the reasons behind missing tags in an Audit is essential for accurate testing. Here are possible scenarios and recommended actions:
1. Tag Missing in Audit but present in the Browser
Issue: The tag is genuinely missing, but browser caching may display it during testing.
Recommendation: For accurate testing, adhere to instructions provided at the top of this help doc, and ensure the tag absence is consistent both in the Audit and the browser.
2. Tag Absent but the Network Request is present
Issue: The network request is present, but the expected tag is missing.
Resolution:
It may be that the network request has not yet been added to our tag database or is associated with a different tag. In either case, our team will submit a request to our engineering team to have it updated.
Navigate to the “Request Log” section from Page Details Report in the Audit.
Search for the network request associated with the missing tag.
If found, contact [email protected] providing:
— The page under examination.
— The network request url.
— The expected tag name.
Note: It may be that the network request is not added in our database or is associated with a different tag.
3. Rule Failures Due to Missing Tag
Issue: Rule failures occur due to a missing tag.
Resolution:
Check the Tag tab in the Page Details Reports for the page in question.
Verify if the tag is genuinely missing or if rule failures stem from account ID mismatches.
Note: Rule failures might happen if the rule's account ID differs from the actual account ID of the tag.
4. Troubleshooting Discrepancies between Audit and Browser Cookies
If you encounter a situation where a cookie is identified during an Audit but cannot be located within the browser, the following steps will guide you through a systematic resolution:
Create a New Chrome Profile:
To conduct accurate testing, it is imperative to ensure that the Chrome profile being used is devoid of any existing cookies. However, to safeguard your primary profile, which may contain critical information such as saved passwords, it is recommended to establish a new Chrome profile dedicated to testing purposes.
Clear Cookies in the New Chrome Profile:
In the newly created Chrome profile, navigate to chrome://settings/privacy. Subsequently, select "Third-party cookies" and proceed to "See all site data and permissions." Execute a thorough clearance of all data by clicking on "Delete all data."
Execute Audit Steps in the New Profile:
Open a new tab within the designated Chrome profile and meticulously perform the steps outlined in the Audit, adhering to the specified sequence. Ensure that each step is accurately executed as detailed in the aforementioned section.
Note: DevTools > Application > Cookies console does not accurately express the state of cookies for a site because it doesn’t take into account a history or indicate what cookies could have been referenced in outgoing HTTP requests or by the application JS executing in the client browser. However, the OP app will always capture the entire cookie picture as we grab all cookies known to the browser at given intervals.
Locating Cookies in DevTools
In the event that you are unable to locate a specific cookie within the DevTools > Application > Cookies console, please follow the outlined steps for a systematic investigation:
Identify the Network Request:
Reference your Audit to identify the network request associated with that cookie. Copy the network request and navigate to DevTools > Network tab, then search for the copied request within the network activity.
Search by Cookie Name:
Within the DevTools > Network tab, utilize the magnifying glass icon to initiate a search. Insert the name of the cookie you are seeking, and the network activity will be filtered to display relevant results.
Utilize Cookie Management Extensions:
Consider enhancing your search capabilities by integrating a dedicated cookie management extension, such as "Awesome Cookie Manager." This tool can provide additional functionality to streamline the process of identifying and managing cookies.
If, despite these efforts, the desired cookie remains elusive within the browser, we encourage you to reach out to our support team at [email protected] for personalized assistance.
Request for Further Assistance
To expedite our support and offer targeted assistance, kindly provide the following information related to the cookie you are attempting to locate:
Cookie Details:
The exact name of the cookie you are searching for.
Audit Reference:
The name or link of the Audit where the specific cookie was initially identified.
Browser Check Reference:
The link of the webpage within your browser where you searched for the aforementioned cookie.
These details will enable our support team to conduct a more precise investigation, facilitating a swift resolution to the challenge you are currently facing.
5. 'Audit starting URLs only' button is toggled on, but the audit is scanning more pages
Issue: The "Audit starting URLs only" button is toggled on, but the Audit is scanning more pages.
Resolution: If the "Audit starting URLs only" button is toggled on and you notice that there are other pages scanned, it means that there are some duplicated links in the Starting URL section.
Check again the Starting URL section and ensure that there are no duplicated links.