Integrating with Adobe Analytics Data Warehouse (Blog Series)

Blog Series

The intent of this set of blogs is to help developers understand the key aspect of how to integrate with Adobe Analytics through the Data Warehouse reporting environment from a higher level architecture perspective all the way down to api implementation topics. Much of the content is useful for other integration options with Adobe Analytics and as such are consumable stand alone.

List of blogs in this series:

Series Overview

Adobe Analytics is a critical data source for insights into visitor engagement, from web, mobile or off line. This single source of truth can be deeply analyzed and acted upon inside the Adobe Marketing Cloud. It is also important for Adobe customers to be able to use this data in third party systems, either operated by the customer directly or provided by partners. This guide will cover how to implement this integration in the most current approach as of Q2 2015.

The guide walks through the Analytics API side of an integration to extract refined(segmented) data via a highly predictable and controlled interface and make it available in a third system.

The types of integrations possible via this approach include, but are not limited to:

  • Extract Transform and Load (ETL) connectors.
  • Business Intelligence data sourcing.
  • Remarketing in ESPs.

Intended Audience

This Implementation Guide is intended for use by advanced Analytics practitioners or integration specialists who fulfill roles such as developer, architect or consultant. The content covers aspects of Adobe Analytics, explaining the key platform components as well as the specific API usage. It assumes previous experience in at least one programming environment, and competencies in REST/JSON based integrations.

Example Use Case

ETL Connector for Adobe Analytics. An ETL is a common product in most enterprises, from vendors such as Informatica and Pentaho. They are used to connect to a third party system, extract data in that system’s native format, potentially add to, or correct that data set, then transform the data into a second system’s native format and load that data into the second system. The primary end users are integration specialists in the Marketing or IT organization and as such usability and configurability are important factors.

This use case will include the following features:

  • Connection setting dialog: a highly usable UI to get and validate the parameters required to interact with the Adobe Analytics accounts.
  • Report Suite, Segment, Metric and Dimension selectors: Pick lists and validators that side step having to enter complicated technical parameters.
  • Report request and download: Reliable flow control that manages the request life cycle of the actual report generation.

Implementation details:
The latest versions of the Adobe APIs and services will be used to ensure that supportability and longevity of the integration.

The following components are used:

  • Adobe Analytics Enterprise API version 1.4

    • Company API 1.4
    • Report Suite API 1.4
    • Segments API 1.4
    • Reporting API 1.4 (with beta Q2 2015 features for “Data” Warehouse reporting)

Authentication will use the WSSE Headers option. OAuth support, which is the new recommended option does not support some of the system to system cases. When those features are available we will provide an Implementation Guide as an adjunct to this guide. WSSE Header support will be available for many years to come and is fully supported with the 1.4 API.

Examples will be verbose and expansive, covering general REST/JSON requests and also code examples in Java in a subsequent version.

Next blog in the Series:

Must be logged in to comment. now to comment!