Custom destinations

​

Before you begin

• Prepare data for AID
• A destination connected in Hightouch (such as HTTP Request)

​

Overview

• Your destination doesn’t have a purpose-built AI Decisioning integration.
• You deliver through middleware you already own, such as a Lambda or an internal service.
• You want to write decisions to a warehouse, object store, or other system for downstream processing.

​

How custom channels differ from managed channels

• You build and own the delivery sync. AI Decisioning writes each agent’s decisions to a Hightouch model. You create a normal sync from that model to your destination, and you own its schedule and monitoring.
• Message content lives in Hightouch. You author each message’s content as variables in AI Decisioning. There’s no destination template to select.

1

Connect your destination

Connect the destination you want AI Decisioning to send to. For a raw HTTP endpoint, add the HTTP Request destination, where you configure the base URL, authentication, and headers for your API.Store API keys and tokens in the destination’s authentication or headers, not in the request body.You’ll configure the request method and payload later, when you build the delivery sync.

2

Add a custom channel

A channel connects an agent’s decisions to a destination.

1. Go to AI Decisioning > Configuration > Channels.
2. Select Add channel.
3. For the channel type, select Custom (“Send personalized decisions to any destination in our catalog”).
4. Select your destination.
5. Select an identifier — the user column that identifies the recipient, such as email or user_id. This becomes the external_id column in the model AI Decisioning writes to.
6. Select Add channel, then select the channel and select Save changes.

A configured custom channel shows the destination, identifier, eligibility filters, and tags:

Custom channels don’t apply a channel tag automatically. To enable frequency limits, add a channel name tag to the channel. See Tags.

3

Add messages

Each message defines the content an agent can send. For a custom channel, you author the content directly in Hightouch as variables.

1. Go to AI Decisioning > Agents and select your agent.
2. Open the Messages tab.
3. Add a message and select your custom channel and destination.
4. In the Content tab, define the message’s variables (for example, subject and body) and add variants.

Each variable you define appears in the delivery sync inside the hightouch_recommendation column. For full details on messages, variants, and tags, see Messages.

4

Build the delivery sync

When you enable the first message on a custom channel, AI Decisioning creates a model that holds each agent’s decisions. Build a sync from that model to your destination, mapping its columns into the request your destination sends.

​

Available columns

The model exposes a fixed set of columns:

Column	Type	Description
external_id	String	The recipient identifier, taken from the identifier column you selected on the channel.
id	String	A unique identifier for the decision.
campaign_id	String	The campaign identifier, used for attribution.
message_id	String	The message the agent selected.
send_at	Timestamp	When the agent recommends sending.
hightouch_recommendation	JSON	The agent’s decision, including a variables object with your message content.
hightouch_user	JSON	The recipient’s synced warehouse columns.

​

Map your message content

hightouch_recommendation and hightouch_user are JSON columns. To read a value, parse the column and reference the field you want.For the HTTP Request destination, build the request body to match what your API expects. This example reads the recipient identifier, the campaign, and two message variables:

{% assign parsedRecs = row['hightouch_recommendation'] | parse %}
{
  "user_id": "{{ row['external_id'] }}",
  "campaign": "{{ row['campaign_id'] }}",
  "subject": "{{ parsedRecs['variables']['subject'] }}",
  "body": "{{ parsedRecs['variables']['body'] }}"
}

Use the same pattern for any variable you defined on the message: parsedRecs['variables']['<variable name>']. To read a synced user column, parse hightouch_user the same way.To hand your API the entire decision instead of individual fields, pass the hightouch_recommendation column through as a JSON object and transform it in your own service.For the full set of request options — method, path, authentication, headers, rate limits, batching, and error handling — see the HTTP Request destination.

5

Schedule and validate

1. Set the sync schedule to match how often your agent makes decisions.
2. Run the sync on a small test group first. Confirm your endpoint receives requests in the expected shape before enabling it broadly.
3. Enable the sync.

A successful sync means your endpoint accepted the request. It doesn’t confirm the message reached the user — check your destination’s own delivery logs for that.

To compare agent performance against your existing campaigns, map a consistent value into campaign_id and use campaign attribution. Attribution matches on exact text, so Summer_Push and summer_push are treated as different campaigns.

​

Manage messages with the API

curl -X POST 'https://api.hightouch.com/api/v1/decision-engine/flow/{flowId}/messages' \
  -H 'Authorization: Bearer YOUR_API_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{
    "name": "Recommended offer",
    "channelId": "YOUR_CHANNEL_ID",
    "config": { "baseMessageId": "recommended-offer" },
    "variables": [
      {
        "name": "subject",
        "variants": [{ "value": "A gift for you" }, { "value": "Welcome back" }]
      }
    ]
  }'

curl -X POST 'https://api.hightouch.com/api/v1/decision-engine/flow/{flowId}/run' \
  -H 'Authorization: Bearer YOUR_API_TOKEN'

​

Troubleshooting

​

Next steps

• Messages to author the content and variants your custom channel delivers.
• HTTP Request destination for the request options you configure on the delivery sync.
• QA guide to validate messages before you launch.
• Hightouch API reference to manage messages and trigger runs programmatically.