> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/sales/callrail.md).

# CallRail

Connect CallRail to pull call volume, caller details, and conversation data into Google Sheets, BigQuery, or any warehouse via Coupler.io.

CallRail is a call tracking and analytics platform that helps businesses understand which marketing campaigns are driving phone calls and conversions. It gives you visibility into call volume, caller details, conversation quality, and team performance — all in one place.

Connecting CallRail to Coupler.io lets you pull your call and conversation data into spreadsheets, dashboards, or data warehouses without any manual exports. You can combine it with CRM or ad data to build a full picture of your marketing ROI.

**Why connect CallRail to Coupler.io?**

* Export calls, conversations, users, and companies to Google Sheets, Excel, BigQuery, or Looker Studio automatically
* Send call data to AI tools like ChatGPT, Claude, or Gemini for summaries, scoring, or trend analysis
* Join call data with ad spend or CRM records to measure true cost-per-lead
* Append data from multiple CallRail accounts into a single unified report

## Prerequisites

Before connecting, make sure you have:

* An active CallRail account (any paid plan)
* A CallRail API key — found in your account under **Settings > API Access**
* Read-level access to the data you want to export

## Quick start

{% hint style="success" %}
Start with the **Calls** entity to get your core call log data, then add Conversations in the same data flow if you need full transcript and messaging data alongside it.
{% endhint %}

## How to connect

{% stepper %}
{% step %}
**Create a new data flow in Coupler.io.** Log in to your Coupler.io account and click **Add data flow**. Search for **CallRail** and select it as your source.
{% endstep %}

{% step %}
**Enter your API key.** In CallRail, go to **Settings > API Access** and copy your API key. Paste it into the API key field in Coupler.io.
{% endstep %}

{% step %}
**Select an entity.** Choose what data you want to pull — Calls, Conversations, Users, or Companies. You can add more sources to the same data flow later.
{% endstep %}

{% step %}
**Set a start date.** Use the date picker to choose the earliest date you want data from. This controls how far back Coupler.io will pull records.
{% endstep %}

{% step %}
**Choose a destination.** Select where you want the data to go — Google Sheets, Excel, BigQuery, Looker Studio, or an AI destination like ChatGPT or Claude.
{% endstep %}

{% step %}
**Run the data flow.** Click **Run** to execute your first manual sync. Once it completes successfully, you can set up a schedule to keep data refreshing automatically.
{% endstep %}
{% endstepper %}

## Available entities

| Entity        | What it contains                                                        |
| ------------- | ----------------------------------------------------------------------- |
| Calls         | Individual call records with caller info, duration, source, and outcome |
| Conversations | Multi-channel conversation threads including calls, texts, and chats    |
| Users         | Team members and agents in your CallRail account                        |
| Companies     | Company records associated with your CallRail account                   |

## CallRail data overview

CallRail exposes four main entities through Coupler.io. The richest data lives in **Calls** and **Conversations** — these are the entities most teams will use for reporting, attribution, and performance analysis.

## Entities overview

| Entity        | Best for                                                             |
| ------------- | -------------------------------------------------------------------- |
| Calls         | Call volume reporting, lead tracking, marketing attribution          |
| Conversations | Omnichannel analysis combining calls, SMS, and live chat             |
| Users         | Auditing team members, mapping agents to call outcomes               |
| Companies     | Account-level segmentation for agencies or multi-location businesses |

## Calls

#### Call identification and timing

| Field       | Description                             |
| ----------- | --------------------------------------- |
| id          | Unique call identifier                  |
| start\_time | Timestamp when the call started         |
| duration    | Call length in seconds                  |
| answered    | Whether the call was answered           |
| first\_call | Whether this is the caller's first call |

#### Caller details

| Field           | Description                       |
| --------------- | --------------------------------- |
| caller\_name    | Name of the caller (if available) |
| caller\_number  | Caller's phone number             |
| caller\_city    | Caller's city                     |
| caller\_state   | Caller's state                    |
| caller\_country | Caller's country                  |

#### Attribution and tracking

