Author: Shamshul
How To mitigate the impact of ITP 2.1, ITP 2.2, and future ITP releases-Adobe Analytics
ITP 2.1 | Capped client-side cookies that are placed on the browser using the document.cookie API to a seven-day expiry. Released February 21, 2019. |
ITP 2.2 | Drastically reduced the seven-day expiry cap to one day. Released April 24, 2019. |
To mitigate the impact of ITP 2.1, ITP 2.2, and future ITP releases, complete the following tasks:
- Deploy the Experience Cloud ID (ECID) library to your pages.
The ECID library enables the people identification framework for Experience Cloud Core solutions. The ECID library allows you to identify same site visitors and their data in different Experience Cloud solutions by assigning persistent and unique identifiers. The ECID library will be updated frequently to help you mitigate any ITP-related changes that impact your implementation.
For ITP 2.1 and ITP 2.2, ECID library 4.3.0+ must be utilized for mitigation.
Check the link too: https://docs.adobe.com/content/help/en/id-service/using/reference/ecid-library-methods.html
2. Use Adobe’s CNAME and Enroll in Adobe Analytics’ Managed Certificate Program.
After installing the ECID library 4.3.0+, you can leverage Adobe Analytics’ CNAME and Managed Certificate Program. This program lets you implement a first-party certificate for first-party cookies at no charge. Leveraging CNAME will help customers mitigate the impact of ITP 2.1 and ITP 2.2.
If you are not leveraging CNAME, you can start the process by talking with your account representative and enrolling in the Adobe Managed Certificate Program .
Classify Tracking Code using Rule Builder
Well explained on Guide to Using UTM Parameters in Adobe Analytics
I used following code to capture Tracking code:
s.usePlugins=true;
s.doPlugins=function(s) {
if(s.Util.getQueryParam(‘utm_medium’)){
s.campaign=s.Util.getQueryParam(‘utm_medium’)+”:”+s.Util.getQueryParam(‘utm_source’)+”:”+s.Util.getQueryParam(‘utm_campaign’)+”:”+s.Util.getQueryParam(‘utm_content’)+”:”+s.Util.getQueryParam(‘utm_term’);
}
s.campaign=s.getValOnce(s.campaign,’s_campaign’,0);
}
Then I set up the calssification in Analytics
Below is the screen shot:

Then under classification rule builder I did following setup using regx ^(.+)\:(.+)\:(.+)\:(.+)\:(.+)$
Sample value:
search:google:christmas:article:gifts

The above regex will not accept value if any one of the field is missing like search:google:christmas::gifts or :google:christmas::gifts
To fix this we have to use : ^(.*)\:(.*)\:(.*)\:(.*)\:(.*)$


For reference check Adobe Doc
For testing, you can use https://rubular.com/
How To Set up a local web-server on your computer
You will need to host a sample website for the hands-on lab. The sample PHP web pages will be provided during the session.
You can host the site in your local server (localhost) if you already have one configured on your computer. You can also use an online web-host if you have access to. Skip this Exercise in that case.
The following steps will guide you install a local web-server on your computer.
Objective:
Successfully Download and install a local-server software. Verify access to their default home page in your web browser.
Steps:
We will use XAMPP in this example. XAMPP is a very easy to install Apache Distribution of Linux, Solaris, Windows, and Mac OS X. The package includes the Apache web server, MySQL, PHP, Perl, an FTP server and phpMyAdmin. With that, you can have fun with your own website/scripting experiments in future with XAMPP on your machine.
(Alternatively, you can choose to install any popular package such as LAMP, WAMP, MAMP etc.)
- Download latest XAMPP software from: https://www.apachefriends.org/download.html
- Install with default settings. Just notice the directory where it’s getting installed (e.g. C:\XAMPP)
- After install, open the “XAMPP Control” app in your computer. Then start “Apache”:

- Apache server should start with default ports: 80/443:

That’s your local web-server switched On!
- Troubleshooting: If Apache could not start on default ports, probably something (e.g. IIS, Skype etc.) was blocking/using the default ports.
Consider changing the ports configured for Apache (try using some other ports e.g. 88 and 488). You can do that by clicking on “Config” and then editing and saving the files: httpd.conf and httpd-ssl.conf:

In those configuration files, find the line that mentions Listening on the ports (80 in httpd.conf and 443 in httpd-ssl.conf) and change those numbers (you can try 88 and 444 respectively).


After you save those two configuration files. Re-start with Step#3 (Starting Apache)
- After a successful start of Apache, in your browser, type “localhost” as the URL and proceed. If you had used a port other than the default, you will need to add the port number to the URL separated by colon e.g. “localhost:88“
You should be redirected to XAMPP Dashboard and see a welcome page like this:

