# Data Overview

AgileCRM gives you access to a wide range of CRM data across sales, marketing, and support. When you connect through Coupler.io, you can pull structured data from any of the available entities and use it in your reports and dashboards.

## Available entities

| Entity         | What it contains                                                               |
| -------------- | ------------------------------------------------------------------------------ |
| Contacts       | Contact records with properties, tags, lead score, owner, and activity history |
| Companies      | Company profiles with industry, size, website, and linked contacts             |
| Deals          | Deal name, value, stage, probability, close date, and assigned owner           |
| Notes          | Note content, associated record (contact/company/deal), author, and timestamp  |
| Tasks          | Task subject, type, due date, status, priority, and assignee                   |
| Events         | Event title, start/end time, associated contact, and attendees                 |
| Milestones     | Pipeline stage names, order, and probability percentages                       |
| Campaigns      | Campaign name, status, type, stats, and creation date                          |
| Documents      | Document name, type, associated contact or deal, and upload date               |
| Ticket filters | Filter name, conditions, and associated ticket view settings                   |
| Tickets        | Ticket subject, status, priority, assignee, requester, and timestamps          |

## Contacts

#### Key fields

| Field                    | Description                             |
| ------------------------ | --------------------------------------- |
| id                       | Unique contact identifier               |
| first\_name / last\_name | Contact's full name                     |
| email                    | Primary email address                   |
| phone                    | Phone number                            |
| lead\_score              | Numeric lead score assigned in AgileCRM |
| tags                     | List of tags applied to the contact     |
| owner                    | Team member responsible for the contact |
| created\_time            | Timestamp when the contact was created  |
| updated\_time            | Timestamp of the last update            |

## Companies

#### Key fields

| Field             | Description                 |
| ----------------- | --------------------------- |
| id                | Unique company identifier   |
| name              | Company name                |
| url               | Company website             |
| industry          | Industry category           |
| no\_of\_employees | Estimated employee count    |
| tags              | Tags applied to the company |
| created\_time     | Record creation timestamp   |

## Deals

#### Key fields

| Field           | Description                      |
| --------------- | -------------------------------- |
| id              | Unique deal identifier           |
| name            | Deal name                        |
| expected\_value | Monetary value of the deal       |
| probability     | Percentage likelihood of closing |
| milestone       | Current pipeline stage           |
| close\_date     | Expected close date              |
| owner           | Assigned sales rep               |
| contacts        | Linked contact records           |
| created\_time   | Deal creation timestamp          |

## Tasks

#### Key fields

| Field    | Description                              |
| -------- | ---------------------------------------- |
| id       | Unique task identifier                   |
| subject  | Task title or description                |
| type     | Task type (call, email, follow-up, etc.) |
| due      | Due date and time                        |
| status   | Open or completed                        |
| priority | Low, normal, or high                     |
| owner    | Assigned team member                     |

## Tickets

#### Key fields

| Field            | Description                               |
| ---------------- | ----------------------------------------- |
| id               | Unique ticket identifier                  |
| subject          | Ticket title                              |
| status           | Open, closed, resolved, etc.              |
| priority         | Urgency level                             |
| group            | Support group assigned                    |
| assignee         | Agent handling the ticket                 |
| requester\_email | Email of the person who raised the ticket |
| created\_time    | Ticket creation timestamp                 |
| updated\_time    | Last update timestamp                     |

## Common field combinations

Here are some useful ways to combine fields across entities:

* **Deal pipeline report** — Deals `name` + `milestone` + `expected_value` + `close_date` + `owner`
* **Contact engagement report** — Contacts `email` + `lead_score` + `tags` + `updated_time`
* **Support workload report** — Tickets `assignee` + `status` + `priority` + `created_time`
* **Campaign performance overview** — Campaigns `name` + `status` + `type` + `created_time`
* **Task completion tracking** — Tasks `subject` + `type` + `due` + `status` + `owner`

## Use cases by role

{% tabs %}
{% tab title="Sales teams" %}

* Track open deals by stage and owner to spot pipeline gaps
* Monitor lead scores to prioritize outreach
* Report on deal close rates and average deal values over time
* Use milestones data to analyze how deals progress through the pipeline
  {% endtab %}

{% tab title="Marketers" %}

* Pull campaign data into dashboards to compare performance across campaigns
* Analyze contact tags and lead scores to segment audiences
* Track new contact creation over time to measure inbound growth
* Cross-reference campaign data with deal creation to measure campaign-to-revenue attribution
  {% endtab %}

{% tab title="Support teams" %}

* Monitor open ticket volume, priority distribution, and resolution time
* Track tickets by assignee to balance team workload
* Use ticket filter data to replicate saved views in external reporting tools
* Identify trends in ticket creation to anticipate support demand
  {% endtab %}
  {% endtabs %}

## Platform-specific notes

* AgileCRM uses Unix timestamps for `created_time` and `updated_time` fields — you may need to convert these in your destination tool
* Custom fields defined in your AgileCRM account will appear in the data but field names may vary depending on your configuration
* The **Milestones** entity returns pipeline stage definitions, not individual deal stages — use the `milestone` field in Deals for per-deal stage data
* **Ticket filters** returns saved filter configurations, not the tickets themselves — use the **Tickets** entity to get actual ticket records
* Lead score values are cumulative and reflect all scoring activity up to the time of the sync