> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/recommendations-and-merchandising/how-tos/how-to-configure-your-analytics-integration/how-to-configure-adobe-analytics-integration.md).

# How to configure Adobe Analytics integration

This how-to provides a comprehensive guide to setting up Adobe Analytics integration with AB Tasty through Data Feed export, detailing each step from creating [eVars](https://experienceleague.adobe.com/en/docs/analytics/admin/admin-tools/manage-report-suites/edit-report-suite/conversion-variables/conversion-var-admin) and events to configuring data feeds.

### Overview

ABTasty Recommendations needs to collect the following "hits" and associated details to cross-reference with your catalog and train its algorithms:

* Page views
* Purchases
* ABTasty Recommendations events

### Prerequisites

* Ensure you have administrative access to Adobe Analytics to create eVars, events, and data feeds.&#x20;

### Step-by-step guide

{% stepper %}
{% step %}

#### Create eVars for recommendation tracking

Create two **text-type** eVar in Adobe Analytics:

1. <kbd>recommendation\_id</kbd>
2. <kbd>recommendation\_item\_ids</kbd>
   {% endstep %}

{% step %}

#### Configure success events

Create three **Counter-type** [success events](https://experienceleague.adobe.com/en/docs/analytics/admin/admin-tools/manage-report-suites/edit-report-suite/conversion-variables/success-event) to measure your recommendations KPIs:

1. <kbd>recommendation\_show</kbd>
2. <kbd>recommendation\_add\_to\_cart</kbd>
3. <kbd>recommendation\_go\_to\_page</kbd>
   {% endstep %}

{% step %}
{% hint style="info" %}
For each event, set the **Unique Event Recording** column to "Use Event ID"
{% endhint %}
{% endstep %}

{% step %}

#### Create a Data Feed

1. Set up a Data Feed to send daily exports to AB Tasty by following the steps described [here](https://experienceleague.adobe.com/en/docs/analytics/export/analytics-data-feed/create-feed).
2. Use ABTasty’s SFTP as **destination.**&#x20;
3. Ensure the following columns are included:

* date\_time
* visid\_high
* visid\_low
* visit\_num
* visit\_page\_num
* page\_url
* pagename
* purchaseid
* product\_list
* eVarXX
* eVarXX
* mobile\_id
* event\_list

Save your **Data Feed configuration** and note down the export name.
{% endstep %}

{% step %}

#### Enable dynamic lookups

Contact Adobe support to enable [dynamic lookups](https://experienceleague.adobe.com/en/docs/analytics/export/analytics-data-feed/data-feed-contents/dynamic-lookups) on your Data Feed. This will allow mobile device attributes to be included in the exported data.
{% endstep %}

{% step %}

#### Share the configuration details with your TSM

Provide your TSM with the following information:

* The **Data Feed export name**&#x20;
* Both eVar names: <kbd>recommendation\_id</kbd> and <kbd>recommendation\_item\_ids</kbd>&#x20;
* All three event IDs: <kbd>recommendation\_show</kbd> , <kbd>recommendation\_add\_to\_cart</kbd> and  <kbd>recommendation\_go\_to\_page</kbd>

{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.abtasty.com/recommendations-and-merchandising/how-tos/how-to-configure-your-analytics-integration/how-to-configure-adobe-analytics-integration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
