Connect this destination to export audience membership onto a Recurly Engage user trait, or to write warehouse rows onto other user traits, for use in Pulse segments and prompts.

This destination writes to your Recurly Engage account and is a good fit when you want to:

Match Engage users on User ID (visitor_id)
Use Pulse segments or prompts with GrowthLoop audience membership or warehouse traits

This maps to GrowthLoop Audiences, Journeys, and Syncs:

Use it for	Audiences	Journeys	Syncs
Writing audience membership to a Recurly Engage user trait	✓	✓
Creating or updating Recurly Engage user traits from a warehouse table			✓

Audience exports manage membership on the Audience Attribute trait. Syncs write other mapped traits. They do not add or remove audience membership.

Prerequisites

Make sure you have:

A Recurly Engage (Pulse) account with Application access.
Your Application ID and API Key. In Pulse, open Settings → Application.
A user trait for audience membership. GrowthLoop defaults to growthloopaudience. Create it in Pulse under Settings → User Traits as a string trait with multi-select display before you export.
A stable Engage user ID in your warehouse that matches the identifier used by the Engage JS tag or SDK (visitor_id).

📘
Note
GrowthLoop can write a new trait key, but Pulse will not show it in segments until you create that trait under Settings → User Traits and set its data type and display options.

Set up Recurly Engage as a destination

In GrowthLoop, click the Destinations tab on the left sidebar.
Click New Destination in the top right corner.
Search for Recurly Engage and click Add Recurly Engage.
Enter the required information, then click Create.

Field	Description
Destination Name	Name this destination in GrowthLoop. Use a name so your team recognizes its purpose, like "Recurly Engage".
Sync Frequency	Set the default export frequency (for example, daily or weekly). You can override this setting for individual exports and syncs.
Application ID	Recurly Engage application ID from Settings → Application.
API Key	Recurly Engage API key from Settings → Application → API Key.
Base URL	Conduit host. Leave `https://conduit.redfast.com` unless Recurly gives you another URL.
Prefix for Personalization Fields (optional)	Prefix GrowthLoop adds to personalization fields, then strips before writing the Recurly trait. The default value is `fw`. Leave this blank for no prefix. If you set one, it must start with a letter and use up to 5 letters or numbers.
Audience Attribute	User trait that stores audience membership. Defaults to `growthloopaudience`. Use the same name you created in Pulse.

GrowthLoop validates the Application ID. Recurly Engage then appears in your list of connected destinations.

Export to Recurly Engage

From within GrowthLoop, export from an audience or from a journey Destination Node. See Export an audience or Build a journey if you need more information on these steps.

After building or selecting an audience, click Export, then search for Recurly Engage. In a journey, add a Destination Node under Email and select Recurly Engage.

Map identifiers

On an audience or in a journey Destination Node, map User ID. This field is required. Use the Engage visitor_id.

You can also map additional fields, including custom attributes from the audience or from the journey. GrowthLoop writes those as user traits.

Configure the export

This is where you set the campaign type and schedule for audience exports. On a journey Destination Node, you set timing on the journey canvas.

Setting	Audience export	Journey Destination Node
Export Name	Defaults to `{audience name}_GL_Audience_{audience ID}`. GrowthLoop writes that name onto the Audience Attribute.	Required. Enter a name so you can find the export in GrowthLoop. GrowthLoop writes that name onto the Audience Attribute.
Campaign type	Choose a one-time or ongoing export.	The journey schedule controls when the journey runs and contacts are sent to Recurly Engage.
Export Inclusion Criteria	All audience members for a full refresh, or Newly added audience members for additions and removals since the last export.	The journey sends contacts who reach this node.
Schedule	Set frequency, start date, end date, and days of the week for ongoing exports.	Users reach this node when the journey runs. Add a Delay Node or set Criteria Evaluation to control timing.
Personalization fields	Optional. GrowthLoop writes these as user traits.	Optional. GrowthLoop writes these as user traits.

Export behavior

This is what GrowthLoop writes when you export an audience.

