> ## Documentation Index
> Fetch the complete documentation index at: https://docs.allyy.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Exporting decisions

> Get an optimised contact list out of Allyy and into your tools

Once you have a decision, the final step is to get it into the tools that actually run the campaign — your CRM, mailing house, dialler, or marketing platform.

## Export configurations

An **export configuration** is a saved mapping that tells Allyy:

1. **Where to send the data** — which destination to write to.
2. **Which fields to include** — which columns from the decision to export, and what to call them in the destination.

You define an export configuration once per destination and reuse it across decision runs. Each time you run a decision you can trigger the export, and the same mapping is applied.

> [!NOTE]
>
> The full API specification (authentication, endpoints, payloads) lives in the **API Reference** tab and is maintained separately. This page covers exporting as a product concept.

## Destination types

Allyy supports the following export destinations out of the box:

| Destination | How it works |
| - | - |
| **CSV to Google Cloud Storage** | A CSV file is written to a GCS bucket you control — download it or pick it up via your own pipeline. |
| **BigQuery** | Rows are inserted directly into a BigQuery table in your project. |
| **Microsoft SQL Server** | Bulk insert via a direct database connection. |
| **SFTP** | A CSV is uploaded to a remote SFTP server — typical for mailing house delivery. |
| **ActiveCampaign** | Decision segments sync to your mailing lists or tags. |
| **Agillic** | Rows are pushed to your Agillic data warehouse. |
| **Microsoft Dynamics** | Contacts and scores are synced to your CRM. |

> [!NOTE]
>
> **Screenshot to add** — configuring an export destination and field mapping in the app.

## Field mapping

When you set up an export configuration you choose which fields from the decision output to include and what to name them in the destination. Available fields per contact include:

| Field category | Examples |
| - | - |
| **Identity** | Contact ID, external CRM identifier |
| **Scores** | Propensity score, expected donation amount |
| **Rank** | Position in the decision's ranked list |
| **Segment** | High-potential, standard, control, exploration |
| **Campaign context** | Decision name, entity / mailing identifier |

You can export a subset of these — for example, just the contact identifier and segment label if your downstream tool only needs to know who gets which treatment.

## What's in an export

A typical export carries, per contact:

* The **contact identifier** so your tools can match it to their records.
* The **scores** behind the decision (e.g. propensity, expected amount).
* The **rank** and any **segment** the decision assigned.
* The **campaign / entity** it relates to.

## Multiple exports per decision

One decision can feed multiple destinations. If you send the same contact list to both your mailing house (via SFTP) and your CRM (via MS Dynamics), you can configure both exports against the same decision run.

## Keeping exports in sync

For recurring campaigns, schedule the export as part of a [workflow](https://docs.allyy.io/automation/workflows.md) — sync data, retrain, score, decide, export — so a fresh, optimised list is delivered on cadence without manual steps. You can track every export on the [Monitoring](https://docs.allyy.io/processes/monitoring_dashboard.md) page.

## Next

> [card] [Connect a destination](https://docs.allyy.io/integrations/overview.md)
>
> Set up where your decisions should go.

> [card] [Automate the pipeline](https://docs.allyy.io/automation/workflows.md)
>
> Run the whole loop on a schedule.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.