Is s_account and trackingServer listed in SC admin anywhere? | Community
Skip to main content
andocom
andocom
Level 2
October 16, 2015
Solved

Is s_account and trackingServer listed in SC admin anywhere?

  • October 16, 2015
  • 3 replies
  • 3657 views

Just wondering if the s_account and trackingServer values are listed in the SC control panel anywhere, I believe older previous versions if you went to code manager and downloaded the code it would be included but now it is just generic? I guess the general response would be just to copy it from elsewhere but regardless is there somewhere to get it from the control panel?

    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 jdonley

    Once upon a time, when you went to the Code Manager and downloaded the library, that information was populated within the file.  But it no longer is. Adobe changed it to where the library files you download from the code manager no longer show the information such as s_account, trackingServer or visitorNamespace values. The variables are in the file but they no longer have your rsid/account-specific values: 

    var s_account="[INSERT-REPORT-SUITE-HERE]"
    s.trackingServer="[INSERT-TRACKING-SERVER-HERE]"
    s.trackingServerSecure="[INSERT-TRACKING-SERVER-SECURE-HERE]"
    s.visitorNamespace="[INSERT-VISITOR-NAMESPACE-HERE]"

    Why they removed the actual values I do not know, though I wish they would put it back, or else provide this information in some other reasonable way (like in the Company Settings or Billing). 

    However, you CAN get this information from within the SC interface from other places. 

    s_account is the report suite (rsid) you specify the data to go to. You can find this by going to Admin Tools > Report Suites.  This will list all your report suites, showing the report suite ids (what s_account should be populated with), and the report suite labels. 

    trackingServer, trackingServerSecure and visitorNamespace are a bit trickier to get.  To get them,

    1. go to Tag Management (not Dynamic).  
    2. Click on "Create new container." Choose "TagManager 2.0" and name it whatever you want (this is just a temporary thing).
    3. You should now be on an "Environment Overview" page.  Click on "Create Revision" on the bottom left.
    4. You should now be on an "Edit Container" page. Under "Edit Tags", there is a "Add product or code" dropdown.  Select Adobe Analytics > Site Catalyst.  (there are 2 listed. One says "New" the other doesn't; it doesn't matter which you choose).
    5. You should now have a "New Site Catalyst Tag" popup to enter in some information. If one is not selected, pick any value (rsid) in the "Accounts" list, it doesn't matter. Click on "Add tag" on the bottom right. 
    6. You should now see the code for the tag. In the "Tag Code" section is trackingServer and visitorNamespace popped with your values. trackingServerSecure will be blank - unless Adobe specifically told you otherwise, this should be the same value as trackingServer. 

    You may want to leave this as-is, for a reference. If that is the case, click on the "save and deploy" or "save as draft" on the bottom left. To find it again, go to Tag Management (again, NOT Dynamic), in the container list, click on the "edit" link to the right of the container you created. Then on the environment overview page, in the dev environment click on the "edit" link next to the revision.  Note that Adobe has stated that Tag Manager will be removed by EOY 2014 so you will need to make sure you can't rely on this indefinitely. 

    There's no harm in keeping the Tag Manager container, but if you want to undo what you did above, you can go to Tag Managment (not dynamic) and then in the container list, click on the "delete" link. It will ask you to enter in the name of the container and click on a big red "I understand the risks" button.  

     

    Also note that trackingServer and trackingServerSecure are for Adobe's default 3rd party cookie tracking. If you worked with Adobe to setup 1st party cookie tracking, then these are NOT the values you should use.  Adobe ClientCare should have a record of what those values should be, but whoever on YOUR end that originally setup the SSL certificates and servers for 1st party tracking should know this information, since they need to be maintained on your end. 

    3 replies

    Alexis_Cazes_
    Alexis_Cazes_
    Level 10
    October 16, 2015

    Hi,

     

    s_account is where you list all the report suite ID to which you are going to send the data to :  http://microsite.omniture.com/t2/help/en_US/sc/implement/index.html#saccount

    You can put one or more report suite ID in this variable separated with a comma. The first report suite listed will send a primary server call and each subsequent report suite ID will send a secondary server each. The more report suite you will have listed the more server calls will be sent and therefore the more you will have to pay. Secondary server calls are cheaper that primary server calls.

    You can find the list of all the report suite IDs by going to SiteCatalyst >> click on the STAR >> Admin tools >> Report suite. Here you will find all the report suite ids and the common name that correspond to it. 

     

    s.trackingServer value cannot be found in the code generated via code manager any more. Please contact ClientCare that will provide your the right value (the value will depend whether you are using first party cookie or third party cookie)

     

    Best regards.

     

    Alexis Cazes

    WhoaShekhar
    WhoaShekhar
    Level 10
    October 16, 2015

    Hi There,

    Thank you for reaching out to Adobe Community.

    I am sorry but these values are not available in the control panel. The s_account is the report suite ID and the trackingServer is the sever value usually implemented in s_code.js file which can be found in the s_code.js java-script file.

    Hope this helps!

    Thanks!

    J
    jdonleyAccepted solution
    Level 8
    October 16, 2015

    Once upon a time, when you went to the Code Manager and downloaded the library, that information was populated within the file.  But it no longer is. Adobe changed it to where the library files you download from the code manager no longer show the information such as s_account, trackingServer or visitorNamespace values. The variables are in the file but they no longer have your rsid/account-specific values: 

    var s_account="[INSERT-REPORT-SUITE-HERE]"
    s.trackingServer="[INSERT-TRACKING-SERVER-HERE]"
    s.trackingServerSecure="[INSERT-TRACKING-SERVER-SECURE-HERE]"
    s.visitorNamespace="[INSERT-VISITOR-NAMESPACE-HERE]"

    Why they removed the actual values I do not know, though I wish they would put it back, or else provide this information in some other reasonable way (like in the Company Settings or Billing). 

    However, you CAN get this information from within the SC interface from other places. 

    s_account is the report suite (rsid) you specify the data to go to. You can find this by going to Admin Tools > Report Suites.  This will list all your report suites, showing the report suite ids (what s_account should be populated with), and the report suite labels. 

    trackingServer, trackingServerSecure and visitorNamespace are a bit trickier to get.  To get them,

    1. go to Tag Management (not Dynamic).  
    2. Click on "Create new container." Choose "TagManager 2.0" and name it whatever you want (this is just a temporary thing).
    3. You should now be on an "Environment Overview" page.  Click on "Create Revision" on the bottom left.
    4. You should now be on an "Edit Container" page. Under "Edit Tags", there is a "Add product or code" dropdown.  Select Adobe Analytics > Site Catalyst.  (there are 2 listed. One says "New" the other doesn't; it doesn't matter which you choose).
    5. You should now have a "New Site Catalyst Tag" popup to enter in some information. If one is not selected, pick any value (rsid) in the "Accounts" list, it doesn't matter. Click on "Add tag" on the bottom right. 
    6. You should now see the code for the tag. In the "Tag Code" section is trackingServer and visitorNamespace popped with your values. trackingServerSecure will be blank - unless Adobe specifically told you otherwise, this should be the same value as trackingServer. 

    You may want to leave this as-is, for a reference. If that is the case, click on the "save and deploy" or "save as draft" on the bottom left. To find it again, go to Tag Management (again, NOT Dynamic), in the container list, click on the "edit" link to the right of the container you created. Then on the environment overview page, in the dev environment click on the "edit" link next to the revision.  Note that Adobe has stated that Tag Manager will be removed by EOY 2014 so you will need to make sure you can't rely on this indefinitely. 

    There's no harm in keeping the Tag Manager container, but if you want to undo what you did above, you can go to Tag Managment (not dynamic) and then in the container list, click on the "delete" link. It will ask you to enter in the name of the container and click on a big red "I understand the risks" button.  

     

    Also note that trackingServer and trackingServerSecure are for Adobe's default 3rd party cookie tracking. If you worked with Adobe to setup 1st party cookie tracking, then these are NOT the values you should use.  Adobe ClientCare should have a record of what those values should be, but whoever on YOUR end that originally setup the SSL certificates and servers for 1st party tracking should know this information, since they need to be maintained on your end. 

      Terms & ConditionsAccessibility statement

      Loading footer...