mParticle

Integration guide for capturing Recurly Engage prompt interactions as custom events in mParticle via Custom Feed.

Overview

The mParticle connector lets you export prompt events and attributes from Recurly Engage to your mParticle workspace, enabling unified user activity tracking across platforms.

Required plan

This feature or setting is available to all customers on any Recurly Engage subscription plan.

Prerequisites & limitations

  • Company or App Administrator permissions in Recurly Engage.
  • An mParticle account with permissions to create Custom Feeds.
  • Access to your mParticle workspace’s Server Key and Secret.

Definition

Using mParticle’s Custom Feed integration, Recurly Engage will send prompt interaction events and related attributes to mParticle for real-time analytics and segmentation.

Key benefits

  • Streamlined event export: Automatically push Recurly Engage events into mParticle without custom coding.
  • Unified user data: Leverage mParticle’s identity resolution and data pipeline for prompt events.
  • Real-time insights: View prompt impressions, clicks, and custom goals alongside all other mParticle-tracked events.

Key details

Activation

  1. In mParticle, navigate to Setup → Inputs.
  1. Click on the Feeds tab and add a Custom Feed by clicking the + icon.
  1. Provide a Configuration Name, then share the Server Key, Server Secret, and API Endpoint with your Recurly Engage Customer Success Manager.

Required settings

Under Settings → Integrations → External → mParticle in Recurly Engage, configure:

  • Base API Endpoint (including mParticle Pod)
  • Server Key
  • Server Secret
  • Mode: Production or Development

Supported actions

ActionDescription
Export EventsReports custom events with user-specific prompt interactions and attributes

Custom events and attributes

After activation, mParticle will receive the following custom events tagged to the user’s identity, visible in the User Activity screen:


Custom EventDescription
Recurly Engage Prompt ImpressionA user has seen the prompt
Recurly Engage Prompt DismissA user has dismissed the prompt by clicking close or outside (if enabled)
Recurly Engage Prompt TimeoutThe prompt closed automatically due to a timer
Recurly Engage Prompt DeclineA user declined the prompt by clicking the decline button
Recurly Engage Prompt ClickA user accepted the prompt via the primary CTA
Recurly Engage Prompt Custom GoalA user completed the custom goal action defined for the prompt

Attributes sent with each event (when available):

Custom AttributeDescription
app_nameThe name of your Recurly Engage instance in Pulse
prompt_idUnique prompt identifier (from Details)
prompt_nameThe name of the prompt
experiment_idUnique experiment identifier (if the prompt is part of an A/B test)
experiment_nameName of the running experiment
variation_idIdentifier for the specific prompt variation
variation_nameName of that prompt variation
survey_valueValue of selected survey option (if survey is enabled on the prompt)

Additional resources