Why there is an unspecified line item while checking Page Report in Adobe Analytics

To understand why there is an unspecified line item while checking the Analytics report with Occurrences metric, we need to understand the following definitions and scenarios.

Occurrences higher than Instances: This outcome is expected for conversion variables, as occurrences also includes the number of times the variable was defined (instances).

Instances higher than Occurrences: This outcome is not possible in reporting, as all instances are recorded as occurrences as well.

Occurrences vs. Instances : Occurrences count hits where a dimension item was set or persisted. Instances do not include hits where a dimension item persists.

Occurrences vs. Page views : Occurrences include all hit types, including page view tracking calls ( t() ) and link tracking calls ( tl() ).

The page views metric only includes page view tracking calls, and excludes link tracking calls.

While running page report(OOB) report with metric Occurrences , it is expected to get Unspecified line item because of s.tl() call which happened during the visitor journey even if the s.pageName variable is set explicitly. To overcome this it is recommended to create a custom analytics variable (prop/eVar) to capture page name into it.

Note: Subrelation is synonymous with conversion report breakdown.

Difference Between Google Analytics and Adobe Analytics

It is one of the common question while opting the Web Analytics tool and doing the comparison is very common and first action done by business owners.

Google Analytics

  • Easy Client-Side Implementation using JavaScript
  • Customizable Intuitive dashboards
  • Data sharing is not very easy with other users
  • Works well with data analysis languages like R and Python.
  • CRM integration not possible
  • Free tool for the first 10 million hits, post that about $150,000 (for over 1 billion hits).
  • No dedicated customer support team
  • Free Version is available

    Adobe Analytics (formerly known as SiteCatalyst – Omniture)
  • Implementation is easy but requires some technical assistance and little programming knowledge.
  • Server Side and Client-side implementation is possible
  • Less intuitive in reporting
  • Much easier to share with other users.
  • Highly customizable
  • Market Leader
  • Third-party integration is available through various options
  • 24×7 Dedicated customer support.
  • CRM integration allowed
  • No free version is available
  • Each server call is charged

Google Analytics is good if you don’t have a large analytics and tech team, Adobe works mainly in large digital-first / e-commerce companies with dedicated analytics and tech teams. Adobe Analytics is for serious business and long term business as it is part of Adobe Experience Cloud. Adobe Analytics has a market share of 39% in Housewares/Home Furnishings, 36% in Food/Drug, 39% in Books/Music/ Video, and 41% in Mass Merchants.

What tools/services Digital Analytics Professionals often use?

While tools/services one uses depend on the need and several other factors. I will share a few popular ones often used by Digital Analytics professionals.

  • Web/App Analytics – Google Analytics, Adobe Analytics, GA(App+Web, Firebase)
  • Dynamic Tag Management – Google Tag Manager, Adobe Launch, Tealium, Ensighten
  • Analysis – Excel, SAS
  • Debugging dataLayer – DataLayer Checker, GA Debugger, FB pixel helper
  • Reporting & Visualization – Google Data Studio, Tableau, PowerBI, Tibco Spotfire
  • Product/Event Analytics – Mixpanel, GA(App+Web)
  • Engagement/Marketing Automation – WebEngage, MoEngage
  • App Attribution – Appsflyer, Branch
  • Session Recording – Hotjar, Full Story
  • Marketing warehouse – Google Bigquery
  • Email – Mailchimp, Sendgrid / SES
  • CRM – Hubspot, Salesforce
  • CDP – Segment

To dig deeper into data/Tech

  • API Testing – Postman
  • Data Lake – S3, GCS
  • Data Warehouse – Postgres, Redshift
  • ETL – AWS Glue
  • Querying S3 data lake – Amazon Athena
  • VCS – Git
  • Executing code – Jupyter Notebook(Python), R Studio(R)
  • Hosting Notebooks – Google Colab
  • SQL Client – Dbeaver (connect/query DWH)
  • Editor – VS Code, Sublime T3

In the future, I will share more example, Feel free to comment that which tool you use and why.

What are Data Collection Steps of Adobe Analytics?

  1. A visitor visits a web page that contains the data collection code.
  2. As the page loads, the data collection code sends an image request (called a web beacon) to Adobe data collection servers. The image request contains the data you want to collect about the visitors’s interaction with your website.
  3. Adobe stores the data in report suites. You can log in to access report suite data and generate reports related to visitor activity on your website.

