> 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/faq.md).

# 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](/sources/category/sales/callrail/data-overview.md). If your data flow isn't returning expected results, check [Common Issues](/sources/category/sales/callrail/common-issues.md) 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 dynamically by asking a question.

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

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.