> ## 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 Branch data source to Adriel: gather a Branch app key, secret, and app ID, then enter them to import attribution and event data.

Branch is a mobile measurement partner (MMP) and deep-linking platform that attributes installs, app opens, and in-app events across mobile ad networks, deep links, email, and owned channels. Connecting it brings clicks, installs, opens, purchases, cost, and standard or custom in-app events into Adriel dashboards, grouped by Branch's attributed campaign, ad set, ad, creative, keyword, and advertising partner.

## Before you connect

The following are required:

* A Branch dashboard account with API access.
* A **Branch app key** (sometimes labeled "account key") — typically 32+ characters, beginning with `key_live_…` or `key_test_…`.
* The matching **Branch API secret**.
* The **Branch app ID** for the app to connect.

To gather these values, log in to the [Branch dashboard](https://dashboard.branch.io), open **Account Settings** in the left bar, and go to **Profile**. The **Key** and **Secret** are listed there, and the **Branch app ID** appears directly below them on the same page.

## Connect Branch

<Steps>
  <Step title="Open the Branch data source">
    On the **Data Sources** page, search for **Branch** and select it.
  </Step>

  <Step title="Enter the key and secret">
    Fill in the **Key** and **Secret** gathered from the Branch dashboard. Keys shorter than 10 characters are rejected — re-copy the full value from Branch if validation fails.
  </Step>

  <Step title="Submit the credentials">
    Click **Submit** to proceed to the data source settings.
  </Step>

  <Step title="Configure the data source">
    Fill in the **Account ID** with the Branch app ID, then set an **Account Name** to distinguish among multiple Branch data sources.
  </Step>

  <Step title="Submit">
    Click **Submit** to complete the connection. Initial data availability can take up to one business day. The first sync backfills the previous 180 days, and subsequent refreshes run daily and update the most recent 5 days.
  </Step>
</Steps>

## What gets imported

The connector reads daily attribution and performance data for the connected Branch app: clicks, installs, opens, purchases, cost, and standard or custom in-app events. Reports arrive at daily granularity with 12 attribution breakdowns — campaign, ad set, ad, creative, keyword, and advertising partner, plus matching ID variants and link tags — all derived from Branch's `last_attributed_touch_data_tilde_*` fields. Custom in-app events defined in Branch appear automatically the first time they fire.

For the complete metric list, breakdown-to-field mapping, refresh cadence, and limits, see the [Branch data reference](/data-sources/a-f/branch/data-reference).

## Troubleshooting

<AccordionGroup>
  <Accordion title="App key is too short">
    Branch app keys are typically 32+ characters; the connector rejects values under 10. Re-copy the full key from the Branch dashboard under **Account Settings → Profile**.
  </Accordion>

  <Accordion title="INVALID_CREDENTIALS error">
    The app key and secret do not match, or one has been rotated in Branch. Regenerate or reconfirm both values in the Branch dashboard, then update the data source.
  </Accordion>

  <Accordion title="Some days show no data">
    Branch does not return rows for date and breakdown combinations with no activity, and the connector does not add empty rows. A campaign with no events on a given day is absent rather than reported as zero. Confirm in the Branch dashboard that the campaign was active for the date in question.
  </Accordion>

  <Accordion title="Breakdown values appear as unknown">
    When Branch cannot attribute an event to a specific value for a breakdown, the literal string `unknown` is stored to keep groupings consistent in dashboards. A large `unknown` group usually points to traffic Branch could not attribute to a specific campaign or creative.
  </Accordion>

  <Accordion title="Backfills are slower than expected">
    Branch enforces 150 API requests per rolling hour, shared across all Branch data sources in the same process. Long backfills with many breakdowns can queue once usage crosses the 135-request safety buffer, then resume after the hour resets.
  </Accordion>
</AccordionGroup>

## Related

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

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

  <Card title="How to connect AppsFlyer" href="/data-sources/a-f/appsflyer/how-to-connect">
    Connect AppsFlyer, an alternative MMP with broader event coverage.
  </Card>

  <Card title="How to connect Adjust" href="/data-sources/a-f/adjust/how-to-connect">
    Connect Adjust, another mobile measurement partner.
  </Card>
</CardGroup>