Note about Service Account (JWT) deprecation
Adobe Analytics is deprecating Service Account (JWT) authentication according to this timeline. This means that it will be supported until January 1, 2025. Creation of new Service Account (JWT) credentials will be supported until May 1, 2024.
To be able to create Service Account (JWT) credentials in the Adobe Analytics platform, OAuth Server-to-Server authentication must not already have been set up for that Adobe Analytics project.
Funnel will replace Service Account (JWT) authentication with OAuth Server-to-Server at the latest May 1, 2024.
This article covers both the Adobe Analytics and the Adobe Analytics 2.0 connector.
Adobe Analytics 2.0 requires less permissions and is more performant, so we suggest to use 2.0 over the original one.
Introduction to credential for Adobe Analytics
New Adobe Analytics data sources in Funnel utilize OAuth Server-to-Server credentials.
See the note above regarding Service Account (JWT) credentials, these can still be used but no new ones can be created.
This means the data from Adobe Analytics is retrieved to Funnel with another set of credentials compared to your personal Adobe account.
In a typical setup, you may have your personal account, which you log in to Adobe Analytics and can view data, set calculated metrics, etc. (if you have the proper permissions)
In addition to/or exclusively to the personal account, someone with System administrator or Developer user roles in an Adobe Analytics account needs to add OAuth Server-to-Server credentials.
So, if you have System administrator or Developer access, follow the steps below or ask someone who has access to do it. You will need the client ID and client Secret in Funnel.
In addition, the technical account email connected to the created OAuth Server-to-Server, used for sharing calculated metrics and segments, can be useful to write down/ask for. See also Troubleshooting missing segments/calculated metrics
Details on how to add a OAuth Server-to-Server credentials in Adobe to be used in Funnel
Prerequisite:
You need to have System administrator or Developer access in Adobe for the following steps.
1. Create profile with correct permissions
1.1 Create a profile
Go to the Admin console
Make sure the correct organisation is chosen in the top right
Select the Products tab, choose "Adobe Analytics" and click New Profile
Click on the new profile and go to Permissions:
1.2. Set the correct permissions
To get all reports suites, metrics and dimensions available in your Adobe product. Click Edit and choose Auto-include: On for Report suites, Metrics and Dimensions:
You can also opt to only select the report suites, metrics and dimensions that Funnel should be able to handle. At least one report suite, one metric and one dimension needs to be included for the credential to work.
Only applicable to Adobe Analytics (1.4) and not Adobe Analytics 2.0
Only applicable to Adobe Analytics (1.4) and not Adobe Analytics 2.0
Click Report Suite Tools and add Report Suite Mgmt:
From Analytics Tools, add Web Services, Web Service Access and Reports &
Analytics Access:
Save your settings.
1.3. Make the profile available for developer console
To make sure the make sure the profile is available in the next step. In Adobe Admin console, go to Users->Developers. Make sure the current user is a developer and add the new profile.
2. Create a Project with access to Adobe Analytics
OAuth Server-to-Server is the recommended authentication method.
2.1 Create a project in the developer console in the same organisation as the previous instructions. This help article describes the steps. Make sure that the same organisation is chosen as the one the profile was created for:
Also
2.2 Add Adobe Analytics as an API to a new project:
2.3 Select OAuth Server-to-Server
2.4 Select the profile created in step 1 and Save:
If you cant see the configured profile here. Go back to step 1.3
3. Retrieve credentials
Go to OAuth Server-to-Server under the Credentials group and copy the client ID and the client secret:
Also write down technical user email since it will be useful for the personal User to share custom metrics and custom segments with the newly created technical (server-to-server credential) user.
