Expand my Community achievements bar.

Join us for the next Community Q&A Coffee Break on Tuesday April 23, 2024 with Eric Matisoff, Principal Evangelist, Analytics & Data Science, who will join us to discuss all the big news and announcements from Summit 2024!
SOLVED

Analytics account details.

Avatar

Level 2

We are about migrate our current analytics account to Adobe analytics account , please let me know where and how to find below details .

trackingServer: "INSERT-TRACKING-SERVER-HERE", // same as s.trackingServer

trackingServerSecure: "INSERT-SECURE-TRACKING-SERVER-HERE", // same as s.trackingServerSecure

account="INSERT-RSID-HERE"

visitorNamespace = "INSERT-NAMESPACE-HERE" // If you are not using CNAME, DO NOT include these variables

visitor = Visitor.getInstance("INSERT-MCORG-ID-HERE")

marketingCloudServer: "INSERT-TRACKING-SERVER-HERE",

marketingCloudServerSecure: "INSERT-SECURE-TRACKING-SERVER-HERE" // same as s.trackingServerSecure

thanks in advance.

Regards,

Shiv

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Adobe documentation is a bit lacking to be honest which is a shame:

Correctly populate the trackingServer and trackingServerSecure variable

trackingServer: "INSERT-TRACKING-SERVER-HERE", // same as s.trackingServer

trackingServerSecure: "INSERT-SECURE-TRACKING-SERVER-HERE", // same as s.trackingServerSecure

account="INSERT-RSID-HERE"

visitorNamespace = "INSERT-NAMESPACE-HERE" // If you are not using CNAME, DO NOT include these variables

visitor = Visitor.getInstance("INSERT-MCORG-ID-HERE")

marketingCloudServer: "INSERT-TRACKING-SERVER-HERE",

marketingCloudServerSecure: "INSERT-SECURE-TRACKING-SERVER-HERE" // same as s.trackingServerSecure

Ok let me try to help you:

  • You most likely tracking to implement Visitor ID services first so check the documentation
    • Implementation Guides
    • You mentioned that you doing a brand new implementation so I will walk you through the servers to use
  • You should use the Regional Data Collection servers nowadays: Transition to Regional Data Collection
  • It is unlikely you will need First Party Cookie as VIsitor ID services AMCV_ cookie is set on the domain as First cookie by default and if you check the doc you should have same mid served on all of your domains as long you are using same Adobe ORg ID and demdex cookie is accepted. They is other ways to obtain same cookie if demdex cookie is not accepted but it is another matter all together.

so for tracking Server:

  • For best performance it is advised to use an RDC tracking server. This should decrease the response time from Adobe Servers. If you are using a tracking server that uses 2o7.net then it is advise to use the corresponding RDC server.
  • All report suites created in 2014 onwards are globally unique, meaning Adobe's servers can route traffic to the correct location without a data center designation. All report suites created or migrated to Singapore or Pacific Northwest are guaranteed to be globally unique, making sc.omtrdc.net always valide.
  • So use sc.omtrdc.net

For namespace:

Data collection requires a unique subdomain to keep visitor data separate across Adobe Marketing Cloud customers. It is prefixed to the data center address, and is generally your Adobe Analytics login company name with all spaces removed. You can technically use whatever subdomain you'd like, however it is highly recommended to be specific enough that:

  • No other Adobe Marketing Cloud customer would use it.
  • You are consistent with the subdomain across all report suites, especially if your organization uses a global report suite.

So the final trackin server should look like as follow: [NAMESPACE].sc.omtrdc.net

For account: this is the report suite ID that you used when you used when you created your report suite ID. Can be found under ADMIN >> Report suites in Adobe Analytics

trackingServer: [NAMESPACE].sc.omtrdc.net

trackingServerSecure:no need

account="[Report suite ID that you can find under Admin >> Report suites]"

visitorNamespace = "Whatever you see fit"

marketingCloudServer: "[NAMESPACE].sc.omtrdc.net",

marketingCloudServerSecure:no need

View solution in original post

