---
title: "CanopyDeploy (Clang) setup for Data Activation"
slug: "canopydeploy-clang-setup-for-data-activation"
description: "Learn how to configure your CanopyDeploy (Clang) connection for Data Activation."
updated: 2026-02-27T12:48:45Z
published: 2026-02-27T13:25:42Z
---

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

# CanopyDeploy (Clang) setup for Data Activation

The Data Activation connector for CanopyDeploy (previously known as Clang) empowers you to seamlessly integrate customer data with this robust marketing automation platform. By connecting these systems, you can deliver hyper-personalized, automated campaigns across email and other channels, driving better engagement and ROI.

Here's how this integration adds value:

- **Personalized marketing at scale**: Use detailed customer profiles to create highly targeted and personalized campaigns in CanopyDeploy, ensuring relevance and resonance.
- **Real-time data activation**: Sync data dynamically between systems, enabling real-time updates for audience lists and automated workflows.
- **Behavior-driven campaigns**: Trigger personalized communications based on real-time customer actions, such as purchases, abandoned carts, or product browsing.
- **Cross-channel consistency**: Integrate CanopyDeploy campaigns into broader cross-channel strategies, ensuring cohesive messaging across all customer touchpoints.
- **Optimize campaign performance**: Use insights and analytics to refine targeting, messaging, and timing, driving higher engagement and conversions.
- **Automated lifecycle management**: Deliver lifecycle-based campaigns, from onboarding to loyalty programs, by combining segmentation capabilities with CanopyDeploy's automation features.
- **Increased efficiency**: Automate data syncs and workflows, reducing manual effort and freeing up resources to focus on strategic marketing initiatives.

## Destination connector overview

| Attribute | Value |
| --- | --- |
| **Platform type** | ESP |
| **PartnerType Slot** | 1020 (Customer ID), 1022 (Hashed Email) |
| **Cookie Sync** | No |
| **Connecting protocol** | REST/SOAP (SOAP for campaign list) |
| **Real-time data sync** | No |
| **Syncs Data On** | Add, Update, Remove |
| **Allowed setting multiple connectors** | Yes |
| **API Documentation** | [CanopyDeploy REST API](https://docs.canopydeploy.net/cdnl/files/78686993/78686994/1/1603222558351/clang-data-model-rest-api-user-manual.pdf#page=4) |

## Before you begin

There are two types of CanopyDeploy integrations available:

- **Real-time integration** using the SOAP API
- **Batched integration** using the REST API

**Which integration to use:**

The advice is to always use the REST API integration since it can handle bigger volumes of data. The only reason to use the SOAP API integration is if it's mandatory to send the email in real-time. Otherwise, data is sent every 20 minutes or when the batch hits 100 profiles.

### Supported features

The CanopyDeploy integration supports the following features:

- Add new profiles to a campaign
- Delete profiles from a campaign (needs to be set up specifically in the CanopyDeploy campaign)
- Modify data for a campaign (needs to be set up specifically in the CanopyDeploy campaign)
- Send data fields from the Data Activation to CanopyDeploy
- Automatically receive engagements (if the Data Activation app has been configured in the CanopyDeploy store)

### Engagements received

When the Data Activation app within CanopyDeploy has been configured, five types of engagements are sent back:

- Email Click
- Email Open
- Email Receive
- Email Bounce
- Email Complaint

These engagements have the following properties:

- campaignId (all)
- brandId (all)
- mailingType (all)
- contentName (all)
- linkHref (Email Click only)
- linkDescription (Email Click only)

You need to configure these engagements within the Data Activation interface.

## Instructions

### REST API configuration (recommended)

**Before you begin**

- CanopyDeploy Token (used for all authenticated calls)
- Identifier type (Hashed email or Customer ID, should have already been collected in the DMP)
- Webhook URL (credentials for CanopyDeploy Store to create new webhook)

**Step 1:**

To enable the synchronization of segments with CanopyDeploy, log in to CanopyDeploy Store, and create a new webhook to receive data from the Data Activation.

**Step 2:**

1. On the Data Activation platform, select **Connectors** in the left-side navigation bar.
2. Select **Server to Server** and click **New Connector**.
3. Select **CanopyDeploy** and fill in the following information:
  - **Name**: Display name of the partner Server to server integration, used throughout the Data Activation system
  - **Token**: Token generated by the CanopyDeploy platform (found under **Administration → Users → select User → Manage tokens**). Also available in the webhook URL after "`?token=`"
  - **Endpoint**: Endpoint known by CanopyDeploy platform. Enter only the URL without the "`?token=`" part (store token separately in the Token field)
  - **Identifier type**: Customer ID (internal identifier) or Hashed email (SHA256 hashed email)

> [!NOTE]
> Note
> 
> Partner number 1020 is the default when using Customer ID and 1022 when Hashed Email is selected.

**Advanced settings** allow you to set any partner number instead of the default.

### SOAP API configuration (real-time only)

Use the SOAP API only if:

- A short delay is not an option
- The amount of profiles is nicely spread across the day

**Before you begin**

- Endpoint (Secure or Login depending on the given token)
- CanopyDeploy Token (used for all authenticated calls)
- Identifier type (Hashed email or Customer ID, should have already been collected in the DMP)

> [!NOTE]
> Note
> 
> Partner number 1010 is default when using Customer ID and 1012 when Hashed Email is selected.

### Store mapping tag

A store-mapping tag must be fired using the TMS to specify how to identify the user. CanopyDeploy expects a valid SHA-256 email hash or customer ID.

1. In Data Activation, navigate to **Tags** and select **Pages**.
2. On the Global path, click the **+ button** to create a new tag.
3. Search for **Store mapping**.
4. Click **Relay42 Data** and choose **Store mapping**.
5. Select **CanopyDeploy (Hashed Email)** from the list.
6. In the Value input field, enter the encrypted email using SHA-256 encryption.

## Error handling

For the CanopyDeploy connector, we report the actual error codes of CanopyDeploy.

For CanopyDeploy-specific errors, see the [CanopyDeploy API documentation](https://docs.canopydeploy.net/cdnl/files/78686993/78686994/1/1603222558351/clang-data-model-rest-api-user-manual.pdf) (chapter 4.3 onwards) or check with your CanopyDeploy representative.

The following error codes are Data Activation-related:

- Timeout
- Other error
- Invalid credentials

To read more about these errors, see [Using journey and audience connectors](/v1/docs/using-audience-and-journey-connectors).

## More resources

- [How to build audiences](/v1/docs/how-to-build-audiences)
- [How to build journeys](/v1/docs/how-to-build-journeys)
- [How to measure goals and outcome signals](/v1/docs/how-to-measure-goals-and-outcome-signals)