Behavior	What happens
What GrowthLoop writes	Audience membership on the Audience Attribute user trait, plus any mapped personalization traits. Direction is GrowthLoop → Recurly Engage.
When it runs	GrowthLoop sends the export as a batch on the next successful run. An export that starts Now runs within about 15 minutes. Journeys send exports on demand when users reach the Destination Node.
Match field	User ID.
Adds	GrowthLoop appends the export name to the audience attribute. If the user is in more than one exported audience, the trait is a comma-separated list.
Removes	GrowthLoop removes that export name from the trait. The trait is empty when no exported audiences remain.
Personalization	Mapped additional fields write as user traits on add. GrowthLoop strips Prefix for Personalization Fields before writing the trait name.
New users	Users that do not yet exist in Engage are created when GrowthLoop writes traits.
One-time exports	GrowthLoop sends current membership once, or the additions and removals since the last export if you chose that inclusion setting.
Ongoing adds and removals	Ongoing exports add contacts who enter the audience and remove contacts who leave.
Deletes	GrowthLoop does not delete Recurly Engage users.

Create a sync in GrowthLoop

Create a sync from a warehouse table to write rows onto Recurly Engage user traits. See Syncs for information on how to complete those steps.

Select an Object Type:

Object	Use it for	Sync modes
User	Create or update Engage user traits	Insert, Update, or Insert or update

When you configure the sync:

Connection: Select your Recurly Engage destination.
Object Type: Select User.
Update Rule: Choose Insert, Update, or Insert or update. GrowthLoop writes mapped traits with an ingest upsert in every mode. See Sync behavior.
Dataset/Table: Select the warehouse table that holds the records.
Match Field: Map User ID.

After you map fields, click Save Sync or Update Sync. Enable the sync with the toggle at the top of the page.

The mapping UI lists User ID as a built-in field. Type every other Pulse trait name in the destination field. Names must match Settings → User Traits for your Engage application.

Syncs write traits. They do not add or remove audience membership. To manage membership, export an audience.

User fields

Destination field	Required	Description
User ID	Yes	Engage `visitor_id`
Additional Pulse trait names	No	Type the exact trait name from Settings → User Traits

Sync behavior

Behavior	What happens
When it runs	GrowthLoop sends the sync as a batch on the next successful run.
Insert, Update, and Insert or update	GrowthLoop writes mapped traits. New users are created when GrowthLoop writes traits. Existing users are updated.
Match field	User ID.
Audience membership	Syncs do not add or remove names on the Audience Attribute.
Deletes	GrowthLoop does not delete Recurly Engage users.

Rows without User ID fail.

Confirm the export was successful

When the run finishes, confirm you can use the data in Recurly Engage.

Audience export: Open Pulse User Lookup, enter a User ID from the export, and look up the Audience Attribute. It should contain the _GL_Audience_ name unless you changed Export Name.
Journey Destination Node: Open User Lookup and look up a user who reached the node. Confirm the Audience Attribute includes the export name.
User sync: Search User Lookup for the user and check the mapped traits.

In GrowthLoop, review counts on the audience Exports tab, open the Activity tab on the journey Destination Node, or confirm the sync appears in the Syncs table. See Export an audience, Monitor a journey, or Syncs for more information.

Congrats on successfully exporting to Recurly Engage!

Troubleshooting

These are the issues we see most often. You can always email us at [email protected] for help.

Problem	Cause	Resolution
Connection fails to validate	Application ID or API Key is wrong, or Base URL is not the Conduit host Recurly gave you	Confirm Settings → Application in Pulse. Leave the default Base URL unless Recurly provided another
Rows fail to export or sync	User ID is not mapped	Map User ID to the Engage `visitor_id`
You cannot find membership in Pulse	The Audience Attribute trait was not created, or you are searching for the unsuffixed audience name	Create the trait under Settings → User Traits, then search User Lookup for the `_GL_Audience_` export name
A segment cannot use the trait	GrowthLoop wrote the key, but the trait is not created in Pulse with a data type and display options	Create the trait under Settings → User Traits
A sync did not change audience membership	Syncs write other traits only	Export an audience to add or remove names on the Audience Attribute

Prerequisites

Note

Set up Recurly Engage as a destination

Export to Recurly Engage

Map identifiers

Configure the export

Export behavior

Create a sync in GrowthLoop

User fields

Sync behavior

Confirm the export was successful

Troubleshooting

What’s Next