With zenloop's native Emarsys integration, new zenSurvey responses can be sent to Emarsys automatically through Workflows. zenloop creates or updates Emarsys contacts and writes mapped survey response data to contact fields.

Survey answers are mapped to Emarsys contact fields so feedback data can be used in Emarsys campaigns, segmentation, and follow-up automation.

Why Connect zenloop and Emarsys?

• Act on feedback where you run your campaigns. NPS, CSAT, and individual survey answers can become part of the Emarsys contact profile.
• Segment by feedback. Build audiences based on survey answers, response IDs, or other mapped fields.
• Trigger follow-up journeys from Emarsys segments or automations based on the updated contact fields.
• Keep setup inside zenloop Workflows. The workflow stores the Emarsys credentials and sends new matching responses automatically.

How It Works

The integration is part of Workflows and is configured per survey. When a response matches the workflow conditions, zenloop sends the selected response data to Emarsys through the Emarsys API.
When you create an Emarsys workflow, zenloop creates or finds dynamic fields in Emarsys for the survey questions. The workflow then stores the field mapping and uses it when responses are sent.

What You Need

You need Emarsys API credentials with access to the Emarsys account you want to update. In the zenloop workflow setup, these are entered as:

• API Key
• Secret Key

If the organization already has an Emarsys workflow configuration, zenloop can reuse the existing configuration instead of entering new credentials again.

Set Up the Integration

1. In zenloop, open Workflows and create a new workflow.
2. Select the survey the workflow should run for.
3. Choose Emarsys Integration as the workflow action.
4. Use an existing Emarsys configuration, or enter a new API key and secret key.
5. Configure the workflow conditions, such as completed response status, answer filters, property filters, or topic filters.
6. Save and activate the workflow.

When the workflow is created, zenloop creates or finds the Emarsys fields needed for the selected survey and stores the mapping on the workflow.

Mapping

zenloop maps survey response fields to Emarsys fields. For new Emarsys workflows, zenloop creates dynamic Emarsys fields for the survey questions and a response ID field, then saves the mapping on the workflow.
The response ID is used as the default identifier for dynamic field mapping. The mapped survey values are then written to the matching Emarsys contact fields when a response is processed.

Using Email Embeds with Emarsys

If the survey is distributed through an Emarsys email, add respondent and metadata values to the survey link before sending. Use the current zenSurveys URL parameter format:

identity[value]=<emarsys-contact-placeholder>&identity[type]=email&properties[order_id]=<order-id-placeholder>

identity[...] stores the respondent identity. properties[...] stores response properties that can be used in zenloop filters, exports, and supported workflow paths. Response properties are useful for deciding when a workflow should fire, but they are not the same as mapped survey answers.
Always test from Emarsys, because Emarsys resolves its own placeholders before the respondent opens the survey link.

Check the Data in Emarsys

After a test response, open the contact in Emarsys and check that the mapped fields contain the expected values. If a field is missing, check that the workflow is active, the response matched the workflow filters, and the mapped value was present on the response.

Good to Know

• The sync is one-way: zenloop sends response data to Emarsys.
• Syncing starts after the workflow is saved and activated. Past responses are not backfilled by the workflow.
• Empty or missing response values cannot be written to Emarsys.
• Dynamic field creation happens when a new Emarsys workflow is created.
• If dynamic field creation fails, check the Emarsys API key, secret key, and account permissions.
• Emarsys email placeholders and native Emarsys workflow sync are separate pieces: placeholders identify or enrich the response link, while the workflow sends response data to Emarsys after submission.
• The current workflow setup is focused on creating or updating Emarsys contacts. If you need event or segment behavior, confirm the workflow setup with your zenloop contact first.
  
  

Example Use Cases

Win Back Unhappy Customers

Send low NPS or CSAT responses to Emarsys and use the updated contact fields in a recovery journey. For example, detractors can enter a flow with an apology, voucher, callback offer, or support follow-up.

Activate Promoters

Send high NPS responses to Emarsys and use promoter fields for a review or referral audience. This lets marketing follow up while the positive experience is still fresh.

Filter by Survey Context

Pass response properties such as order ID, country, store, or customer segment with the survey link. Use those properties in zenloop workflow filters so only the right responses are sent to Emarsys.