Target Properties | Community
Skip to main content
balakrishnad200
balakrishnad200
Level 3
November 4, 2020
Solved

Target Properties

  • November 4, 2020
  • 2 replies
  • 3285 views

Hi Team,

I'm very much beginner to Adobe Target . I have implemented adobe target using Adobe Launch with extension at.js and passing a default global variable sitename in to Target. Now I got a new request asking about to setup a Propertie. I'm confused that I have already done the implementation using launch but what is the need of properties and how it is helpful.

 

Help is highly appreciated!

 

Thanks,

Balakrishna

 

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

    Hi Balakrishna,

     

    Properties are useful when you want to limit users to use Adobe Target on specific domains or applications.

     

    More info can be found here: https://helpx.adobe.com/target/kb/how-to-create-properties-in-adobe-target.html

     

    This works very well with the concept of workspaces and product profiles. More info can be found here:  https://docs.adobe.com/content/help/en/target/using/administer/manage-users/enterprise/property-channel.html

     

    Basically you can for example ensure that somebody with access to Target can only adapt the American website and not the German website. You would then create 2 different workspaces: 

    1. America workspace ===> linked to property A
    2. German workspace ==> linked to property B

    So you would put the property code using your tag manager on the different websites and in the Admin console you link the property to the right workspace. You can then give your users access to the workspaces they need.

     

    A even better guide for beginners can be found here: https://www.pedromonjo.com/2019/01/multi-tenancy-in-adobe-target/

     

    Kind regards,

    Jonas

    2 replies

    J
    Adobe Employee
    JonasvvdAdobe EmployeeAccepted solution
    Adobe Employee
    November 5, 2020

    Hi Balakrishna,

     

    Properties are useful when you want to limit users to use Adobe Target on specific domains or applications.

     

    More info can be found here: https://helpx.adobe.com/target/kb/how-to-create-properties-in-adobe-target.html

     

    This works very well with the concept of workspaces and product profiles. More info can be found here:  https://docs.adobe.com/content/help/en/target/using/administer/manage-users/enterprise/property-channel.html

     

    Basically you can for example ensure that somebody with access to Target can only adapt the American website and not the German website. You would then create 2 different workspaces: 

    1. America workspace ===> linked to property A
    2. German workspace ==> linked to property B

    So you would put the property code using your tag manager on the different websites and in the Admin console you link the property to the right workspace. You can then give your users access to the workspaces they need.

     

    A even better guide for beginners can be found here: https://www.pedromonjo.com/2019/01/multi-tenancy-in-adobe-target/

     

    Kind regards,

    Jonas

      balakrishnad200
      balakrishnad200Author
      Level 3
      November 5, 2020

      Hi Jonas,

       

      Thanks for the response. Can you help me where we should place the code which is generated in the process of Properties Creations? I'm using Adobe Launch as Tag Manager fire/track Target.

      Thanks,

      Balakrishna

      K
      Adobe Employee
      karandhawanAdobe Employee
      Adobe Employee
      November 26, 2020

      @balakrishnad200 By creating Properties for your organization, you are able to establish boundaries around where users can run target Activities.

      More information around properties can be found at:

      https://helpx.adobe.com/in/target/kb/how-to-create-properties-in-adobe-target.html

       

      Regards,

      Karan

        Terms & ConditionsAccessibility statement

        Loading footer...