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

# How to connect

> How to connect the CallRail data source to Adriel: retrieve a CallRail API v3 key, enter it, and select an account and data type.

CallRail is a call-tracking and lead-intelligence platform that assigns trackable phone numbers and web forms to marketing sources and attributes inbound calls and form submissions back to the channel, campaign, or keyword that drove them. Connecting it brings call records, form submissions, and tracker configuration into Adriel dashboards alongside ad-platform spend, making it possible to attribute phone-call and form-lead outcomes to the campaigns that produced them.

## Before you connect

The following are required:

* A CallRail account with access to account settings.
* A CallRail **API v3 Key**.
* At least one configured company and tracker in CallRail.

## Connect CallRail

<Steps>
  <Step title="Retrieve the CallRail API key">
    Sign in to CallRail. Click the **Settings** icon in the left navigation bar and select the company to connect. Click **Integrations** at the top of the page, then click **API Keys** under the **Data Access** header. Click **Create New API v3 Key** to generate a new key (existing keys can be reused if available), and copy it for the next step.
  </Step>

  <Step title="Enter the API key in Adriel">
    On the **Data Sources** page, search for **CallRail** and select it. Under **Connection settings**, enter the **API Key** retrieved from CallRail, then click **Submit** to proceed.
  </Step>

  <Step title="Configure the data source">
    Under **Data source settings**, fill in the required fields for the account being connected:

    * **Name**: an identifiable name for the data source. This helps distinguish multiple CallRail data sources.
    * **Ad Account**: select the account to connect. Multi-selection is supported, but selecting a single account per data source is recommended since each data source shares one name.
    * **Data Type**: select one type from the dropdown list.
  </Step>

  <Step title="Scope the import (optional)">
    To limit the import, fill in the optional filter fields:

    * **Filter Field**: any field name to filter by (for example, `Company`).
    * **Filter Operator**: select **IN** or **LIKE** from the dropdown.
    * **Filter Values**: the value of the field (for example, `Adriel`).

    Selecting `Company` — `IN` — `Adriel` produces a data source filtered to rows under the Adriel company.
  </Step>

  <Step title="Submit">
    Click **Submit** to complete the connection. The initial sync backfills recent call logs in the background.
  </Step>
</Steps>

## What gets imported

The connector imports per-call and per-form-submission records along with company and tracker configuration. Around 140 fields cover call core attributes, customer details, attribution fields, click-identifier passthroughs (gclid, fbclid, msclkid), UTM parameters, CallScribe transcription and sentiment data, and form-capture payloads.

For the complete field list, see the [CallRail data reference](/data-sources/a-f/callrail/data-reference).

## Troubleshooting

<AccordionGroup>
  <Accordion title="Calls are missing source or campaign attribution">
    Attribution requires an active tracker session at the time of the call. Calls placed to a default number, or after the tracker session has expired, return without source, medium, or campaign values. Confirm that dynamic number insertion is enabled on the landing pages driving traffic.
  </Accordion>

  <Accordion title="Recordings or transcripts appear blank for recent calls">
    CallRail produces recordings, transcriptions, and sentiment asynchronously after a call ends. The daily refresh re-fetches the last five days of calls specifically to backfill these fields. Wait for the next refresh cycle before reporting on transcripts for calls placed in the previous 24 hours.
  </Accordion>

  <Accordion title="New trackers do not appear immediately">
    Tracker, company, and tag catalogs refresh every four hours. Newly provisioned trackers become available within that window.
  </Accordion>

  <Accordion title="Form submissions and calls cannot be combined in a single widget">
    Form submissions and call records use separate underlying datasets. Reports that need both should be split into two widgets or aggregated at the campaign level.
  </Accordion>
</AccordionGroup>

## Related

<CardGroup cols={2}>
  <Card title="CallRail data reference" href="/data-sources/a-f/callrail/data-reference">
    Metrics, breakdowns, and limits for CallRail.
  </Card>

  <Card title="CallRail FAQs" href="/data-sources/a-f/callrail/faqs">
    Common questions and expected behaviors for the CallRail data source.
  </Card>

  <Card title="How to connect Google Ads" href="/data-sources/g-n/google-ads/how-to-connect">
    Join call attribution with paid-search spend.
  </Card>

  <Card title="How to connect Meta Ads" href="/data-sources/g-n/meta-ads/how-to-connect">
    Join call attribution with paid-social spend.
  </Card>
</CardGroup>