4 Replies

Avatar

Level 5

Hi Shiv

You may want to reach out your account manager or customer care to get support on migration.

Support delegates can get assisted support via:

In-Product:

  1. Sign in to Adobe Analytics.
  2. Navigate to Help > Customer Care.
Phone: 1-800-497-0335 (US & Canada).Get phone numbers for other regions.Email:
  1. Include case details to open a ticket via email.
  2. Send your case to customercare@adobe.com.

Thanks,

Ramesh

Avatar

Correct answer by
Community Advisor

Adobe documentation is a bit lacking to be honest which is a shame:

Correctly populate the trackingServer and trackingServerSecure variable

trackingServer: "INSERT-TRACKING-SERVER-HERE", // same as s.trackingServer

trackingServerSecure: "INSERT-SECURE-TRACKING-SERVER-HERE", // same as s.trackingServerSecure

account="INSERT-RSID-HERE"

visitorNamespace = "INSERT-NAMESPACE-HERE" // If you are not using CNAME, DO NOT include these variables

visitor = Visitor.getInstance("INSERT-MCORG-ID-HERE")

marketingCloudServer: "INSERT-TRACKING-SERVER-HERE",

marketingCloudServerSecure: "INSERT-SECURE-TRACKING-SERVER-HERE" // same as s.trackingServerSecure

Ok let me try to help you:

  • You most likely tracking to implement Visitor ID services first so check the documentation
    • Implementation Guides
    • You mentioned that you doing a brand new implementation so I will walk you through the servers to use
  • You should use the Regional Data Collection servers nowadays: Transition to Regional Data Collection
  • It is unlikely you will need First Party Cookie as VIsitor ID services AMCV_ cookie is set on the domain as First cookie by default and if you check the doc you should have same mid served on all of your domains as long you are using same Adobe ORg ID and demdex cookie is accepted. They is other ways to obtain same cookie if demdex cookie is not accepted but it is another matter all together.

so for tracking Server:

  • For best performance it is advised to use an RDC tracking server. This should decrease the response time from Adobe Servers. If you are using a tracking server that uses 2o7.net then it is advise to use the corresponding RDC server.
  • All report suites created in 2014 onwards are globally unique, meaning Adobe's servers can route traffic to the correct location without a data center designation. All report suites created or migrated to Singapore or Pacific Northwest are guaranteed to be globally unique, making sc.omtrdc.net always valide.
  • So use sc.omtrdc.net

For namespace:

Data collection requires a unique subdomain to keep visitor data separate across Adobe Marketing Cloud customers. It is prefixed to the data center address, and is generally your Adobe Analytics login company name with all spaces removed. You can technically use whatever subdomain you'd like, however it is highly recommended to be specific enough that:

  • No other Adobe Marketing Cloud customer would use it.
  • You are consistent with the subdomain across all report suites, especially if your organization uses a global report suite.

So the final trackin server should look like as follow: [NAMESPACE].sc.omtrdc.net

For account: this is the report suite ID that you used when you used when you created your report suite ID. Can be found under ADMIN >> Report suites in Adobe Analytics

trackingServer: [NAMESPACE].sc.omtrdc.net

trackingServerSecure:no need

account="[Report suite ID that you can find under Admin >> Report suites]"

visitorNamespace = "Whatever you see fit"

marketingCloudServer: "[NAMESPACE].sc.omtrdc.net",

marketingCloudServerSecure:no need

Avatar

Level 2

Thanks a lot Alexis on this.

I want one more thing to get clarified and seeking your advise for the same.

Actually we have a existing report suite in one of the account and we do created a new report suite in some other account ,So now i want to migrate my historical data(data transition) from existing report suite to new one. please enlighten on this what could be the best approach for smooth data transition as this activity needs to performed in production as well.

FYI - both the report suite exist in different account and belongs to adobe analytics.

Avatar

Community Advisor

I know it is a bit late but it is not possible to migrate data from one report suite to another one.

The only possible solution would be to contact Adobe and adobe engineering might be able to do it but it will require a fee for sure