Table of Contents
This article will show you how to deploy Adobe analytics through Adobe Launch, and do the necessary configuration.
Create A Property
Now let’s create a new Property，Click on “New Property” in the top right corner. Position as shown below:
After clicking, you can see a property setting interface:
- Name is a required parameter, and the name or domain name of the site is generally filled in. Fill in http://www.bbccss.com here.
- Platform type is required. Select the type according to the actual situation. The website selects Web and the APP selects Mobile.
- Domains is a required parameter. You can fill in the top-level domain name directly, no subdomains, paths, protocols, etc.
- ADVANCED OPTIONS check the first and second . The third one only needs to be checked when you need to develop your own extensions. Most are not needed.
- Run rule components in sequence: The execution sequence of Rules is executed in accordance with Order, the smaller the faster the trigger.
- Return an empty string for missing data elements: Data elements with no value return an empty character, which is convenient for debugging.
- Configure for extension development (cannot be modified later): Users develop Extensions.
Save as shown in the above figure. The property you just created can be seen in the property management interface.
Our new property are created.
Library Code Implementation on Website
Adobe Launch Library Code is deployed on the website and then verified.
Implementation on Website
Click on the property name to go to the corresponding Launch management interface. The library we are going to deploy is below the Environments.
Click to enter the Environments：
You can see that there are three types of environments:
- Development is an environment for program development.
- Production is a formal environment for online.
- Staging is the environment for testing.
A Property can only have one Production environment and one Staging environment. But you can create multiple Development environments.
We need to be officially deployed and choose the second one——Production，Click the icon on the right side，As shown in FIG. After clicking, a page will pop up, as shown below:
This is the library that Adobe Launch needs to deploy. You need to deploy this library to the headers of all the pages.
We copy this library，Then log in to the server and find the location of the page you need to deploy.
If you do not have server permissions, please send Library to your development colleagues for deployment.
After saving and exiting, Adobe Launch‘s Library was deployed.
Then check the Adobe Launch library Code in the network in the developer tools of the browser to see if it can load normally.
If the status is 200, it means the loading is normal.
If the status is 404, it means that the loading on the server is unsuccessful. Adobe is using Akamai’s CDN, which may be that the CDN has not been updated. You can click on the code, open it in the browser, and then refresh until you can see the code, which means it has taken effect. Then refresh to see the status, it should be 200.
Configuring the Adobe Analytics Extensions
Go back to adobe Launch and click on Extensions，Click on Catalog to search for Adobe Analytics：
Click to install, then go to the Adobe Analytics Extensions:
There are a lot of places to set up here, we configure them one by one.
Here is where the management library loads and where the data is sent. Mainly the first configuration Manage the library for me. Here is a report suites that indicates that data is sent to this report suites.The place to create reports suites is in Adobe analytics, we need to return to Adobe Analytics to create Report suites.
In Adobe Analytics , Click Admin>Report Suite Manager:
Click Create New>Report Suite,Then there will be a setting interface for Report Suite:
Fill in the actual situation, and then click Create Report Suites at the bottom. It should be noted that the Report Suites ID BBCCSS filled above is needed later.
We are getting the report suites id is BBCCSS, go back to Adobe Analytics Extension in Launch, just fill this out to Production Reports Suites:
Here we only fill out a Production environment Reports Suites, if you are developing and staging separate, then fill in the corresponding Reports Suites.
There is an icon to the right of the filled location, which indicates that some data elements can be selected.
For example, you can save Reports Suites with a constant in a data element and then select that data element with that icon.
There are two optional options below:
- Use Activity Map：After it is turned on, some clicks of the user will be tracked, only clicks with links will be tracked. It’s actually a heat map.
- Make tracker globally accessible：You can opt to “make tracker globally accessible” in your extension configuration. This will create the ‘s’ object at the window scope so you can have other scripts potentially reference the object directly. With this you get the added benefit of future library updates being easier. Having scripts that directly reference the ‘s’ object isn’t something you should plan on leveraging heavily, For example, when using s.doPlugins
Enable EU compliance for Adobe Analytics：When you check the EU Compliance check box, the Tracking Cookie Name field appears. The Tracking Cookie overrides the default tracking cookie name. You can customize the name that Launch uses to track your opt-out status for receiving other cookies. The simple understanding is that you can choose whether to accept cookie tracking for the user, and then write the selected result into the cookie. Adobe Analytics will get it. If it is allowed, continue to load and set the cookie. If it is not allowed, the Adobe Analytics cookie is not. Will be set.
We don’t set it here, because my blog does not yet have a cookie reminder for this. If your website is for a business site in the European Union, then this place must be set.
Character Set：Determines how the image request is encoded. If your implementation or site uses non-ASCII characters, it is important to define character set here. You can select a preset character set or specify a custom character set. Adobe recommends using the same character coding as your site. Typically this value is UTF-8.
Currency Code：Determines the conversion rate to be applied to revenue and currency events. If your site allows visitors to purchase in multiple currencies, setting the currency code ensures the monetary amount is converted and stored correctly.
Tracking Server & SSL Tracking Server：Used for SSL first-party cookie implementations to dictate where the first-party cookie is stored. If you use the Experience Cloud ID Service, Adobe advises against populating this field. The effect of this is that the cookie is placed under the domain name. If you are using third-party cookies, you won’t need to set the tracking server secure variable, you can leave it blank here.
One more thing:.Because of the large amounts of data and clients the Adobe Experience Cloud has, there are several data centers to accommodate each organization. The following are locations where data is sent to and stored: Pacific Northwest, United States，London, UK and Singapore, it will be sent to the subdomains of sc.omtrdc.net or 2o7.net by default.
There are a lot of settings here, but not all of them need to be set in this Extensions.
eVars and Props, these two are custom variables, configured as needed, we do not make special configuration here. So here are just one example:
Move the cursor to the corresponding Report Suite ID and click Edit Settings above:
Open eVars management interface:
Then create an Evers, assuming 100 is created. Then return to Adobe Launch, select eVarsr100 on the left, and select the variables to be passed on the right:
This sets up eVars.
The setting of Props is similar to eVars.
If your site has an obvious hierarchy, you can configure Hierarchy. If the page is such a structure: bbccssc.com/adobe/adobe-analytics/a.html, you need to use Hierarchy. You can use a custom code to judge the URL and return it to the classification. It is stored in a data element and can be directly referenced here.
Create a Custom Code in the data element and name it Hierarchy:
Then the code is as follows:
Extensions can then be set up like this:
Other levels can be handled similarly.
Page Name, this requires the use of data elements. We first need to create a data element to store the Page Name, and then directly reference the data element here.
We are going to create a data element now, Click on Data Elements and click on Add Data Element：
See the following interface:
- Name：Here is the name of the set data element.
- Extensions：Which extensions does this data element depend on?
- Data Element Type：There are many types in it，For example, Constant, Cookie, Page info…We can get a lot of information from here.
- Enable Default Value：Setting a default value ， it is easy to understand.
- Force lowercase value：All letters are lowercase
Storage Duration：How long is the life cycle of this data element?
These are the data elements that must be set and are now returned to the Adobe Analytics Extensions:
Click on the small icon to select the corresponding data element：
The final effect is as follows:
You can also input two% directly, and then input the name of the data element between the two %, the effect is the same.
This part ends here.
- Enable ClickMap：enable Activity map data collection. Click the checkbox to enable Activity map tracking. It is turned on by default.
- Track download links：enable automatic download link tracking. It is turned on by default.
- Track outbound links：Follow the jump link.
- Keep URL Parameters：Preserves query strings.
The default is fine.
Visitor ID :The s.visitorID variable is a string that contains a custom unique identifier for the visitor. Adobe advises against using this variable. Use the Adobe Experience Cloud Identity Service instead.
Visitor Namespace: This variable is retired. Use trackingServer instead. If you apply to Adobe to collect data with a specific second-level domain name and trackingServer is not set, cookies are stored under bcs112.2o7.net s.visitorNameSpace = “bcs”.
Domain Periods: The domain on which the Analytics cookie s_cc and s_sq are set by determining the number of periods in the domain of the page URL. This variable is also used by some plug-ins in determining the correct domain to set the plug-in’s cookie.
First-party Domain Periods: The fpCookieDomainPeriods variable helps AppMeasurement determine where Analytics cookies are set by calling out that the domain suffix has an extra period in it. This variable allows AppMeasurement to accommodate the extra period in the domain suffix and set cookies in the right location. Generally do not need to be set, the default is 2.
- For domains like example.com or http://www.example.com , this variable does not need to be set. If needed, you can set this variable to “2” .
- For domains like example.co.uk or http://www.example.co.jp , set this variable to “3” .
cookieLifetime: The validity period of the cookie, This variable impacts unique visitor counts and attribution. Use caution when setting this variable. There are four options:
- Default : Cookie expires after 2 years.
- None : AppMeasurement does not set cookies.
- Session : Cookie expires at the end of the visitor’s session.
- Seconds : Cookie expires after the specified number of seconds have elapsed. For example, setting this dropdown to Seconds and placing 86400 into the custom field forces cookies to expire after exactly 24 hours.
Write secure cookies: https is used for content transmission, which is more secure. This setting applies to both visitor ID cookies set by AppMeasurement, and cookies you set using the Util.CookieWrite() method. It requires AppMeasurement 2.18.0 or higher. If all resources on your website are enabled using https, do not enable them if they are not.
Here we only set cookieLifetime to default. Effect after setting:
CONFIGURE TRACKER USING CUSTOM CODE
Before using this, you need to check Make tracker globally accessible in LIBRARY MANAGEMENT.
No settings are currently required.
ADOBE AUDIENCE MANAGER
Here is to set up Adobe Audience Manager, we do not set up Adobe Audience Manager here, so there is no need to set it.
Finally save the settings on the Adobe Analytics Extensions.
The role of Rules is to set the conditions and where to send the data. Create a Rules, the settings interface is as follows:
If indicates a condition, then indicates execution, and the action is executed when the condition is satisfied.
Named Adobe Analytics Base Tracking Code。
Click to add EVENTS:
Save as follows:
Create an ACTIONS and save it as follows：
Add one more ACTIONS and add the location as shown:
Save as follows:
The final effect after the rules are set:
The Rules are set up and the next step is to publish.
Publishing is a cumbersome process due to the complexity of Adobe Launch permissions. Click Add New Library：
Customize the naming, then select the development environment, and finally click Add All Changed Resources
Once you’re done, click Save &Build for Development in the top right corner.You will see a library under Development:
The next step is to submit to the test，Click the down corner in the upper right corner of the library and click Submit For Approval.
Click on Build for Staging：
Click on Approve for Publishing：
The final step is to confirm the publish：
We tested it with Ghostery and saw that there is a label for Adobe Analytics.
Next open the Adobe Experience Cloud Debugger to test:
Looks like no problem, finally look at the Adobe Analytics Real-Time reports：
We are done.