Hi @nehachauhan17 ,
Check for Implementation or Tagging Changes
Older activities may depend on at.js 1.x or specific DOM structures or mbox setups that no longer exist.
Actions:
Ensure your site is running at.js 2.x or 2.9+ (VEC is more stable in later versions).
If you switched from mbox.js to at.js or upgraded from at.js 1.x to 2.x, older activities might not work as expected.
Check whether the target-global-mbox or other custom mboxes still exist in your code.
Confirm the Page is VEC-Compatible
VEC requires:
The page to be publicly accessible, or the domain whitelisted under Target > Setup > Visual Experience Composer Configuration.
The page to not block Adobe scripts with Content Security Policy (CSP) or CORS issues.
Actions:
Open browser dev tools and check for CSP or X-Frame-Options blocking Adobe's editor iframe.
Add your staging/prod domains to VEC Approved URLs in Admin > Setup.
Clear Target's Saved Context / Reset Experience
Sometimes, corrupted cookies or local Target data can prevent old activities from loading properly.
Actions:
Clear site cookies and local storage.
Try opening the activity in an Incognito window.
Ensure you’re logged in with the correct Adobe Org and Workspace.
Check if Activity is Still Active and Matches Audience Rules
If activities were created years ago, they may:
Be expired, archived, or unapproved.
Have outdated audience targeting rules (e.g., browser versions, IP ranges, segments that no longer match).
Actions:
Verify the activity is Active and Approved.
Check audiences and targeting rules to ensure they still apply.
Please check and let me know.
