> 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/active-campaign/synchronize-contact-attributes.md).

# Synchronize contact attributes

## Overview

In this destination service, DinMo creates and updates contacts in ActiveCampaign using the attributes available in your model or segment.

Contacts are matched by **email address**. Unknown contacts are created, and existing contacts are updated with the fields you map.

To get started:

* Create an ActiveCampaign destination for contact attributes. Refer to the [Destination setup section](#destination-setup).
* Create a user model or segment containing the contacts to synchronize. Refer to our [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.
* Activate the model or segment to the destination to start sending data.

## Destination setup

Create a destination using your [ActiveCampaign connection](/integrations/destination-platforms/active-campaign.md#authentication-to-activecampaign) and select the contact attributes destination service.

{% hint style="info" %}
Learn how to create a destination in our [step-by-step tutorial](/guides/get-started-with-dinmo/initial-configuration-of-dinmo/create-a-destination.md).
{% endhint %}

## Activation configuration

Once your destination and model or segment are ready, create an activation and configure the attributes to synchronize.

{% hint style="info" %}
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).
{% endhint %}

### Sync mode

This destination supports **Upsert**:

* Contacts that do not exist in ActiveCampaign are created.
* Existing contacts are updated with the mapped attributes.
* Contacts leaving your source model or segment stop being updated by this activation. Their ActiveCampaign profiles are not deleted.

### Run type

DinMo distinguishes between full and incremental runs:

| Run type  | Behavior                                                                                                     |
| --------- | ------------------------------------------------------------------------------------------------------------ |
| **Full**  | Processes every contact currently in the source model or segment.                                            |
| **Delta** | Processes new contacts and contacts whose mapped attributes have changed since the previous synchronization. |

The synchronization starts with a full run and continues with incremental runs. A full resynchronization processes all current source records again.

In both cases, the sync mode remains **Upsert**. A full run does not delete contacts that are absent from the source.

### Fields mapping

Map your source fields to the following ActiveCampaign fields:

| ActiveCampaign field | Required | Description                                 |
| -------------------- | -------- | ------------------------------------------- |
| Email                | Yes      | Email address used to identify the contact. |
| First name           | No       | Contact's first name.                       |
| Last name            | No       | Contact's last name.                        |
| Phone                | No       | Contact's phone number.                     |

Each record must contain a valid email address.

You can also select existing ActiveCampaign custom contact fields and map them to your source attributes.

### Custom attributes

Use the **Custom attributes** section to specify additional source fields and their destination attribute names.

When saving the mapping, DinMo reuses a matching existing custom field or creates a new one.

### Scheduling

Specify how often the activation should run.

At each execution, DinMo processes the records selected by the run type and creates or updates their mapped attributes.


---

# 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/active-campaign/synchronize-contact-attributes.md?ask=<question>&goal=<user_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.