VEC activity - what is default property for display ?

[Michael_Soprano]

What property is the default one for VEC? How to change default one?

[SarthakBh]

For default workspace we don't need a property; property is required for non default ones 

[Michael_Soprano]

So what is the best practice when I have dev and prod environment?

Two properties (one dev and one prod) in one workspace?

Two workspaces (one dev and one prod) and mapped specific properties to specific workspaces (dev property + dev workspace && prod property + prod workspace)?

[Gokul_Agiwal]

Hi @Michael_Soprano  

As Sarthak mentioned, don't need a property for Default workspace. 

default workspaces function as a type of catch-all environment, where anyone who has access to Target will have access to that Organization’s default workspace. It is up to the Administrator to restrict users’ access to the default workspace and instead assign those users to a Workspace that specifically concerns their work.

Regarding the best practice ,  First Understand workspace 

One of the most common use cases is to split workspaces by geographic region, so that teams have their own separate space where their relevant Properties, Activities, Audiences, and Offers live. To set up a configuration like this, create a workspace for each of your organization’s regional teams. 

For example - in my case, I've created a separate workspace for China, as my client team based in China. like below 

When it comes to property, I've created a property for each environment like below and assigned these properties to a single workspace created above. 

Since this Workspace is being created for teams based in China, it should only include those properties that this team will need access to, namely, those that are based in China. ( see in above image, highlighted in Red ) 

As per above example 

Once the above setup done,  update your implementation to include at_property parameter code with respective to environment.  ( This at_property is different for each) 

To obtain the at_property parameter code:

Go to Target, click Administration > Properties to display the Properties list. 

1. Hover your mouse pointer over the Last Updated column for the desired property to display and click the Code icon.
2. Right-click the highlighted implementation code to copy it to your clipboard.

For more information on how to used at_property code in your implementation - please check below guide. 

https://experienceleague.adobe.com/en/docs/target/using/administer/manage-users/enterprise/propertie... 

https://experienceleague.adobe.com/en/docs/target-learn/tutorials/administration/set-up-workspaces 

https://experienceleague.adobe.com/en/docs/target/using/administer/manage-users/enterprise/propertie... 

https://experienceleague.adobe.com/en/docs/experience-cloud-kcs/kbarticles/ka-17521 

Hope it helps. 

Thanks 

[Michael_Soprano]

Thanks!

I have got one country some my case is simpler 😄

I totally get at_property functionality and how to map this to Datastreams in Data Collection

1. So what is the practical use-case of Default Workspace? Only functionality - that you can see everything in one place?

2. I set up something like this:

Dev workspace & Dev property.

Prod workspace & Prod property

However there is an issue from my perspective:

I am able to set in Dev Workspace VEC Activity and map this to Prod property which totally do not make any sense (I used to work with different MA tools so have different perspectives)

I thought that setting up Workspaces would disable such an setup .... I am setting this for my customer so I would like to have this as bulletproof as possible ex. somebody by mistake would put VEC activity on a production ...

If I do not choose any property for this VEC activity so which property is choosen when turning on activity?

[Gokul_Agiwal]

Hi @Michael_Soprano  

1 . So what is the practical use-case of Default Workspace? Only functionality - that you can see everything in one place?

default workspaces function as a type of catch-all environment, where anyone who has access to Target will have access to that Organization’s default workspace. It is up to the Administrator to restrict users’ access to the default workspace and instead assign those users to a Workspace that specifically concerns their work. 

2. So in your case - as you're able to set in Dev Workspace VEC Activity and map this to Prod property . 

In this case - you tighten the roles and permission like below 

• Dev workspace can only use Dev property  and 
• Prod workspace can only use Prod property  

Also 

• Assign users to only the Dev workspace, with no access to the Prod workspace or Prod property.

• Use Approver and Editor roles wisely.

• Remove the ability for Dev users to activate activities to Prod.

You can setup this rules from Adobe Admin Console. 

Hope it helps. 

Thanks