# Customer.io

![Customer.io_logo.svg](https://assets.relyanceuat.xyz/images/docs/12888021143181/12885792651021.svg)
Customer.io is an automated messaging platform for tech-savvy marketers who want more control and flexibility to craft and send data-driven emails, push notifications, in-app messages, and SMS.

In order to integrate Customer.io with Relyance AI you will need a **Tracking Site ID**, **Tracking API Key**, and **App API Key**.

#### In Customer.io:

1. Login to your Customer.io account.
2. In the left hand navigation click the **Account Settings** link below the **Settings** menu item.
3. Navigate to the **API Credentials** tab.
4. On the Tracking API Keys tab, click the **Create Tracking API Key** button.
5. Copy the **Site ID** and **API** to be used as the **Tracking Site ID** and **Tracking API Key** respectively.
6. Click on the **App API Keys** tab.
7. Click on the **Create an App API Key** button and assign it to the appropriate workspace. Copy this API Key to be used as the **App API Key**.

#### In the Relyance AI application:

1. Login to your Relyance account.
2. Navigate to the **Settings** Menu in the bottom left-hand side.
3. Select **Integrations**.
4. Click on the **Vendor Integration** tab.
5. Find the **Customer.io** integration card and click it to open its connections.
6. Under **Authentication Method**, choose **Custom**.
8. Select the **European Union (EU) data center** checkbox if using one.
9. Paste the **Tracking Site ID**, **Tracking API Key**, and **App API Key** into their respective fields.

![Customerio-1.png](https://assets.relyanceuat.xyz/images/docs/12888021143181/12885962350861.png)

10. Click **Authenticate**.
11. At this point, you should see the following result on the **Vendor** Integrations page:

![Customerio-2.png](https://assets.relyanceuat.xyz/images/docs/12888021143181/12885962350477.png)

12. Congratulations, you are now connected to **Customer.io**.

<!-- failure-modes:begin (generated from the integration catalog; do not hand-edit) -->

## If the connection reports Connected but returns nothing

These are the ways this integration comes back empty without reporting an error. Generated from the integration catalog, so it tracks what the connection actually asks for.

1. **A credential rotated at the vendor is not picked up here.** **Tracking API Key** and **App API Key** are stored when you save the connection, so regenerating the value at the vendor breaks the next scan until it is re-pasted here. Recording the expiry on the connection means Relyance warns you before it lapses.
2. **Check the address fields before suspecting the credentials.** **Tracking Site ID** identifies which tenant, region or host to talk to. A wrong value there fails authentication and looks exactly like a bad secret.

<!-- failure-modes:end -->

<!-- terraform-examples:begin (generated from the integration catalog; do not hand-edit) -->

## Manage this integration with Terraform

Connections for this integration can be managed as code with the [Relyance Terraform provider](https://registry.terraform.io/providers/Relyance/relyance/latest). Non-secret fields go in `auth.params`; secret fields go in `auth.secrets_wo`, which is write-only — never stored in Terraform state. Rotate secrets by bumping `auth.secrets_wo_version`.

```hcl
resource "relyance_integration_connection" "customerio" {
  vendor = "customerio"
  name   = "<your connection name>"

  auth = {
    method = "api-key"
    params = {
      tracking_site_id = "<tracking_site_id>"
      data_storage_location = "us"
    }
    # Secret fields are write-only: sent to Relyance, never stored in state.
    secrets_wo = {
      tracking_api_key = var.customerio_tracking_api_key
      api_key = var.customerio_api_key
      is_european_database = "false"
    }
    secrets_wo_version = 1
  }

  scans = { "data-inspection" = { enabled = true } }
}
```

<!-- terraform-examples:end -->