> For the complete documentation index, see [llms.txt](https://doc.commandersact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.commandersact.com/features/destinations/destinations-catalog/data-activation-legacy.md).

# 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="/files/Vys3JJEO9il5LIIkrCzC" 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="/files/MGuP4IsJ2yo3vuFnNWhd" 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="/files/MJ05bCVF2JMS6I3kAbay" 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="/files/zD5jEYlhi5QKHXwWSOFX" 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="/files/zqdzBlsVXdP9uka7qk5p" 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.


---

# 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://doc.commandersact.com/features/destinations/destinations-catalog/data-activation-legacy.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.