| Field                   | Description                                  |
| ----------------------- | -------------------------------------------- |
| tracking\_phone\_number | The CallRail tracking number that was dialed |
| source                  | Traffic source (e.g., Google, Direct)        |
| medium                  | Marketing medium (e.g., organic, cpc)        |
| campaign                | Associated campaign name                     |
| keywords                | Search keywords that triggered the call      |
| landing\_page\_url      | Page the caller visited before calling       |
| referring\_url          | Referring URL                                |

#### Outcome and quality

| Field        | Description                        |
| ------------ | ---------------------------------- |
| lead\_status | Qualified lead status              |
| value        | Revenue value assigned to the call |
| note         | Agent notes on the call            |
| tags         | Tags applied to the call           |
| voicemail    | Whether a voicemail was left       |

## Conversations

#### Conversation metadata

| Field              | Description                           |
| ------------------ | ------------------------------------- |
| id                 | Unique conversation identifier        |
| created\_at        | When the conversation was created     |
| last\_activity\_at | Timestamp of the most recent activity |
| state              | Current state (e.g., open, closed)    |
| channel            | Channel type (call, sms, chat)        |

#### Contact and attribution

| Field                   | Description                             |
| ----------------------- | --------------------------------------- |
| customer\_name          | Name of the customer                    |
| customer\_phone\_number | Customer's phone number                 |
| source                  | Traffic source tied to the conversation |
| medium                  | Marketing medium                        |
| campaign                | Associated campaign                     |

## Users

| Field | Description                           |
| ----- | ------------------------------------- |
| id    | User ID                               |
| name  | Full name                             |
| email | Email address                         |
| role  | Account role (admin, reporting, etc.) |

## Companies

| Field      | Description               |
| ---------- | ------------------------- |
| id         | Company ID                |
| name       | Company name              |
| status     | Active or disabled        |
| time\_zone | Company time zone setting |

## Common metric combinations

* **Calls + source/medium/campaign** — see which channels are driving inbound calls
* **Calls + duration + answered** — measure call quality and missed call rates
* **Calls + landing\_page\_url + keywords** — connect SEO and PPC keywords to phone leads
* **Conversations + channel + state** — track open vs. closed conversations across channels

## Use cases by role

{% tabs %}
{% tab title="Marketers" %}

* Map calls to campaigns, keywords, and landing pages to calculate true cost-per-lead
* Combine CallRail calls data with Google Ads spend (via Coupler.io Join) to measure call conversion rates by campaign
* Send call source summaries to ChatGPT or Claude for automated channel performance commentary
  {% endtab %}

{% tab title="Sales teams" %}

* Track answered vs. missed calls by agent or time of day to optimize staffing
* Use the Conversations entity to monitor response times and open conversation queues
* Append call data from multiple CallRail accounts for a consolidated team leaderboard in Google Sheets
  {% endtab %}

{% tab title="Agencies" %}

* Use the Companies entity to segment reporting by client account
* Aggregate call volume and lead quality metrics across all managed accounts into a single BigQuery or Looker Studio dashboard
* Automate monthly call performance reports per company with scheduled data flows
  {% endtab %}
  {% endtabs %}

## Platform-specific notes

* CallRail's API returns data scoped to the account associated with your API key — if you manage multiple accounts, you'll need separate API keys and separate data flows or use Append to combine them
* Call duration is returned in seconds — you may want to create a calculated column in your destination to convert to minutes
* The `keywords` field is only populated for calls tracked via keyword-level tracking; it will be empty for number-only tracking
* Tags and lead status fields are only populated if your team actively applies them in CallRail
* Conversation data includes all channels (calls, SMS, chat) — filter by the `channel` field if you only want one channel type

## CallRail common issues

### Connection issues

<details>

<summary>My API key is rejected when connecting</summary>

Double-check that you're copying the full API key from **Settings > API Access** in CallRail — it's easy to accidentally trim characters. Also confirm the API key is enabled and hasn't been revoked. If you've recently regenerated your key, any existing data flows using the old key will need to be updated with the new one.

</details>

<details>

<summary>I see an authentication error even with a valid key</summary>

Make sure the CallRail account tied to your API key has API access enabled. Some CallRail plans restrict API usage — check your plan or contact CallRail support to confirm API access is active on your account.

