User profiles in different workspaces | Community
Skip to main content
Michael_Soprano
Level 10
August 14, 2025
Question

User profiles in different workspaces

  • August 14, 2025
  • 1 reply
  • 341 views

Does Target keeps separate profiles for different workspaces? Or not and profiles might be merged?

Examply:

1. Domain 1 - Workspace 1 - User 1

2. Domain 2 - Workspace 2 - User 1

Would Target keep separate profile or it would be one profile?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

NarenKotipalli
Level 3
August 14, 2025

@michael_soprano 

Basically, Adobe Target maintains profiles at the visitor level, not based on workspaces. That means profiles are not kept separate for each workspace.

 

Now, coming to domains:

 

  • If it’s a main domain and its subdomains (like example.com and shop.example.com), then usually it’s considered one profile, since cookies can be shared across subdomains (if set on the root domain).
  • But if it’s two completely different domains (like example1.com and example2.com), then Target will consider them as two separate profiles because cookies can’t be shared across different domains due to browser restrictions.

 

So in your example:

  • Domain 1 - Workspace 1 - User 1
  • Domain 2 - Workspace 2 - User 1

If the domains are different, even if it’s the same user, Target will treat them as two separate profiles.

 

That said, with cross-domain tracking, you can link users across domains by following certain setup steps. This lets Adobe Target recognize the same user on multiple domains and keep a unified profile.

 

Hope this clears things up! Feel free to reach out if you’ve got any more questions.

 

Best,

Narendra

Michael_Soprano
Level 10
August 17, 2025

With Web SDK I can use 3rd party cookies enabled and then with multiple domains profiles should be merged?

NarenKotipalli
Level 3
August 20, 2025

@michael_sopranoI haven't tried this myself yet, but according to the documentation, it should work as expected. However, given the evolving third-party cookie support in modern browsers, you'll need to carefully weigh the pros and cons to determine what approach works best for your organization.