Adobe Analytics¶
Adobe Analytics is an analytics service provided by Adobe Systems Incorporated. It enables the owner to monitor and analyze web traffic and can be used to keep track of user behavior. Adobe Analytics APIs offer limitless ways to integrate your most important customer data into key business processes.
You can configure Denodo to retrieve data from Adobe Analytics by creating JSON data sources and base views in Denodo using the Adobe Analytics APIs.
In order to make this process easier and faster, you have available an Adobe Analytics wizard. You just have to configure a few parameters and click on Import to create into your Denodo server the needed data sources and views to get access to Adobe Analytics.
This wizard configures access to some predefined Adobe Analytics reports and allows users to create base Adobe Analytics reports with the metric and the dimension they prefer in order to create customized reports tailored to their own specifications.
Getting OAuth 2.0 Credentials¶
To get the Adobe Analytics credentials to configure the Adobe Analytics wizard, follow these steps:
Create a project in Adobe Developer Console.
Add the Analytics API to your project.
Create OAuth 2.0 credentials.
Create a project in the Adobe Developer Console¶
Add APIs¶
Add Adobe Analytics API¶
Choose API authentication¶
Configure API with OAuth 2.0¶
OAuth 2.0 credentials generated¶
Importing Artifacts¶
Once you have the OAuth 2.0 credentials generated, you can get the access token and the refresh token by clicking Tools > OAuth credential wizards > OAuth 2.0 wizard.
The Tool will display the dialog to get the OAuth tokens.
OAuth 2.0 credentials wizard¶
To get the OAuth tokens, enter the following parameters:
Client identifier. The client id generated in the Adobe Developer Console.
Client secret. The client secret generated in the Adobe Developer Console.
Token endpoint URL. https://ims-na1.adobelogin.com/ims/token/v3.
Authorization server URL. https://ims-na1.adobelogin.com/ims/authorize/v2.
Redirect URI. https://adobeioruntime.net.
Scopes. The following scopes are needed in order the final views work properly: openid, AdobeID, read_organizations, additional_info.projectedProductContext and additional_info.job_function.
Now, you have all the data needed to create the predefined Adobe Analytics reports. Right-click on the desired database in the Design Studio Explorer and click New > Data source > Software as a service > Adobe Analytics.
The Tool will display the dialog to get access to Adobe Analytics.
Adobe Analytics wizard¶
To import the Adobe Analytics data sources and views, enter the following parameters:
Database. Name of the database in which the predefined Adobe Analytics reports will be created.
Client ID. The client id generated in the Adobe Developer Console.
Client Secret. The client secret generated in the Adobe Developer Console.
Access token . The access token generated in the VDP wizard for OAuth 2.0.
Company id. Your Adobe company id.
Report suite id. the id of the Adobe Analytics report suite which you want to get data.
Report suite prefix. you can configure the name prefix of every report suite created in the VDP in order to be able to relate VDP views to Adobe Analytics report suites. The max length of this parameter is 10 characters.
Then click Execute import to create the predefined Adobe Analytics reports.
After the execute import finishes, you will be able to see the data sources and the views for accessing to Adobe Analytics.
Note
We have used suite1 as the value of the Report suite id configuration parameter in the examples shown below.
Campaign Performance¶
Predefined reports to know which campaigns are driving the most revenue.
Campaign performance data sources and views¶
${report.suite.prefix}_campaign_tracking_code_report: Returns Analytics data. Required parameter is:datarange: the reporting period. Must have this format: yyyy-MM-ddThh:mm:ss.SSS/yyyy-MM-ddThh:mm:ss.SSS.${report.suite.prefix}_tracking_code_flow_report: Returns Analytics data. Required parameter is:datarange: the reporting period. Must have this format: yyyy-MM-ddThh:mm:ss.SSS/yyyy-MM-ddThh:mm:ss.SSS.
Query Example¶
Now, you can execute queries on the Adobe Analytics views that have been created:
Querying suite1_campaign_tracking_code_report view¶
suite1_campaign_tracking_code_report query results¶
Content Consumption¶
Predefined reports to know which content is being consumed most and is engaging users.
Content consumption data sources and views¶
${report.suite.prefix}_page_report: Returns Analytics data. Required parameter is:daterange: the reporting period. Must have this format: yyyy-MM-ddThh:mm:ss.SSS/yyyy-MM-ddThh:mm:ss.SSS.${report.suite.prefix}_site_section_report: Returns Analytics data. Required parameter is:daterange: the reporting period. Must have this format: yyyy-MM-ddThh:mm:ss.SSS/yyyy-MM-ddThh:mm:ss.SSS.
Query Example¶
Now, you can execute queries on the Adobe Analytics views that have been created:
Querying suite1_page_report view¶
suite1_page_report query results¶
Generic¶
Base view which lets you make a custom report with the metric and dimension you choose.
Generic data sources and views¶
${report.suite.prefix}_custom_report: Returns Analytics data. Required parameters are: *daterange: Must have this format: yyyy-MM-ddThh:mm:ss.SSS/yyyy-MM-ddThh:mm:ss.SSS. *metric1: an available metric of your Adobe report suite. *dimension: an available dimension of your Adobe report suite.
Query Example¶
Now, you can execute queries on the Adobe Analytics views that have been created:
Querying suite1_page_report view¶
suite1_custom_report query results¶
Metric and Dimensions¶
In the Metrics and Dimensions folder there are some views to get the list of available metrics and dimensions defined in your Adobe report suite. To make your own reports using the generic view, you have to use the id field of these views as the parameters metric1 and dimension.
Metrics and dimensions views¶
${report.suite.prefix}_dimensions: Returns available dimensions of your Adobe report suite.${report.suite.prefix}_metrics: Returns available metrics of your Adobe report suite.
Query Example¶
Now, you can execute queries on the Adobe Analytics views that have been created:
suite1_dimensions results¶
suite1_dimensions results¶
Marketing Ecommerce¶
Predefined reports to know the effectiveness of your marketing on ecommerce.
Marketing Ecommerce data sources and views¶
${report.suite.prefix}_marketing_channel_report: Returns Analytics data. Required parameters is:dateRange: the reporting period. Must have this format: yyyy-MM-ddThh:mm:ss.SSS/yyyy-MM-ddThh:mm:ss.SSS.${report.suite.prefix}_sales_by_region_report: Returns Analytics data. Required parameters is:dateRange: the reporting period. Must have this format: yyyy-MM-ddThh:mm:ss.SSS/yyyy-MM-ddThh:mm:ss.SSS.
Query Example¶
Now, you can execute queries on the Adobe Analytics views that have been created:
Querying suite1_page_sales_by_region_report view¶
suite1_page_sales_by_region query results¶
People Metrics¶
Predefined report to know people interacting with your brand.
People Metrics data sources and views.¶
${report.suite.prefix}_site_section_people_report: Returns Analytics data. Required parameters is:dateRange: the reporting period. Must have this format: yyyy-MM-ddThh:mm:ss.SSS/yyyy-MM-ddThh:mm:ss.SSS.
Query Example¶
Now, you can execute queries on the Adobe Analytics views that have been created:
Querying suite1_site_section_people_report view¶
suite1_site_section_people_report query results¶
Product Retail¶
Predefined reports to know which products are performing the best.
Product Retail data sources and views¶
${report.suite.prefix}_product_report: Returns Analytics data. Required parameters are:dateRange: the reporting period. Must have this format: yyyy-MM-ddThh:mm:ss.SSS/yyyy-MM-ddThh:mm:ss.SSS.
Query Example¶
Now, you can execute queries on the Adobe Analytics views that have been created:
Querying suite1_product_report view¶
suite1_product_report query results¶
Web Acquisition¶
Predefined reports detailing the top traffic drivers.
Web Acquisition data sources and views¶
${report.suite.prefix}_entry_page_report: Returns Analytics data. Required parameters are:dateRange: the reporting period. Must have this format: yyyy-MM-ddThh:mm:ss.SSS/yyyy-MM-ddThh:mm:ss.SSS.${report.suite.prefix}_referrer_report: Returns Analytics data. Required parameters are:dateRange: the reporting period. Must have this format: yyyy-MM-ddThh:mm:ss.SSS/yyyy-MM-ddThh:mm:ss.SSS.${report.suite.prefix}_referring_domain_report: Returns Analytics data. Required parameters are:dateRange: the reporting period. Must have this format: yyyy-MM-ddThh:mm:ss.SSS/yyyy-MM-ddThh:mm:ss.SSS.${report.suite.prefix}_search_engine_report: Returns Analytics data. Required parameters are:dateRange: the reporting period. Must have this format: yyyy-MM-ddThh:mm:ss.SSS/yyyy-MM-ddThh:mm:ss.SSS.${report.suite.prefix}_search_keyword_report: Returns Analytics data. Required parameters are:dateRange: the reporting period. Must have this format: yyyy-MM-ddThh:mm:ss.SSS/yyyy-MM-ddThh:mm:ss.SSS.${report.suite.prefix}_tracking_code_report: Returns Analytics data. Required parameters are:dateRange: the reporting period. Must have this format: yyyy-MM-ddThh:mm:ss.SSS/yyyy-MM-ddThh:mm:ss.SSS.
Query Example¶
Now, you can execute queries on the Adobe Analytics views that have been created:
Querying suite1_referring_domain_report view¶
suite1_referring_domain_report query results¶
Web Technology¶
Predefined reports to know which technologies users are using to access your website.
Web Technology data sources and views¶
${report.suite.prefix}_browser_report: Returns Analytics data. Required parameters are:dateRange: Must have this format: yyyy-MM-ddThh:mm:ss.SSS/yyyy-MM-ddThh:mm:ss.SSS.${report.suite.prefix}_countries_report: Returns Analytics data. Required parameters are:dateRange: Must have this format: yyyy-MM-ddThh:mm:ss.SSS/yyyy-MM-ddThh:mm:ss.SSS.${report.suite.prefix}_mobile_device_report: Returns Analytics data. Required parameters are:dateRange: Must have this format: yyyy-MM-ddThh:mm:ss.SSS/yyyy-MM-ddThh:mm:ss.SSS.${report.suite.prefix}_operating_systems_report: Returns Analytics data. Required parameters are:dateRange: Must have this format: yyyy-MM-ddThh:mm:ss.SSS/yyyy-MM-ddThh:mm:ss.SSS.${report.suite.prefix}_regions_report: Returns Analytics data. Required parameters are:dateRange: Must have this format: yyyy-MM-ddThh:mm:ss.SSS/yyyy-MM-ddThh:mm:ss.SSS.
Query Example¶
Now, you can execute queries on the Adobe Analytics views that have been created:
Querying suite1_countries_report view¶
suite1_countries_report query results¶
Appendix I. How to Simplify the Data Range Format in Views¶
You can create a derived view over the final views to divide the daterange text parameter in two timestamp parameters:
startdate and enddate.
Below you can see an example of creating a derived view over ${report.suite.prefix}_browser_report.
First, right click on the ${report.suite.prefix}_browser_report view and select New > Selection.
Create new Selection view option in VDP¶
You have to create two new view parameters in the new view:
startdate: timestamp.enddate: timestamp.
Create view parameters option¶
Now, you have to relate both view parameters with the daterange original parameter in the Where conditions tab using
the following condition:
concat(formatdate('yyyy-MM-dd''T''hh:mm:ss.SSS', startdate), '/', formatdate('yyyy-MM-dd''T''hh:mm:ss.SSS', enddate))
Finally, remove the datarange column from the Output tab and click save:
Output tab¶
Now, you can execute your new view:
New view query¶
New view query results¶