~things that matter~

Category: Adobe Analytics

CSP for Adobe Experience Cloud

There have been quite a few questions from across our Experience Cloud customers on handling CSP for the products, mainly Adobe Analytics and Adobe Target.

If CSP is something you are hearing for the first time, let me simplify: There are some Adobe domain names you should add to a Content Security Policy (CSP) on your website if you use these solutions and have tight security policies.

Allowing these domains lets visitor browsers that access your site make those important calls to Experience Cloud resources that you use.

Our documentation covers CSP recommendations for the various solutions separately. Feel free to review them here and here.

These documents tell you the domains that need to be whitelisted for your website to communicate from a browser. Few things you need to keep in mind:

  • unsafe-inline” can help fix the CSP errors. However, that is UNSAFE 🙂
  • A nonce-based solution would be required for Adobe Launch.
  • Launch must load asynchronously for the recommended approach to work. Technically, if you feel adventurous, you may be able to make a synchronous deployment work equally well. Again, neither a recommendation from Adobe nor would I be responsible should anything break.
  • While Launch would work with the nonce-based solution, you must take care of Adobe Target pre-hiding and flicker control code (outside of Adobe Launch) separately (i.e. allow them somehow).

I feel that is enough instruction for someone who knows what CSP is. You can see some (not-so-elegant) csp demo pages here.
Do look at the CSP HEADERS and/or META Tags, and the custom message I am printing in the developer console, e.g.:

Cross-Device? Yes Please

Wondered what to do when the only approach to connect cross-device behavior was by using a Custom Visitor ID (read login ID), and then your Adobe consultant strongly discouraged doing that?

That legacy approach of using a Custom Visitor ID has been in the crossfire between the legacy way of getting things done and the modern (and more futureproof) approach of connected journeys and activations using ECID.

What’s wrong with the legacy approach – you may ask. Sure, that was a solution built-in with a lot of historical burdens, worked well with Adobe Analytics/Omniture as a standalone product. However, that restricts you from getting the latest and greatest benefits from ECID, the future-looking identity solution that has been and is only going to be more closely integrated with Analytics and the Experience Cloud features.

Here comes CDA – Cross Device Analytics, to give you a view of user behavior across devices should you be able to provide a unique identifier tracked in Analytics. It’s dynamic and can be applied retroactively. You do CDA in a virtual report suite, and mostly do analysis and reporting based on that.

What if I want to connect journey components that do not have a common identifier? Read up about CJA (Customer Journey Analytics).

Get rid of that s.visitorID today!

Some Adobe Analytics magic in PDFs

[Update: 2020-04-04: We now have a productized solution via a client-side PDF rendering engine, DCViewSDK. I have removed the technical details of the custom solution from here.]

Back in South Africa, our customer wondered how some companies claimed to be “magically” tracking what you did inside a PDF document. And they asked why hadn’t Adobe Analytics got something similar; especially Adobe being the PDF pioneer.

The company was interested to understand the consumption of their clients’ PDF brochures and targeting those who reviewed the stock price (page).

Now, ever wondered how it might feel to be able to understand what content inside that beautiful pdf brochure people are looking at?

  • Send a personalized message to a potential customer who read about a new offering in the brochure.
  • Figure out if a piece of info out there may make more sense at a prominent location on the website real estate rather than buried deep within a voluminous pdf.
  • Or even for the designer, is there a piece of content that forced users to zoom in?

The Problem

You are not alone. PDF Analytics or document analytics in a broader sense had been a path rarely traveled. There were not a whole lot of options for accessing a URL or data collection over the internet. That kind of restricted Analytics efforts on downloaded documents.

The Solution

However, as most browsers are now capable of rendering PDF documents, the question becomes simpler. How do we add Adobe Analytics client-side technologies into the content that’s already sitting there, in the browser, in plain HTML?
The answer is a JavaScript-based PDF parsing and rendering engine. Once the PDF document is rendered in the browser and you get access to the DOM, you can very easily deploy Adobe Analytics and the Launch Tag Management Solution. With minimal coding, you can capture the page number and interactions therein: zoom, search, select, copy text, and print to name a few.

The initial solution leveraged a good 3rd-party library for rendering PDFs. However, a lot has changed after that, and we now have a great rendering engine called the View SDK from Adobe. Adobe Analytics integration comes pre-built.
At this point, I would rather suggest you review the widely available documentation and public posts (including this one I wrote) on the topic.

PDF Analytics may soon become the new norm. The great thing is that it can be done in a Non-Destructive way. The plugin is easy to deploy and manage! Please, try it today!

Protected: Client-Side Analytics Vulnerability

This content is password protected. To view it please enter your password below:

Let’s get a Certificate!

Adobe Analytics has always been fun, and thanks to the wide range of complexities in customer implementations, there wasn’t a lot to prepare for the certification exam.

The exam was a piece of cake – and completed in less than half the time.

Feel free to reach out if you need some guidance for writing the exam. I would suggest going through at least one sample implementation (i.e. pick a large organization’s website and use some sort of a browser debugger to understand the code as well as the network calls).

If you have been involved in real implementations, I think you don’t need to prepare. You will appreciate the questions aim to test the skills rather than the memory.

Explored the API Explorer?

API sounded scary? Never again.

Did you know you could use Adobe Analytics API to do almost everything that you do on the UI and other import/export functionalities?

(Hint: You do not need to know programming to start using the APIs.)

Try the Adobe Analytics API Explorer today:

<Broken link automatically removed. Please check back later or contact me.>

Please see the really simple tool-tip instructions and you should be all set. (Basically, you need to be sure what Data Center holds your data.)

Creating a Report Suite via Adobe Analytics API Explorer

Once you think you are on the right path and are getting the right response, go talk to someone who can incorporate this experiment of yours into a production-ready script in whatever language they are comfortable with.

Deepak Ranjan Kar