Skip to main content

Search

Welcome to the Lumar Knowledge Base

Adobe Analytics Integration

Karolina Machalska

API permissions

To use the Adobe Analytics integration, the connected Adobe identity must be able to queue and retrieve Adobe Analytics reports.
 
The extractor uses the Adobe Analytics 1.4 Reporting API methods:
  • `Report.Queue`
  • `Report.Get`
For OAuth Server-to-Server authentication, we request a token from Adobe IMS with the following scope:
 
`openid,AdobeID,read_organizations,additional_info.job_function,additional_info.projectedProductContext`
 
Note that IMS token scope alone is not sufficient — the Adobe integration must also be assigned to an Adobe Analytics product profile in the Adobe Admin Console that grants access to the target report suite. Without this, report requests will be rejected even if authentication succeeds.
 

 

Report suite access

The integration requires a `reportSuiteId`.

All report requests are made against that specific report suite, so the connected Adobe identity must have access to the configured report suite. If it does not, report queue/retrieval requests will fail.
 

 

Which eVars, Props, and events are collected

The integration does not request Adobe eVars, Props, or custom success events.
It requests the following standard metrics from Adobe Analytics:
  • `visits`
  • `bounces`
  • `entries`
  • `bounceRate`
  • `pageViews`
  • `averagetimespentonpage`
Note that `bounces` and `entries` are requested from Adobe in order to calculate bounce rate on our side — they are not stored directly as output fields.

The data stored in the platform is URL/page-level and includes:
  • Visits
  • Page views
  • Bounce rate
  • Average time on page
The report is also filtered to pages that received traffic from Google (via the `searchEngine` element filter).

 

 

Data access frequency


Data extraction is crawl-triggered. When a crawl runs with the Adobe Analytics integration enabled, we request Adobe Analytics data for the configured report suite and selected date range.

The integration does not continuously monitor Adobe Analytics or access data on a fixed background schedule. Data is accessed only as part of an extraction run.



 

x