# Campaign Monitor

![campaign-monitor-vector-logo.png](https://assets.relyanceuat.xyz/images/docs/34562256509837/34562256508301.png)
Campaign Monitor is an email marketing platform that enables marketers to send beautiful and personalized emails through its ease-of-use interface. It allows businesses to start emailing quickly, tracks the customer journey, and helps automate the process.

In order to integrate Campaign Monitor with Relyance AI you will need an **API Token**.

#### In Campaign Monitor:

![CampaignMonitor-4.png](https://assets.relyanceuat.xyz/images/docs/34562256509837/34562222351373.png)
1. Login to your Campaign Monitor account.
2. Click on your account menu in the top right-hand menu.
3. Select **Account settings**.
4. Click the **API keys** link.
5. Click on **Generate API key** or **Show API key**.
6. Copy this **API Token** to be used in Relyance AI.

![CampaignMonitor-3.png](https://assets.relyanceuat.xyz/images/docs/34562256509837/34562256508941.png)

#### In the Relyance AI application:

1. Login to your Relyance AI account.
2. Navigate to the **Settings** (bottom-left corner).
3. Select **Integrations**.
4. Search and locate the **Campaign Monitor** integration card and click on it.
5. Click on the **Add Connection** button on the top right.
6. Provide a meaningful name for the integration and click on the **Add** button.
7. In the **Overview** section, select the integration features you wish to enable for the integration, review the **Scope and Permission**, and **Endpoint** details and click on **Continue**. For more details, see [Integration Features](/docs/introduction-to-relyance-ai/integration-features/).
8. In the **Connection** section, provide the appropriate values and click on **Continue**,
    - **Connection Name**: This property allows you to update the integration specified in Step 6. If you have multiple integrations for the same vendor, you may want to assign distinct names to each. This helps streamline filtering by **Discovery Source** across the **Inventory**, **Visual** **Maps**, **Assets**, and **Data Flow Analysis** pages.
    - **Rescan Frequency**: This property allows you to configure how often Relyance executes scans against this Vendor connection.
    - **Business Atlas Associations** (required): the business entities or products that newly discovered third parties, services and assets from this integration are attributed to. Choose at least one from the **Select Associations** dropdown — the wizard will not advance past this step without one. For more details, see [Business Atlas](/docs/other-settings/business-atlas-overview/).
9. In the **Authentication** section, provide the **Campaign Monitor API Token** information retrieved from the **Campaign Monitor** section and click on **Continue**.
10. This step applies only if the **Data Inspection** check box was enabled in Step 7. In the Data Inspection section, provide the appropriate values and click on **Continue**,
    - **Minimum Confidence Level:** This property adjusts the sensitivity of the Data Inspection feature. Lower likelihoods (e.g., unlikely) offer more coverage but may produce false positives, while higher sensitivity (e.g., very likely) provides greater accuracy but less coverage.
11. Review the configuration summary from the **Completion** section and click on **Finish.**
12. Confirm the integration Status reflects **Connected.**

![Screenshot](https://assets.relyanceuat.xyz/images/docs/34562256509837/34592213218829.png)

![Screenshot](https://assets.relyanceuat.xyz/images/docs/34562256509837/34562222351629.png)

![Screenshot](https://assets.relyanceuat.xyz/images/docs/34562256509837/34562222351885.png)

![Screenshot](https://assets.relyanceuat.xyz/images/docs/34562256509837/34562222352013.png)

![Screenshot](https://assets.relyanceuat.xyz/images/docs/34562256509837/34562256509325.png)

![Screenshot](https://assets.relyanceuat.xyz/images/docs/34562256509837/ext-9ec2966a1e.png)

<!-- 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 feature you enabled returns nothing.** Some scopes belong to a feature rather than to the connection: **Data subject requests** needs `ManageLists`, `ViewReports`, `AdministerPersons`, `AdministerAccount`. Turning the feature on after the connection exists does not widen the grant it already holds, so re-authenticate the connection.
2. **Authorised, then empty.** The connection carries an authorisation, not a password: it stops returning data if the account that granted it loses access, its own permissions narrow, or the grant is revoked at the vendor. None of that reports an error here -- the connection keeps its last status until the next scan.
3. **A credential rotated at the vendor is not picked up here.** **CampaignMonitor API Token** is 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.

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

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

## Authentication methods and fields

Pick one of these under **Authentication Method** on the connection wizard's **Authentication** step. This table is generated from the integration catalog, so it always matches what the form actually asks for.

| Method | Required | Optional |
| --- | --- | --- |
| **Custom** | `CampaignMonitor API Token` (secret) | — |
| **OAuth2** | — | — |

<!-- auth-methods: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`.

### API key

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

  auth = {
    method = "api-key"
    params = {
      data_storage_location = "us"
    }
    # Secret fields are write-only: sent to Relyance, never stored in state.
    secrets_wo = {
      API_KEY = var.campaign_monitor_api_key
    }
    secrets_wo_version = 1
  }

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

### OAuth (browser authorization)

The **OAuth (browser authorization)** method uses a browser authorization flow, so the connection is created in the Relyance app. Manage it in Terraform afterwards by importing it (`terraform import relyance_integration_connection.example campaign_monitor/<connection_id>`) or reading it with the `relyance_integration_connection` data source.

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