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