Adobe Analytics
Follow our setup guide to integer the reverse-connector Adobe Analytics
Last updated
Was this helpful?
Follow our setup guide to integer the reverse-connector Adobe Analytics
Last updated
Was this helpful?
To establish a connection between the QUANTI platform and the Adobe Analytics reverse connector, it is essential to possess an Adobe Experience Cloud account. This account will provide the necessary permissions to access and interact with the Adobe Analytics product.
Access the Adobe Developer Console using your Adobe Experience Cloud credentials.
Navigate to the Console tab, specifically the APIs and services section, and review the available services.
Locate the Adobe Analytics service and proceed to create a new project.
Select OAuth server-to-server.
Assign a unique name to your project (For example: Quanti Reverse Connector API) and move to the next step.
Select your organization's name and click on "Save configured API".
Then on the new project page, you will see your API Key (Client ID). Note the API key. You will need it to configure QUANTI:
Click on OAuth Server-to-Server < 'Retrieve Client Secret'. Note the Client Secret. You will need it to configure QUANTI:
Enter Adobe Analytics UI and go to your Adobe Analytics product.
Click on the tab Admin > Report Suite > Select your Report Suite > Edit Settings > Conversion > Conversion Classification.
Select Classification Type "Campaign" and add your classification field names.
Note the classification field names. You will need them to configure QUANTI:
Click on the tab Admin > Report Suite > Select your Report Suite > Edit Settings > Conversion > Success Events.
Select events of your choice and add your custom metrics names.
Write down events and meanings. You will need them to configure QUANTI:
Click on the tab Admin > Data sources > Select your Report Suite in the top-right corner > Create
Now, on the page for creating a new data source, in the first multi-select field, choose: Ad Campaigns, and in the second multi-select field, choose: Generic Pay-Per-Click Service. Click Next.
A pop-up will open and ask you to name your data source and provide an email address where notifications will be sent each time data is uploaded.
Check the box to give your consent, then click on "Next".
Check the metrics you wish to import and fill in the fields with any additional metrics you wish to import, then click on "Next".
In the selection fields, for each metric listed, select the events you created previously in the "Declare your custom metrics" step. Then click "Next".
Check the box labeled "Tracking codes" and click on "Next".
In the selection field for Tracking codes, select "Tracking Code".
Then click "Next", "Save" and "Close".
You will have to set 2 connectors type : Adobe Analytics - Data Sources Connector and Adobe Analytics - Classifications Connector. They don’t use the same API point and don’t import the same data type. Therefore, we formally present you with the subject, separating it into two distinct connectors
Adobe Analytics - Data Sources Connector is used to import metrics.
Adobe Analytics - Classifications Connector is used to import dimensions. In Data Warehousing language, we can talk about "Fact table" for data source importing and "Dimensions table" for classification importing. It is very important to understand this point for the rest because Adobe Analytics will match your two imports using the primary keys concept.
These steps show how to create a SQL query which permits to import data into Adobe Analytics UI. The selected fields in your query must coincide with custom metrics that you created above. You can import all custom metrics you want, but you have to respect two mandatory fields: Date and tracking_code.
Date field: Make a coincidence between a field with a date data type from your query and the date field expected by the connector.
Tracking Code field: Make a coincidence between a string data type field from your query and the tracking_code expected by the connector. Tracking_code + date are the unique keys of your query which permit afterwards to match your data source with classification dimensions that we will configure together later in this tutorial. Data type expected :
Date (DATE - YYYY-mm-dd)
Tracking Code (STRING - Matching with your Classification)
Event 1 (FLOAT)
Event 2 (FLOAT)
Event 3 (FLOAT)
All custom events must be of FLOAT type. Date, Tracking Code & Events are written with space and upper case as in the example above.
These steps show how to extract data from your table:
Build a new SQL request from your table following the last step and give aliases to your queried fields. Your query must only compose of fields expected by Adobe Analytics.
In the connector setup form, copy/paste your query.
Click Next.
Make correspondence between query fields and fields expected by Adobe Analytics.
Tracking_code field and date field are expected by Adobe Analytics: You have to indicate which fields are used for them in your query.
You also have to fill each text input using custom metric names created earlier in your Adobe Analytics UI.
Click View details.
These steps show how to create a SQL query which permits to import dimensions in Adobe Analytics UI. The selected fields in your query must coincide with classification names that you created above. You have to respect one mandatory field: tracking_code. Make a coincidence between a string data type field from your query and the tracking_code expected by the connector. Tracking_code must be the unique key of your query and permit afterwards to match your classification dimensions with your data source.
These steps show how to extract a classification table from your Data Warehouse:
Build a new SQL request from your table following the last step and give aliases to your queried fields. Your query must only compose of fields expected by Adobe Analytics.
In the connector setup form, copy/paste your query.
Click Next.
Make correspondence between query fields and fields expected by Adobe Analytics.
Key field is expected by Adobe Analytics: You have to indicate which field is used for it in your query.
You also have to fill each text input using classification names created earlier in Adobe Analytics UI in step 2 above.
Click View details.
I want to know the expenses made on my advertising platforms for each of my traffic sources to my site. Therefore, I will need to identify the traffic sent to my site and match it with the metrics imported from the data source to have a clear dispatch of my campaign performances between my sources and campaigns.
To align the metrics you import from external sources into Adobe Analytics (such as impressions, clicks, or spend from your advertising platforms) with internal Adobe Analytics metrics (for example: visits, conversions, or revenue), it is crucial to match them.
Quanti supports you in these transformation procedures with pre-built transformations that allow you to merge your data from different sources (campaign data and navigation data) using the concept of reconciliation and the use of Tracking Template.