Hi Ashwini,
The appearance of "/notset" in the Page Name variable in Adobe Analytics is not a default system behavior. Instead, it is likely caused by an issue in your implementation or data layer setup. Below are some possible reasons and troubleshooting steps to resolve it.
Possible Reasons for "/notset" in Page Name:
Data Layer or Custom Script Issue:
- Check if "notset" is explicitly assigned in your data layer (digitalData or other custom objects).
- Run console.log(digitalData) (or your specific data layer object) in the browser console to see if pageName contains "notset".
Adobe Launch or Tagging Configuration Issue:
- If using Adobe Launch, verify that the Data Element or JavaScript variable used for Page Name is correctly mapped.
- Ensure there are no default values like "notset" assigned when the actual page name is missing.
Tracking Execution Order Problem:
- If the tracking call fires before the page name is available, it may send an incorrect value ("/notset").
- Use a "DOM Ready" or "Page Load Completed" trigger to ensure the data layer is fully populated before firing the tracking call.
Custom Hardcoded Values in Javascript:
- Check whether the value "notset" is hardcoded somewhere in your JavaScript implementation.
- Run s.pageName in the console when the page loads to confirm what is being captured.
How to Fix This Issue:
Check Your Data Layer & Debug the Page Name:
- Open Developer Console (F12 → Console) and inspect the data layer variables.
- Ensure pageName has the correct value before the Adobe Analytics tracking call executes.
Validate Adobe Launch Rules & Mapping:
- Open the Network tab (F12 → Network → Filter "b/ss") and check the pageName parameter in the Adobe Analytics tracking request.
- If "/notset" appears, review your Launch rule conditions and Data Elements.
Ensure Proper Execution Timing:
- Make sure the pageName value is available before the Adobe Analytics beacon fires.
- If necessary, delay the tracking call until the data layer is fully populated.
Thanks,
Vishnupriya R
