# Data model

The following data is synced, grouped here by how it is stored in Mailchimp

**Email address**

The contact's email address

#### Subscription status

* Subscribed: Can be emailed
* Pending: Has been sent an email asking them to confirm they want to be subscribed
* Unsubscribed: Can't be emailed but does still count towards billing
* Archived: Can't be emailed and no longer counts towards billing but data has not been deleted, if the user is unarchived their data would be restored (e.g. open/click rates)
* Deleted: Data is fully deleted from Mailchimp, if the user is re-added they will have no previous data associated with them

#### Tags

Contacts can have one or more tags.

beabee currently has one standard tag, Active member" which is set on contacts who have an active "member" role. Community organisers can also assign a tag to a segment and this will be set on all contacts who are in the segment.

#### Merge fields

Contacts can have merge fields (custom fields), currently we use:

| beabee field                | Mailchimp merge field | Example      |
| --------------------------- | --------------------- | ------------ |
| First name                  | FNAME                 | Will         |
| Last name                   | LNAME                 | Franklin     |
| Contribution monthly amount | C\_MNTHAMT            | 5            |
| Contribution period         | C\_PERIOD             | annually     |
| Contribution description    | C\_DESC               | £60/annually |
| Referral code               | REFCODE               | WF301        |
| Polls code                  | POLLSCODE             | WF678        |

**Note:** This currently isn't editable by community organisers


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://wiki.beabee.io/help-center-english/mailchimp-integration/data-model.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.