Skip to main content
These are the data types Allyy typically uses to model your supporters and predict who to contact, when, and for how much. Each maps onto one of the four entities in the Allyy data model, though familiarity with that model is not required to prepare your data.
You can connect your data in its existing format and structure. The data-mapping step links your fields to the Allyy data model, so you do not need to restructure your data beforehand. More history and greater detail about your donors and their interactions generally improve prediction accuracy, as the models determine for themselves which data points are relevant.

​
What to share, at a glance

Contacts

Your supporters and their attributes.

Engagement & responses

Direct mail, telemarketing, SMS/WhatsApp and email communication history.

Payments

Donation history across all channels.

Campaigns

Campaign names, labels and unit costs.

Subscriptions

Recurring-giving agreements (direct debit / standing order).

​
1. Contacts

Your supporters — individuals or organisations — and the attributes you hold about them.
  • ContactId — unique identifier
  • Age, Gender, Postal code
  • Other attributes — permissions, contact type, demographics, and anything else you hold
These are the most commonly useful fields, but additional donor-related data is often valuable and worth including. → Mapped to the Contact entity.

​
2. Engagement / responses

Your communication history — what you sent each contact and, where you have it, how they reacted. Include as much detail as you have. For direct mail, SMS/WhatsApp and email, the table usually records the send-out only; the donation itself is found in your payment history (section 3). For telemarketing, the outcome is often stored alongside the call as a response code. Direct Mail — ContactId, Campaign, Send-out timestamp Telemarketing — ContactId, Campaign, Call timestamp, Call response code SMS / WhatsApp — ContactId, Campaign, Sent timestamp Email — ContactId, Campaign, Sent timestamp → Mapped to the Response entity — one record per communication, including the send-out itself.

​
3. Payment history

Every donation you’ve recorded, across all channels.
  • ContactId, Campaign, Payment timestamp, Payment amount
  • Additional fields — payment method, transaction ID, etc. — are welcome
Donations often live in more than one place — one-off donations, responses to mailings, and recurring-donation charges. Include all of them so none is missed; this is the single most important input for accurate models.
→ Mapped to the Response entity.

​
4. Campaign metadata

Background on your campaigns, so Allyy can reason about type of ask and cost-effectiveness.
  • Campaign name
  • Labels — emergency type, region/country, nurturing/retention, or any other characteristics
  • Unit cost — for direct mail and telemarketing
→ Mapped to the Offer entity (also called Content or Treatment) — one row per campaign.

​
5. Subscription agreement history

Your recurring-giving agreements — direct debits and standing orders.
  • ContactId, SubscriptionId
  • Start (YYYY-MM-DD HH:MM:SS)
  • End (YYYY-MM-DD HH:MM:SS, or blank if still active)
  • Amount (numeric, with currency)
  • Frequency (e.g. Monthly)
  • Any other relevant information is welcome
→ Mapped to the Subscription entity.

​
How your data maps to Allyy

You provide data in the terms above; Allyy maps it onto a small set of entities so the same models and dashboards work for any organisation. For the conceptual model behind these entities, see The Allyy data model. For how your fields are connected to them inside the app, see Data mapping. Next: Connect a data source · Data mapping