Overview

This guide provides a step-by-step walkthrough for syncing your customer data from Hightouch to Recurly Engage. By utilizing the Recurly Engage Ingest API, you can ensure your application has the most up-to-date user attributes—such as subscription plans, names, and custom tags—triggering more relevant user experiences and retention workflows.

Key benefits

• Automated Personalization: Keep user properties in Recurly Engage perfectly in sync with your source of truth (Snowflake, BigQuery, etc.) without manual uploads.
• Low-Code Integration: Use Hightouch’s flexible HTTP Request destination to connect to the Recurly Engage API without needing custom engineering resources.
• Real-Time Accuracy: Ensure that changes in a user’s status (e.g., upgrading from "Basic" to "Premium") are reflected immediately in your engagement campaigns.

Key steps

Step one: Create a New Destination

In your Hightouch dashboard, navigate to the Destinations page and click Add Destination. Search for and select HTTP Request.

Step two: Configure the HTTP Request

To establish the connection, enter the following configuration details:

• Authentication Method: Select Basic Auth.
• Base URL:https://conduit.redfast.com/ingest/property

Step three: Initialize a New Sync

Navigate to the Syncs page and click Add Sync. Select the Model containing the user data you wish to move into Recurly Engage.

Step four: Select the Destination

Choose the HTTP Request destination you configured in Step 2.

Step five: Configure Sync Mapping

While specific mapping depends on your data model, use these standard configurations for the payload:

Note: to find your API Key navigate to Settings > Application > API Key

Step six: Map the Request Body

Ensure your JSON payload matches the Recurly Engage requirements. Your mapping should generate a structure similar to this:

{
  "id": "123-456-789-012-",
  "user_id": "test-user-001",
  "properties": {
    "first_name": "Jane",
    "plan": "premium"
  }
}

Example response

{
  "success": true
}