Table of Contents
In this section, we will analyze how GM uses Adobe Launch. Through analysis, we can know which configurations GM has made and which are problematic.
We will use this tool in this section: Launch Library Parser, which has been introduced at Adobe Launch detection tool: Launch Library Parser.
Launch Library Parser is a development tool developed by Urs Boller. Thanks a lot to Urs Boller for developing this tool.
GM’s website: https://www.gm.com/
First let’s look at the loading and data sending of the code:
From this we can know that GM uses Adobe Launch and deployed AAM.
In fact, you can get other information from the console, but we can get more detailed information through the Launch Library Parser, so we won’t take a closer look at the console information here.
Then, take a look at cookies:
From the cookie, you can know that there are Experience Cloud Id and Adobe audience manager.
Finally take a look at the source code:
The Adobe Launch library code is deployed in front of the head. This is no problem. It uses the Akamai method. Finally, I saw that some resources include DAM. This is estimated to be the Adobe Experience Manager product.
Through the above page check, we can know which Adobe products used by GM: Adobe Launch, Adobe Analytics, Adobe Audience Manager, Adobe Experience Manager.
You can also know that the deployment location of Adobe Launch Library Code is correct.
Tool Detection-Launch Library Parser
The detection method is very simple, just copy the Adobe Launch library code into it:
This tool is to parse this js. In fact, you can directly look at the source code of this js, and you can also interpret some information, but it is more troublesome. It is much more convenient to look at the parsed directly.
After parsing, there will be many reports, these reports are very useful, let’s look at each one:
Quality Check Result: 85%
Quality Check Result: Only 85%, the configuration must be redundant or wrong.
Basic library information
You can know the organization ID, environment, and when the last version will be released.
The last version was almost 5 months ago, and GM hasn’t used this tool for a long time.
Library checks & Extension checks
The prototype and triangle indicate that there is something wrong, such as Library is older than 90 days, maybe it’s time for an update, because it has not been used for five months, and some Extensions have been updated during this period. Obviously, GM is not updated to the latest version of.
It can be known that GM’s Adobe Launch is configured with 3 Extensions, 19 data elements, and 16 rules.
Click on EXTENSIONS, we can know which three EXTENSIONS are deployed, namely core, Adobe analytics and Experience Cloud ID Service.
Click Adobe Analytics directly, there will be a lot of configuration information on the right side, these are Adobe Analytics Extensions configuration information, you can imitate this configuration.
Let’s take a look at what configuration the Adobe Analytics Extensions do:
customSetup indicates that there is a custom code, so be sure to enable scopeTrackerGlobally. You can see that the scopeTrackerGlobally setting is true, which means that it is enabled.
Looking at the custom code is to get Campaign information, there are cmp, cid, ppc, evar25, eVar25, evar36, eVar36, a lot of information.
The development environment and the staging environment are the same gmgcf-quantum-dev
The others are some checked information. You can see that some information is not set, such as page name, page url, channel, etc. These can be set on the Adobe Analytics Extensions to reduce hit calls.
Click directly on DATAELEMENTS:
You can see digitalData.pageInfo.pageName. Many of GM’s data elements are passed through this form, indicating that the values of these data elements are passed through the data layer. In fact, some elements are built-in and can be used directly. There is no need to use the data layer.
If individual data elements are not available, consider using a data layer.
Click on rule directly
On the right is the configuration of each rule, events conditions, actions.
What is more interesting is that actions are all in the order of Set Variables, Send Beacon, and Clear Variables. Clear Variables are not necessarily required. If the data element used is of type none, This should prevent the previous page view events from cascading to the next call. So you need to use clear variables.For example, when I set the data element to select none, I will select pageview, session, and visitor according to the life cycle of the data element, so there is no need to clear the variable.
Set Variables, Send Beacon, and Clear Variables can be clicked to open, you can see the specific configuration inside, you can imitate its
This is mainly to visualize the relationship between Extensions, Data Elements and Rules.
RULES: all rules
Most of the tracking is click.
VARIABLES: : ALL items
You can know what data elements are set for each eVar, Props, and events.
EXTENSIONS: ALL extensions
Adobe launch has not been updated for too long;
Many data elements can use the built-in, there is no need to use the data layer;
When configuring rules, clear variables are not unnecessary and should be selected according to the actual situation;
Some settings of Adobe analytics Extensions are still missing;