Data collection is very quick and does not noticeably affect page load times. Collected data includes page views that result from clicking the browser Reload or Back buttons. The Javascript code runs even when the page is retrieved from cache.

Processing Order of Adobe Analytics:

What is Adobe Analytics?

It’s the industry-leading solution for applying real-time analytics and detailed segmentation across all of marketing channels. Use it to discover high-value audiences and power customer intelligence for business.

What Adobe Analytics can do?

Reporting provides insights into your traditional web-based channels as well as evolving channels like mobile, video, and social networking. Some examples of marketing reports include:

  1. How many people visit your site
  2. How many of those visitors are unique visitors (counted only once)
  3. How they came to the site (such as whether they followed a link or came there directly)
  4. What keywords visitors used to search site content
  5. How long visitors stayed on a given page or on the entire site
  6. What links visitors clicked, and when they left the site
  7. Which marketing channels are most effective at generating revenue or conversion events
  8. How much time they spent watching a video
  9. Which browsers and devices they used to visit your site

Photoshop Camera “Free”

Meet the camera of your dreams.Adobe Photoshop Camera is now available for free on iOS and Android! With the AI-powered Photoshop Camera, you have access to dozens of lenses, so you can add the best effects to your photos — before you even take the shot!Adobe keep on releasing special edition lenses.

Why should I use HTTPS and how it impact Web Tracking?

HTTPS is an encrypted communication protocol — essentially, a more secure way of browsing the web, since you get a private channel directly between your browser and the web server. That’s why most major sites use it.

If a site’s using HTTPS, you’ll see a little padlock icon in the address field, just as in the screenshot below:

Screenshot of the "secure site" padlock icon

Here are the most common reasons you might want to use HTTPS on your own site:

Faster. One might think that HTTPS would make your site slower, since it takes some time to encrypt and decrypt all data. But a lot of efficiency improvements to HTTP are only available when you use HTTPS. As a result, HTTPS will actually make your site faster for almost all visitors.

Trust. Users find it easier to trust a secure site. While they don’t necessarily know their traffic is encrypted, they do know the little padlock icon means a site cares about their privacy. Tech people will know that any servers between your computer and the web server won’t be able to see the information flowing forth and back, and won’t be able to change it.

Payment security. If you sell anything on your site, users want to know their payment information is secure. HTTPS, and the little padlock, assure that their information travels safely to the web server.

Search Engine Optimization. Many search engines will add a penalty to web sites that don’t use HTTPS, thus making it harder to reach the best spots in search results.

Your good name. Have you noticed that some websites have the text “not secure” next to their address?

That happens when your web browser wants you to know a site is NOT using HTTPS. Browsers want you to think (rightly!) that site owners who can’t be bothered using HTTPS (it’s free in many cases) aren’t worth your time and certainly not your money.

In turn, you don’t want browsers suggesting you might be that kind of shady site owner yourself.

How it impact referrer for Web Analytics tools:

Never Tag for an eVar or Mbox Again,Meet Alloy.js

Over the years, as Adobe has built or acquired new technology and collected lots of JavaScript libraries — AppMeasurement.js, mbox.js, at.js, DIL.js, Visitor.js, just to name a few. Each has its own strengths, features, history, functions, schema, quirks and interdependencies. Although Adobe Experience Platform Launch makes it as easy as possible to manage all these libraries, customers have been asking us for years why we can’t just have one JavaScript tag and library. 

Now meet the new Alloy.js. Adobe worked hard all year to take all the best features of our current libraries and build a new one that supports Adobe Experience Platform, Adobe Analytics, Adobe Audience Manager and Adobe Target. One library and beacon, sent to a single destination, then mapped and sent to all your Adobe solutions server side. And that’s just the beginning.

Alloy is the code name for the Adobe Experience Platform Web SDK. It allows for streaming data into the platform, syncing identities, personalizing content, and more.

For documentation on how to use Alloy, please see the user documentation.

For documentation on how to contribute to Alloy, please see the developer documentation

Adobe Web SDK (alloy.js) FAQ’s

Download