> For the complete documentation index, see [llms.txt](https://docs.dinmo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dinmo.io/integrations/destination-platforms/attentive/export-contact-lists.md).
# Export contact lists
## Overview
In this destination service, DinMo will create lists of user and keep them up to date in Attentive.
To do so, you will need to go through these three steps:
* Create a Attentive destination. Refer to the [corresponding section ](/integrations/destination-platforms/attentive.md)for more info.
* Create a user model or segment composed of all the users that will populate your list in Attentive.\
Refer to this [step-by-step tutorial](/guides/get-started-with-dinmo/create-and-activate-segments-on-dinmo/create-your-first-segment.md) to learn how to build segments without SQL in DinMo.
* Activate the segment to the Attentive destination to start sending data. Refer to the corresponding section for more info.
{% hint style="warning" %}
Due to a Attentive limitation, DinMo will not directly create a list in Attentive. Instead, it will create and update an attribute in the users table, which will be set to `True` for all the users who are part of the list.
{% endhint %}
* To finalize the list creation, navigate to the Attentive interface, then creating a new list by filtering all the users where the attribute value is `True`.
Each time the activation will be running:
* Any new user entering your DinMo model or segment will have its attribute updated to `True` in Attentive
* Any user leaving your DinMo model or segment will have its attribute updated to `False` in Attentive
{% hint style="info" %}
Note that only users who have an external ID (email or phone) linked to an existing Attentive user will be considered by DinMo. In this destination service, DinMo will not create new user.
{% endhint %}
## Destination setup
To start exporting lists, you are first required to create a Attentive destination with the corresponding destination service.
### Optional: Setup default activation settings
At the end of the destination creation, you will be proposed to setup Default Activation Settings. This step is optional, but is highly recommended to facilitate the activation process.
By configuring default settings, synchronizing all your contacts lists to Attentive will just take one click. Without default settings, you will be required to go through the [configuration](#activation-configuration) each time you activate a new audience.
Note that even if you setup default settings, you will still be able to adjust activation settings for each of your activations if you wish to.
## Activation configuration
Once the destination has been setup, and your DinMo model or segment created, you can create an activation to start sending data to Attentive right away. The model or segment will be exported as an attribute value in Attentive (`True` / `False`).
Learn how to activate a segment in our [step-by-step tutorial](/guides/get-started-with-dinmo/create-and-activate-segments-on-dinmo/activate-your-first-segment.md)
### Audience Name
The audience name will be the name of the attribute that will be created in the users table in Attentive. DinMo will replace spaces by underscores.
{% hint style="warning" %}
Make sure an attribute with the same name does not already exist.
{% endhint %}
### Fields mapping
In this section, specify the DinMo field corresponding to the external ID that should be used by Attentive to identify your users. It must correspond to the email or the phone number.
### **Scheduling**
In this section, specify how often the list should be updated in Attentive. Every time the list is updated:
* Any new user entering your DinMo model or segment will have its attribute updated to `True` in Attentive
* Any user leaving your DinMo model or segment will have its attribute updated to `False` in Attentive
### **Warnings**
In this section, specify if you want to receive warning for your Attentive activation.
{% hint style="info" %}
Consult the specific section to [learn more about sync warnings](/activations/troubleshooting-syncs/sync-warnings.md).
{% endhint %}
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.dinmo.io/integrations/destination-platforms/attentive/export-contact-lists.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
