Include Get Previous Value in Adobe default product | Community
Skip to main content
Level 2
March 5, 2026
New

Include Get Previous Value in Adobe default product

  • March 5, 2026
  • 1 reply
  • 13 views

Include thh Adobe consulting plugin Get previous value as part of the default Adobe product and also make it work across subdomains as this now only works isolated per subdomain. Get previous value is setting information in a cookie e.g. Previous Page Name, but does so on a subdomain level which makes the previous page name to not work properly across subdomains e.g. www.website.com and secure.website.com 

1 reply

Jennifer_Dungan
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
March 5, 2026

While I agree with you that this would be a nice feature, this isn’t so easy to make work the way you would like…

 

This feature uses Cookies to store the “page” value, then on the next page, read that value, put it into the dimension of your choice, then override the value in the cookie to be ready to track on the next page.

 

Cookies can be set to “.website.com” and work on both www. and secure. in your example… but for other uses, like moving between domains (on the same tracking suite/implementation) such as www.domainA.com and www.domainB.com are impossible, without sending the data in an alternate way (like appending the previous page name into the URL with a query string parameter… which may not be ideal for all companies.

 

I think this is why Adobe has a specialized panel in workspace for “Next or Previous” where they are using segmentation to get the previous value, without the need to track an extra value in a custom dimension. This will work across both sub-domains and fully different domains. 

 

You should check this out and see if it supports your needs.

 

I am still going to give you an upvote, because any tools or improvements for understanding our User Flows is important and even if this doesn’t get picked up exactly as requested, it hopefully will inspire improvements in this area.

LiFaAuthor
Level 2
March 5, 2026

Agree that it wouldn’t solve tracking across completely different domains, but getting subdomains to work (as it actually does with AppMeasurement and the consulting built plugin) would provide additional value for some use cases even not for all. I haven’t explored the Next or Previous Item, so thanks for that tips :)

Jennifer_Dungan
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
March 5, 2026

Yeah, there are caveats to every solution… I agree, making it more in-line with Activity Map on AppMeasurement would make a lot of sense… but I suspect the decision to move away from cookies was to be more inline with GDPR….   😔

 

While I agree to a point what GDPR is trying to do… I also believe the went too far and too restrictive on a lot of things….. and it causes a lot of headaches….

 

In the meantime (since even if Adobe does pick this up, it will be a while), play with the Previous Item panel and see if that will support your needs for now. Good Luck.