Adobe Analytics Advanced Connector

Creating a new OAuth project in Adobe Developer Console

To create a new OAuth project in Adobe Developer Console, do the following:

1. Log into https://console.adobe.io/projects.
2. Click Create new project button.
3. Click on Add API to start using the Adobe services.

4. The APIs available to you will be listed in the Add an API window. Select Adobe Analytics. 

5. Now, you need to select the authentication type. Select OAuth here.

6. Select the Web platform to configure the API.

    Enter the redirect URI as https://oauth.domo.com/api/data/v2/o...oauth/exchange

7. Click Save configured API.

Credentials Pane

This pane contains fields for entering credentials to connect to the Adobe Analytics API. The following table describes what is needed for each field:  

Once you have entered valid credentials, you can use the same account any time you go to create a new Adobe Analytics Advanced DataSet. You can manage connector accounts in the Accounts tab in the Data Center. For more information about this tab, see Managing User Accounts for Connectors.

Details Pane

This pane contains two primary menus, Report Suite and Report Type, along with various other menus which may or may not appear depending on the report type you select.

Other Panes

For information about the remaining sections of the connector interface, including how to configure scheduling, retry, and update options, see Adding a DataSet Using a Data Connector.

Using Additional Elements to Increase Your Top Results

By default, the Adobe Analytics API only return the top 10 results for the selected element. You can increase the number of top results using Additional Elements. For example, to increase the limit to 100 you would add the following to the Additional Elements field:

{“top”:100,
“id”:”page”}

"id" is the ID of the element you want. There is no upper limit to the “Top” number but the less you pull back in using the query, the more efficient it will be. You can do this for multiple elements by separating them with a comma.

{“top”:100,
“id”:”page”},
{“top”:100,
“id”:”region”} 

Using Additional Elements to Search for Keywords in Elements

You can use Additional Elements to search for keywords in elements by inputting properly formatted JSON. You can search using AND, OR, and NOT operators. Below is a table that describes these operators.

The following example searches for the top three pages that have “help” OR “faq” in the page name/URL. You can also do an AND search by replacing the “OR” with “AND”. 

{
"id": "page",
"top": 3,
"search": {
"type": "OR",
"keywords": ["help","faq"]
}
}

You can also use special characters like the following to increase the power of your search:

Here is an example of a search that uses these characters:

{
"id": "page",
"top": 3,
"search": {
"type": "OR",
"keywords": [“help*","^faq"]
}
}

Exact keyword matches can be obtained by placing the "starts with" and "ends with" special characters at the beginning and ending of the keyword:

{
"id": "page",
"top": 3,
"search": {
"type": "OR",
"keywords": ["^faq$"]
}
}

Adding Classifications to the JSON Syntax

If you wish to do any of the above advanced functions with a SAINT Classification then you need to add the classification to the JSON syntax, as shown in the following example:

{
"id": “page",
“classification”:”region”,
"top": 3
}

Unique Metrics

One of the most frequently encountered issues with the Adobe Analytics connector involves unique metrics, such as Unique Visitors, Unique Pageviews, etc. Unique metrics are non-additive and need to be pulled from the connector at the same level of granularity they will be viewed at. This is because if you pull these metrics in a different granularity when the numbers are rolled up, they will no longer be accurate. For example, say we have a visitor to our site, Visitor 1. This individual visits the site once a day for a week. When we go to report how many people visited the site in a week, if we pull the data using a day granularity, Visitor 1 is counted 7 times. However, if we pull the data using a week granularity, Visitor 1 is only counted once, giving us an accurate count of how many individuals visited the page in a week but NOT how many times the site was visited. The following table shows a visual example of this:

API Explorer

Adobe Analytics has an API Explorer that you can use to run your report and check the results. It is available at https://marketing.adobe.com/developer/api-explorer.

Do I need a certain kind of account with the data service to set up the connector?

It is best if your account has the Admin access. At the very least you need access to the report suites you want as well as access to retrieve elements, metrics and segments from the API.

My Adobe Analytics datasets are failing intermittently and displaying unhelpful error messages like "Unable to complete report at this time. Please try again later." What should I do?

This error originates on Adobe’s end. Unfortunately, it is nothing we at Domo have direct control over, but we are working with Adobe to improve these types of errors. That said, you can take steps to alleviate the occurrence of these errors, which include reducing the number of connectors, the frequency at which they try to pull data, and the size of their requests. Attempting to schedule requests to run at different times can also help. Another possible solution is to use the “retry” setting in the connector.

What do I do if I need to include more than 4 elements in my Adobe Analytics DataSet?

Run Adobe's Data Warehouse reports. These do not use the Domo connector; rather they leverage scheduled emails to import data into Domo. These reports can use SFTP. Note that results may vary slightly from the Adobe Analytics front end.

My report takes a long time. How do I speed up my report?

In case of the Intermediate-Custom report, the number of elements selected and the parameters in the Additional Element Information text box can make a big difference in your report performance. Select the minimum number of elements needed.

It is also possible to have a number of reports queued up in Adobe Analytics that is preventing your report from being finished. You can use the Queue report to see what reports are currently being processed by Adobe.

If you have a large number of datasets, try to stagger their execution times so that the datasets will not clog up Adobe's queue all at once.

Is there a way to see what data is being returned from the Adobe Analytics API?

Adobe Analytics has an API Explorer that you can use to run your report and check the results. It is available at https://marketing.adobe.com/developer/api-explorer.

Is there any limit to the number of Elements that can be retrieved?

Adobe's API has a 4 element limit and only 50000 rows per element can be retrieved.

What is the workflow for pulling data from Adobe?

The process used by Domo to pull Adobe data is as follows:

1. Queue report -- Domo sends Adobe the parameters of the desired report. https://github.com/AdobeDocs/analyti...ods/r_Queue.md

2. Get report ID -- Domo receives a report ID.

3. Wait for report to be done -- Domo watches Adobe's queue and wait for the report to be done. https://github.com/AdobeDocs/analyti.../r_GetQueue.md

4. Pull report -- When the report no longer appears in the queue, Domo uses the report ID received in step 2 to ask for the data of the report. https://github.com/AdobeDocs/analyti...thods/r_Get.md