# Adobe Analytics

[Adobe ](https://www.adobe.com/)is an multinational computer software and web analytics company (See [Adobe Experience Cloud](https://business.adobe.com/)). Using this destination you can implement server-side tracking, by sending events to Adobe Analytics.

Please note that we use the Adobe [Bulk Data Insertion API](https://developer.adobe.com/analytics-apis/docs/2.0/guides/endpoints/bulk-data-insertion/).

### Authentication

We use the Oauth2 authentication process.

{% hint style="warning" %}
Only the **server-to-server** oauth is supported
{% endhint %}

Go to *Administration* / *Connector Credentials* and click on **Add connector credentials**.\
Select Adobe Analytics.

<figure><img src="/files/yPSh7mWHU9w9aqp8awLO" alt=""><figcaption></figcaption></figure>

Enter the Client ID and Client Secret that you can find on your **Adobe Developer Console**.

<figure><img src="/files/M7tOrSJj4VwNfmdDkXgR" alt="" width="375"><figcaption></figcaption></figure>

<figure><img src="/files/6d3VPkUJ63evU4ugZlyd" alt=""><figcaption></figcaption></figure>

In case you haven’t selected the server-to-server oauth (if it is an old project, and you don’t want to configure it again for example), it is possible to change the authentication, click on “Connect another credential” on Adobe Analytics interface.

<figure><img src="/files/rS3WRw52EUMpej96TuUD" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/JM6sG6SOy7XvfI7Fhtcu" alt=""><figcaption></figcaption></figure>

### Configuration

Click on *Destinations* / *Add destination* and select **Adobe Analytics** on the catalog.

Select sources, give a name to the destination and select the environment.

Select the authentication you've just created previously.

Fill the **Adobe Group ID** and **Customer ID Type** coming from your Adobe Analytics account.

<figure><img src="/files/JP7wyOAecREMCd6nI8tw" alt=""><figcaption></figcaption></figure>

#### **Mandatory parameters mapping**

This parameter is mandatory:

* userAgent

You can map corresponding properties or directly enter values.

#### **User id mapping**

At least one of these fields should be filled to identify users.

* visitorID
* marketingCloudVisitorId
* IP address
* CustomerID (CustomerIDType)

<figure><img src="/files/WQ6XsZkN7PoVDDaLlGuJ" alt=""><figcaption></figcaption></figure>

#### Page identifier mapping

Adobe web page identifier. You can set several, but at least one is needed for the export. If you set either linkName, linkURL or linkType the other two must be set as well.

<figure><img src="/files/d0kIOrFLI8EfvKSTNGik" alt=""><figcaption></figcaption></figure>

#### Mapping

You can map here all your event properties to Adobe Analytics properties, especially eVars.

<figure><img src="/files/uieyG8cyYGezw0Jj0G9b" alt=""><figcaption></figcaption></figure>

#### Properties transformation

This step is optional, you can transform your properties before to send it.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://doc.commandersact.com/features/destinations/destinations-catalog/adobe/adobe-analytics.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.