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

# Understand your audience

> Ask who came in, what one person shared, and how your whole audience is growing. Every answer comes from your live Fanaura contacts.

Every person who shares an email or phone number through a journey becomes a contact. Fanaura keeps what they told you, how they found you, and each time they came back. Your assistant can read all of it, from a single contact to your whole audience.

## Pick the right question

<CardGroup cols={2}>
  <Card title="How many contacts do I have?" icon="hash" href="/mcp-server/tools/contacts#audience-overview">
    Total contacts, new this week, and how many have an email or phone. Uses `audience_overview`.
  </Card>

  <Card title="Who came in?" icon="list" href="/mcp-server/tools/contacts#search-contacts">
    A list of contacts with a summary and their three newest events. Uses `search_contacts`.
  </Card>

  <Card title="Tell me about one person" icon="user" href="/mcp-server/tools/contacts#get-contact">
    A written summary, every field, the full timeline, and what is missing. Uses `get_contact`.
  </Card>

  <Card title="How is my audience changing?" icon="chart-line" href="/mcp-server/tools/contacts#audience-activity">
    New contacts per day and breakdowns by journey, source, city, and device. Uses `audience_activity`.
  </Card>
</CardGroup>

## Ask about one contact

You can name a contact by Instagram handle, email, phone, or Fanaura contact ID.

```text theme={null}
Tell me everything about @jordan.
```

The answer follows the same order every time:

<Steps>
  <Step title="A summary paragraph">
    Written by Fanaura from the contact's data, so it reads the same in Claude and ChatGPT.

    > Jordan Lee joined Tue, Mar 3, 8:14 PM. They found you by commenting on Instagram. They were in Austin, Texas, United States on iPhone. They told you their favorite song Midnight. You can reach them at [jordan@example.com](mailto:jordan@example.com). Their engagement score is 32, across 3 link visits.
  </Step>

  <Step title="The timeline, oldest first">
    Each event has a plain label such as "Commented on Instagram", "Opened your link", "Came back to your link", or "Filled out your journey". Times are shown in your account's time zone.
  </Step>

  <Step title="What is missing">
    Fanaura splits missing details into two lists: questions the contact was asked and did not answer, and questions no journey has asked yet.
  </Step>
</Steps>

<Info>
  The assistant is told not to invent details. If a field is not in the result, it says the field is missing instead of guessing.
</Info>

## Search and rank

<Tabs>
  <Tab title="Find people">
    ```text theme={null}
    Find contacts in Austin.
    Who came in from my BOOK journey this week?
    Search my contacts for "jordan".
    ```

    `search_contacts` returns up to 50 contacts per page, 20 by default. Ask for "more" and the assistant passes the `next_cursor` to load the next page.
  </Tab>

  <Tab title="Rank by visits">
    ```text theme={null}
    Who opened my link the most?
    Show contacts who came back at least 3 times.
    ```

    Ranking uses link visits across your journeys. `min_visits` keeps only contacts who visited at least that many times.
  </Tab>

  <Tab title="Filter by a field">
    ```text theme={null}
    Which contacts follow me on Instagram?
    Show contacts whose streaming service is Spotify.
    ```

    Any stored field can be a filter. Ask "What can I know about my fans?" to see every field and how many contacts have it.
  </Tab>
</Tabs>

## Read the whole audience

```text theme={null}
How did my audience grow in September, and where did they come from?
```

`audience_activity` returns counts, not individual people:

| Breakdown | What it shows |
| - | - |
| `new_contacts_per_day` | How many contacts joined each day |
| `events_by_type` | How many comments, DMs, visits, and form fills happened |
| `by_journey` | Link visits per journey |
| `by_source` | Which app people opened your link from |
| `by_city` | Link visits per city |
| `by_device` | Link visits per device |
| `by_field` | Counts for one field you name, such as `vip_status` or `city` |

<Warning>
  Each breakdown reads up to 5,000 rows in the range. When a range is larger, the result says `truncated: true`. Ask for a shorter range to get exact counts.
</Warning>

## Where each detail comes from

Every field has a provenance, so you know how much to trust it.

<Columns cols={2}>
  <Card title="Self reported" icon="message-circle">
    The contact typed it into your journey: name, email, phone, birthday, favorite song.
  </Card>

  <Card title="Inferred" icon="map-pin">
    Fanaura estimated it from the visit, such as city from the network. A city the contact typed shows as self reported.
  </Card>

  <Card title="Enriched" icon="instagram">
    Fanaura added it from a connected service, such as the Instagram handle, follower count, or whether they follow you.
  </Card>

  <Card title="Imported" icon="upload">
    It came from an import or another system, such as VIP status or rewards.
  </Card>
</Columns>

<Card title="Field and event reference" icon="book-open" href="/mcp-server/tools/contacts">
  Every contact field, every event type, and the full response for each contact tool.
</Card>


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