Hi @nitesh__anwani ,   Although mobileappid is not a persisted variable by design, Adobe Analytics’ processing layer may carry forward certain context data across hits within a visit when the Experience Cloud Visitor ID (ECID) is shared — as is the case with appendVisitorInfoForUrl().   In practice:...

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...

Hi @NingLaoShi ,   Adobe Target processes profile parameters on the first call — so if: The parameter (e.g. industry, companyName) is not yet set in localStorage (e.g. before Demandbase script has loaded), Target may receive and store a null (or empty) value into the visitor profile. If you don't ...

Hi @Michael_Soprano ,   Extending the visitor profile lifetime in Adobe Target from 14 days to 90 days typically does not increase your license costs directly, as Adobe currently does not charge extra for extending this duration. However, there are indirect considerations that could impact your over...

Hi @Viraj_Bankar ,   Since you were successfully moving AEP audiences from the Default workspace to a custom workspace as recently as May 5, 2025, and the error suddenly started, this strongly suggests that something has changed in the environment or backend, not in your process. Recent Changes in A...

Hi @dineshpr ,   Krishna is already explained. Options and What They Mean: "Within 1 week" = The purchase happened within 7 days after the email click. "After 1 week" = The purchase happened more than 7 days after the email click. "Within 1 day" = Purchase happened within 24 hours. "After 1 day"...

Hi @TNxx,   On the first page load, the user hasn't yet qualified for either Activity A or B in their profile stored on Adobe Target's edge network. That means: When the visitor hits the page for the first time, they haven't qualified for any activities yet.The decisioning engine can't yet include A...

Hi @bkrane2 , These scripts run on the edge (server-side), so tracking browser behaviors (like scroll or time on page) needs to be collected client-side and passed into Target as profile parameters using targetPageParams() or adobe.target.trackEvent().   So each use case requires: Client-side JS to ...

Hi @KhushbooBh3 ,   You Do Not Need to Include Success/Confirmation Pages in the Activity Setup Run the test activity on a limited set of pages (e.g., Step 1 of a form, or the homepage). Track goals/conversions that happen on separate, downstream pages (e.g., form submission on Step 5, or an order c...

Hi @KhushbooBh3 ,   Yes, Adobe Target can track a "Viewed a Page" conversion goal even if the page being viewed is not part of the actual activity/page where the A/B test is running. Here's how it works under the hood:   When a user is exposed to your A/B test (i.e., a Target activity delivers a var...