# Data Activation Legacy

{% hint style="info" %}
This destination is temporary, it is the first step of the migration to support events format in Data Activation module
{% endhint %}

Map events collected to Data Activation format (previously called Data Commander format). The goal is to collect events and map it to Data Activation format to be able to use the segmentation, audience connectors, augmented user attributes...

Select Data Activation Legacy on the destination catalog.

On the settings page, you can find the mapping:

## **Step 1: Data Activation Variable ← Event property mapping**

<figure><img src="https://1259070148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mk6XpTQ2LaRLcr2tA-d%2Fuploads%2Fgit-blob-412c2d2a660647adb495d14410a1980a69e2a347%2FCapture%20d%E2%80%99e%CC%81cran%202023-04-20%20a%CC%80%2011.31.01.png?alt=media" alt=""><figcaption></figcaption></figure>

Select on the left a Data Activation variable (user\_email ; user\_id...) and map it to the corresponding event's property (user.email ; value...).

You can use a static value, please enter it between quotation marks “ “.

## Step 2: **Data Activation page type (env\_template variable) ← Event name mapping**

<figure><img src="https://1259070148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mk6XpTQ2LaRLcr2tA-d%2Fuploads%2Fgit-blob-e7a223452602de13cad60f64e17a37312700490f%2FCapture%20d%E2%80%99e%CC%81cran%202023-04-20%20a%CC%80%2011.31.19.png?alt=media" alt=""><figcaption></figcaption></figure>

This mapping is dedicated for env\_template variable.

On the left, enter the env\_template variable corresponding to the page type and map it to the event name (ex: funnel\_confirmation ⇒ purchase).

## Step 3: additional mapping, ONLY for page\_view event

<figure><img src="https://1259070148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mk6XpTQ2LaRLcr2tA-d%2Fuploads%2Fgit-blob-65234bae1fc1b6345a6f9e12189a50f406ca32c9%2FCapture%20d%E2%80%99e%CC%81cran%202023-04-20%20a%CC%80%2011.31.29.png?alt=media" alt=""><figcaption></figcaption></figure>

Only for page view event, map the env\_template variable corresponding to the page type to the page type in page view event (ex: productpage ⇒ product).

## Step 4: Advanced options

<figure><img src="https://1259070148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mk6XpTQ2LaRLcr2tA-d%2Fuploads%2Fgit-blob-d3162be556fbad7d9720d833afcf4d9bdcadf3bb%2FCapture%20d%E2%80%99e%CC%81cran%202023-05-11%20a%CC%80%2015.23.17.png?alt=media" alt=""><figcaption></figcaption></figure>

### Purchase event to Data activation conversion universe

If you check the box, purchase events will be stored on Data activation conversion storage.

### Items mapping

If you check the box, you can define the mapping between product variables and items properties in event.

<figure><img src="https://1259070148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mk6XpTQ2LaRLcr2tA-d%2Fuploads%2Fgit-blob-0aa7111755be77adf11d3d6b1f27206ee51745f1%2FCapture%20d%E2%80%99e%CC%81cran%202023-04-20%20a%CC%80%2016.22.41.png?alt=media" alt=""><figcaption></figcaption></figure>

First, select the variable corresponding to the product list. Then, map the product variable to the item property in the event.