(with default settings)

(with HTTP port changed to 88)
- Locate your XAMPP install directory in your computer. You should see a sub-directory “htdocs“:

Your websites and web pages usually reside in that
sub-directory. We will come back to this during the Lab.
How To Cross Verify Marketing Channel through Data Feed
1.Pull following column through data feed:
exclude_hit
va_closer_detail
va_closer_id
va_detail
va_finder_detail
va_finder_id
va_instance_event
va_master_id
va_new_engagement
2.Apply filter on column exclude_hit=0
3.Apply filter on column va_new_engagement=1
4.Apply filter on column va_closer_id=channel ID
Notice: The count should match to reports
Adobe Analytics Interview Questions
- Difference b/w prop and evar
- What is the pathing report
- Explain segment comparison
- Explain the container in segments
- What is the use of calculated metric
- Analysis Workspace
- Visitor and visit concept
- Mid , experience cloud ID services
- Merchandizing evar
- Image request parsing
- Getqueryparam
- Data collection query parameters
- What is DTM?
- In how many ways you can implement analytics
- Difference b/w Google Analytics and Adobe Analytics
- Export and import tools
- Data sources
- Classification
- Processing rule
- Processing order
- Marketing channel
- Internal URL filter
- Reason of “other” in pages report
- S.t and s.tl implementation and syntax
- Difference b/w s.t and s.tl
- What is data range
- Virtual report suite
- Menu customization
- Experience cloud
- Report suite and rollup
- Multi suite tagging
- Difference b/w rollup and multisuite tagging
- What is the primary and secondary server call
- Key metrics
- First part cookie
- Tracking code
- Product string
- Plugin
- Visitor id identification method
- Data feed understanding
- Scenario-Based time spent on page.
- Scenario based segment configuration questions.
- Prop can correlate with (only prop or traffic sources)
- The difference in multi tagging and rollup report suite.
- Options available when on first screen of Report builder wizard when creating a request.
- who can create and share calculated metrics
- Total appears in report represents?
- Maximum number of line items that can appear on screen while running a report (answer:200)
- Recommended format to download or schedule file for 501 line items (csv)
- Data extract limitation (available only in csv format)
- when an alert is set on percentage change how it works
- Publishing list benefit
- How a non-admin user can share a report
- Definition of Report Acceleration
- variable character limit
- How total would be affected if we apply an advance filter on the reports
- what changes can be applied to a dashboard in one go which will affect all the reportlets
- If notes are added in any report who can view those notes
- definition of copy me, on menu, options available for dashboard
- When running page views or any other metrics report which are the default column that appears in report (4 week prior and 52 weeks prior).
Using Postman to Make Adobe Analytics 2.0 API Requests
Impression data to Audience Manager (AAM)
Is Ad Cloud able to pass display media exposure back to AA, and then have this forwarded via Server
Advertising Cloud is able to pass data in Analytics via Adobe server to server integration for Adobe to understand if the ad impacted the consumer to visit the website. For example, Adobe can capture view-through data and understand if someone saw the display ad (delivered via Advertising Cloud) and then went to the advertisers’ web page a few days later (via the Analytics pixel on the web-page), we can capture that as a view-through conversion and say the ad contributed to the person visiting the website. From there, Analytics can understand other ways users are interacting with the web page (bounce rate, page views etc.) to help create audiences to re-target, or build look-a-likes (via pushing Analytics segments into Audience Manager). Additionally, we can create audiences via Analytics data and push those audience segments into Audience Manager through
You have the option to push audiences straight from Analytics into Advertising Cloud to target, or can push the audiences into Audience Manager for organization and then push from AAM to Ad Cloud to target.
The benefits of using all three products together are:
– Capture audience and website behavior and use it to build segments of in-market intenders
– Create a single view of the customer form your unified data, enriched and added data
– Deliver a personalized ad to an audience at the right time whenever they are in an authentic and relevant experience
– Continue to personalize through analysis, reporting & optimization
Mobile carrier reports and it’s behavior in Adobe Analytics
I am sure most of you must be aware of the “Mobile carrier” reports and it’s behavior in site catalyst.
Still, I would like to share a few inputs which I came across, and thought some people might not be aware of the same.
It’s a Visitor’s profile report that comes under Technology i.e Visitor’s profile à Technology à Mobile carrier
It helps identifying the traffic ( mobile visitors) by carrier i.e the mobile operators and shows the wireless service provider.
The third party : NetAcquity is the one which sources the data for us.
It is calculated as taking the unique key calculated by taking the combination of ISP + Domain. Hope this little information may help in understanding.