Recurly Engage
Learn how to set up Recurly Engage as a destination for audience exports and user-trait personalization.
Use Recurly Engage as a GrowthLoop destination to export Audiences as membership on a custom user trait, and to keep warehouse attributes synced as Engage traits for Pulse segments and prompts.
Prerequisites
Before you connect Recurly Engage to GrowthLoop, make sure you have:
- A Recurly Engage (Pulse) account with Application access.
- Your Application ID and API Key from Settings → Application.
- A user trait in Recurly Engage for audience membership. GrowthLoop defaults to
growthloopaudience, but your team can use a different name when configuring the destination. - A stable Engage user id in your warehouse that matches the identifier used by the Engage JS tag / SDK (
visitor_id).
NoteGrowthLoop does not create traits for you. Create and configure traits under Settings → User Traits in Pulse before exporting or syncing. New trait keys can be ingested, but they must be typed and displayed in Pulse before you can use them in segments.
Create the audience attribute in Recurly Engage
GrowthLoop stores audience membership in a user trait on each Engage user (default name: growthloopaudience). Configure that trait in Pulse before you connect the destination or run your first export.
- In Recurly Engage, go to Settings → User Traits.
- Create a string trait named
growthloopaudience(or your agreed name) and set display to multi-select. - When you connect Recurly Engage in GrowthLoop, enter the same trait name in the Audience Attribute field.
Set up destination
- In GrowthLoop, navigate to Destinations in the left sidebar.
- Click New Destination in the upper right corner.
- Search for Recurly Engage and click Add Recurly Engage.
- Enter the following destination details:
- Destination Name: A clear name for your team.
- Sync Frequency: Default export frequency (adjustable per export).
- Application ID: From Settings → Application in Pulse.
- API Key: From Settings → Application → API Key.
- Base URL: Leave
https://conduit.redfast.comunless Recurly provides another host. - Prefix for Personalization Fields: Optional prefix stripped before trait names are sent.
- Audience Attribute: Defaults to
growthloopaudience.
- Click Create. GrowthLoop validates the Application ID with the Engage Ping API.
Export to destination
- Open an Audience and click Export Audience.
- Select your Recurly Engage destination.
- Map User ID to the warehouse column that matches Engage
visitor_id. - Optionally map additional personalization fields to Engage trait names.
- Save and enable the export.
How membership works
GrowthLoop looks up each user via the Ping API, then upserts traits with the Ingest Property API.
- Add: Appends the GrowthLoop audience name to the audience attribute (comma-separated if the user is in multiple audiences).
- Remove: Removes that audience name from the attribute (empty string when none remain).
- Users that do not yet exist in Engage are provisioned by ingest when GrowthLoop writes traits.
Verify the export
- In Pulse, open User Lookup.
- Enter a User ID from the export.
- Confirm the audience attribute contains the exported audience name.
- Optionally create a Pulse segment that filters on that trait to drive prompts.
NoteFor warehouse attribute sync (subscription status, plan, churn signals), use Recurly Engage Syncs. Audience export manages membership; Sync overwrites mapped trait values from your dataset.
NoteIssues configuring Recurly Engage? Contact [email protected].
Updated 4 days ago