</details>

### Missing data

<details>

<summary>Some calls are missing from my export</summary>

Check your **start date** setting in the data flow. If it's set too recently, historical calls before that date won't be included. Adjust the start date using the date picker and re-run the data flow. Also note that calls still in progress or very recently ended may not appear immediately due to processing delays on CallRail's side.

</details>

<details>

<summary>The keywords field is empty for most calls</summary>

Keyword-level data is only available if you have **keyword-level call tracking** enabled in CallRail for those tracking numbers. Calls tracked with a single pool number or static number won't have keyword data populated.

</details>

<details>

<summary>Conversation data is missing SMS or chat entries</summary>

The Conversations entity covers all channels, but older SMS or chat messages may not appear if they fall outside your start date range. Adjust the start date and re-run. Also confirm that SMS and chat features are enabled and active on your CallRail account.

</details>

### Permission errors

<details>

<summary>I can connect but only see partial data</summary>

Your API key inherits the permissions of the user account it belongs to. If that user has restricted access to certain companies or features, the API will only return data they can see. Use an API key from an admin-level account to access all data.

</details>

### Data discrepancies

<details>

<summary>Call counts in Coupler.io don't match the CallRail dashboard</summary>

CallRail's dashboard may apply default date filters or exclude certain call types (e.g., spam calls) that the API returns. Check whether your CallRail dashboard is filtering by a specific company, tracking number, or call status — and apply the same filters in your destination to align the numbers.

</details>

<details>

<summary>Call durations look wrong</summary>

Coupler.io returns call duration in **seconds** as provided by the CallRail API. The CallRail dashboard typically displays duration in minutes and seconds. Divide the raw value by 60 in your destination to convert.

</details>

### Rate limits

<details>

<summary>My data flow fails with a rate limit error</summary>

CallRail enforces API rate limits on a per-account basis. If you're running multiple data flows against the same account simultaneously, they may hit these limits. Stagger your scheduled data flows so they don't run at the same time, or reduce the frequency of refreshes on data flows that pull large date ranges.

</details>

## CallRail FAQ

<details>

<summary>Where do I find my CallRail API key?</summary>

Log in to CallRail and go to **Settings > API Access**. Your API key is listed there. If you don't see this option, your plan may not include API access — contact CallRail support to confirm.

</details>

<details>

<summary>Can I connect multiple CallRail accounts to one data flow?</summary>

Yes. Add each account as a separate source within the same data flow using its own API key, then use the **Append** transformation to combine the data into one table. This is especially useful for agencies managing multiple client accounts.

</details>

<details>

<summary>What's the difference between Calls and Conversations?</summary>

The **Calls** entity contains individual inbound and outbound call records. The **Conversations** entity is broader — it groups interactions across channels (calls, SMS, live chat) into threaded conversation records. Use Calls for pure call analytics and Conversations if you want a unified view of all customer touchpoints.

</details>

<details>

<summary>Can I pull data for a specific tracking number only?</summary>

CallRail's API doesn't support filtering by tracking number at the source level. Pull all calls and filter by tracking number in your destination (e.g., using a filter in Google Sheets or a WHERE clause in BigQuery).

</details>

<details>

<summary>Why are some calls showing no source or campaign data?</summary>

Source, medium, and campaign fields are only populated when CallRail's JavaScript snippet is active on your website and the caller arrived via a tracked session. Direct calls to a static number — or calls where the session wasn't tracked — won't have attribution data.

</details>

<details>

<summary>Can I use CallRail data with AI tools?</summary>

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw. You can route your call or conversation data directly to these tools for summarization, lead scoring, trend analysis, or automated reporting commentary.

</details>

<details>

<summary>How far back can I pull historical call data?</summary>

There's no hard limit set by Coupler.io — use the date picker in the **Start date** field to set how far back you want to go. Very large date ranges covering years of high-volume call data may take longer to process on the first run.

</details>

{% hint style="info" %}
For details on what fields are available in each entity, see [Data Overview](#callrail-data-overview). If your data flow isn't returning expected results, check [Common Issues](#callrail-common-issues) for troubleshooting steps.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.coupler.io/sources/category/sales/callrail.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
