Update time: March 19, 2026
This guide walks you through how to implement Adobe Analytics using Adobe Launch (Tags) step by step.
If you’re interested in a server-side setup, check out: Implementation Adobe Analytics Via Web SDK
Before getting started, make sure you have the necessary permissions for both Adobe Launch (Tags) and Adobe Analytics.
Let’s dive in.
Step 1: Create a Property in Adobe Launch
In Adobe Launch，click「Tags」——「New Property」, then set up as follows:
- Name：Usually your website name or domain (e.g., http://www.bbccss.com)
- Platform：Web for websites, Mobile for apps
- Domains：Enter your root domain only (no subdomains, paths, or protocols)
- ADVANCED OPTIONS
- Run rule components in sequence: Ensures rules execute in order (lower order = earlier execution)
- Return an empty string for missing data elements: Helps with debugging
- Configure for extension development (cannot be modified later): Only needed if you’re building custom extensions
Save your property.
Step 2: Install the Adobe Launch Library and Verify It
Next, install the Adobe Launch library on your website and verify that it’s working correctly.
Go to your newly created Property and click 「Environment」:
You’ll see three environment types:
- Development – used for implementation and testing during development
- Staging – used for QA and pre-production validation
- Production – the live environment for your website
Each Property can have one Production and one Staging environment, but you can create multiple Development environments.
Since we’re deploying to the live site, select Production. Click the icon on the right—this will open a panel with the embed code.
This is the Adobe Launch library you need to install. Place this code in the <head> section of all pages on your site.
Copy the library code, then log in to your server and add it to the appropriate template or page location.
Once saved and published, the Adobe Launch library is deployed.
For the library to take effect, you must publish a version in Adobe Launch. Without publishing, the code won’t load even if it’s installed on the site.
Open your browser’s Developer Tools and check the Network tab to confirm that the Adobe Launch library is loading correctly.
- Status 200 → The library loaded successfully
- Status 404 → The library failed to load
If you see a 404 error, it may be due to CDN propagation. Adobe Launch uses the Akamai CDN, so updates can take a short time to go live.
You can click the library URL, open it in a new tab, and refresh until the file loads. Once it does, go back and refresh your site—the status should return 200, indicating everything is working as expected.
Step 3: Create a Report Suite
In Adobe Analytics, Click 「Admin」——「Report Suite Manager」——「Create New」——「Report Suite」to set up a new report suite.
Configure the basic settings such as Report Suite ID, Name, Time Zone, and Currency based on your business requirements.
Once created, make sure to note down the Report Suite ID, as it will be required for the subsequent implementation steps.
Step 4: Install Adobe Analytics Extension
In Adobe Launch，click「Extensions」——「Catalog」，then search for “Adobe Analytics”
Click 「install」, and once the installation is complete, open the Adobe Analytics extension settings.
You’ll notice there are quite a few configuration options available. Don’t worry—we’ll walk through them step by step.
LIBRARY MANAGEMENT
This section controls how the Adobe Analytics library is managed and where your data is sent.
For most implementations, you’ll use the default option: “Manage the library for me.”
Next, configure the Report Suite ID, which determines where your data will be collected.
In our example, we created a Report Suite with the ID BBCCSS in the previous step. Enter this value in the Production Report Suites field, like this:
If you’re using separate environments (e.g., Development and Staging), you should also enter the corresponding Report Suite IDs for those environments.
There are two optional configurations below:
- Use Activity Map：When enabled, this tracks user click interactions on links. It provides a visual click heatmap, helping you understand which elements users engage with most.
- Make tracker globally accessible：Enabling this option exposes the
sobject on the globalwindowscope, allowing other scripts to reference it directly. This can be useful in specific cases (e.g., usings.doPluginsor custom scripts), and it also makes future library updates easier. However, it’s generally not recommended to rely heavily on direct access to thesobject unless you have a clear use case.
GENERAL
- Character Set： Typically set this to UTF-8, which is the standard for most modern websites.
- Currency Code：If you run an e-commerce site, select the currency your business uses (e.g., USD, EUR, JPY).
- Tracking Server & SSL Tracking Server：You can leave these fields blank to use Adobe’s default third-party domains. In this case, data will be sent to domains like sc.omtrdc.net or 2o7.net. If you prefer to use a first-party domain (CNAME), you’ll need to work with Adobe to set it up. Once configured, you can update these fields to your custom tracking domain.
- Enable EU compliance for Adobe Analytics：Leave this unchecked unless you have specific compliance requirements that require it.
- Collect high entropy user-agent client hints: Enable this option. Client Hints are gradually replacing the traditional User-Agent string as a more reliable and privacy-friendly source of device information.
GLOBAL VARIABLES
The main settings are eVars and Props, and basic page information (ADDITIONAL SETTINGS).
Please ignore eVars and Props for now; our focus is on ADDITIONAL SETTINGS.
These are all basic tracking variables. Let’s use Page Name as an example to walk through the setup process.
In Adobe Launch，click「 Data Elements」——「Add Data Element」，then set up as follows：
|
Name
|
Extension
|
DataElement Type
|
Check
|
StorageDuration
|
Attribute
|
|---|---|---|---|---|---|
|
PageURL
|
Core
|
PageInfo
|
Forcelowercasevalue
|
PageView
|
URL
|
|
Server
|
Core
|
PageInfo
|
Forcelowercasevalue
|
PageView
|
Hostname
|
|
Channel
|
Core
|
VisitorBehavior
|
Forcelowercasevalue
|
Session
|
TrafficSource
|
|
Referral
|
Core
|
PageInfo
|
Forcelowercasevalue
|
PageView
|
Referral
|
Once your Data Elements are set up, go back to the Adobe Analytics extension.
Click the Data Element picker icon to select the appropriate Data Element for each field.
The final effect is as follows:
Alternatively, you can manually reference a Data Element by typing it in this format %Data Element Name%
Both methods work the same way.
LINK TRACKING
- Enable ClickMap：Turns on Activity Map data collection. Check this option to enable Activity Map tracking (enabled by default).
- Track download links：Automatically tracks download link clicks (enabled by default).
- Track outbound links：Tracks clicks on links that navigate users away from your site.
- Keep URL Parameters：Preserves query string parameters in tracked URLs.
The default settings are generally sufficient for most implementations.
COOKIES
For this setup, we only configure:
- cookieLifetime = Default
- Visitor ID :The s.visitorID variable is used to store a custom unique identifier for each visitor. However, Adobe does not recommend using this variable. Instead, you should use the Adobe Experience Cloud Identity Service.
- Visitor Namespace: This variable is deprecated. You should use trackingServer instead.
- Domain Periods:This setting determines where Analytics cookies (such as s_cc and s_sq) are set by counting the number of periods in the page’s domain. It is also used by some plug-ins to correctly determine the cookie domain.
- First-party Domain Periods: The fpCookieDomainPeriods variable helps AppMeasurement correctly set cookies when the domain includes an additional suffix level. In most cases, you do not need to configure this (default value is 2).
- For domains like
example.comorwww.example.com→ no change needed (use 2) - For domains like
example.co.ukorwww.example.co.jp→ set to 3
- For domains like
- cookieLifetime: This setting defines how long Analytics cookies persist. It directly impacts unique visitor counts and attribution, so configure it carefully.
- Default : Cookie expires after 2 years.
- None : AppMeasurement does not set cookies.
- Session : Cookie expires at the end of the visitor’s session.
- Seconds : Cookies expire after a specified number of seconds
- Write secure cookies: This option ensures cookies are only transmitted over HTTPS, improving security.
CONFIGURE TRACKER USING CUSTOM CODE
If you want to use custom JavaScript, you can add it here.
Before doing so, make sure “Make tracker globally accessible” is enabled in Library Management.
No additional configuration is needed at this stage.
ADOBE AUDIENCE MANAGER
This section is for setting up Adobe Audience Manager. Since we are not using Adobe Audience Manager, you can leave it unset.
Finally, save your changes in the Adobe Analytics Extension.
Step 4: Configure Rules
In Adobe Launch，click 「Rules」——「Add Rule」，named “Adobe Analytics Base Tracking Code”.
EVENTS
Configure EVENTS as follows:
ACTIONS
The configuration in Action 1 is:
The configuration in Action 2 is:
The final effect after the rules are set:
The Rules are set up and the next step is to publish.
Step 6: Publish & Test
Publishing can feel a bit cumbersome due to the complexity of Adobe Launch permissions. To get started, click Add New Library.：
Give your library a clear name, select the appropriate development environment, and then click Add All Changed Resources.
Once everything is set, click Save & Build for Development in the top-right corner. You should now see the library listed under the Development environment.
Next, visit your website and use theAdobe Experience Platform Debugger to validate your implementation.
If everything looks good, you can also verify the data in Adobe Analytics Real-Time reports.
We are done.
