Export configurations
An export configuration is a saved mapping that tells Allyy:- Where to send the data — which destination to write to.
- Which fields to include — which columns from the decision to export, and what to call them in the destination.
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: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:
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 — 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 page.Next
Connect a destination
Set up where your decisions should go.
Automate the pipeline
Run the whole loop on a schedule.