How to set email recipient from trigger event data in scenarios

This article explains how to configure an email campaign to send to the email address provided inside a trigger event.

This is one of the most common use cases: a customer provides an email in an event, and you want the triggered campaign to send to that exact email address.

The system doesn't automatically use the email from the event. You need to explicitly store it in a customer attribute and configure the campaign accordingly.

How the system determines the email recipient

By default, Bloomreach sends email campaigns to the value stored in the email customer attribute.

Even if your triggered event contains an email property, it will not be used automatically unless you store it in a customer attribute.

To send to the event email, you must:

• Use a Set attribute node in the scenario

• Store {{ event.email }}

• Ensure the campaign uses that attribute as recipient

If this step is skipped, the campaign will send to the previously stored profile email.

Use case 1: Replace the customer’s main email with the event Email

This setup overwrites the existing profile email with the one from the triggered event.

Step 1 – Configure the event trigger

Create a scenario triggered by the event that contains the email property.

In your example:

Event name: test
Condition: email has value

This ensures the scenario runs only when the event includes an email.

Step 2 – Add a Set attribute node

Add a Set attribute node immediately after the trigger.

Configure it as:

Attribute:

email

Value:

{{ event.email }}

Important:

• email must match the exact property name stored in your event.

• Property names are case-sensitive.

This step replaces the customer's existing email with the one provided in the triggered event.

Step 3 – Add a wait node

Add a Wait node (1 minute) after the Set attribute node.

Reason:
This gives the platform time to update the customer profile before the email campaign executes.

Without this wait, edge cases may occur where the email node executes before the attribute is fully saved.

Step 4 – Add the email campaign node

Connect your Email campaign node after the Wait node.

Because Bloomreach uses the email attribute by default:

The campaign will now send to the email stored from {{ event.email }}.

Common issues in this setup

Symptom

The email is sent to the old address instead of the one from the event.

Root causes

• The Set attribute node is missing.

• The Jinja expression is incorrect.

• The event property name does not match.

• The attribute update did not complete before the email node executed.

How to check

• Open the customer profile after the event triggers.

• Verify that the email attribute was updated.

• Inspect the event payload to confirm the property name.

• Confirm Jinja syntax exactly matches the event property.

Use case 2: Send to a secondary email without replacing the main email

In some cases, you don't want to overwrite the main profile email.
Instead, you want to:

• Store the event email in a separate attribute.

• Send the campaign only to that secondary email.

Step 1 – Create a new customer attribute

Create a new attribute, for example:

second_email

Step 2 – Store event email in the new attribute

Add a Set attribute node:

Attribute:

second_email

Value:

{{ event.email }}

This stores the event email separately without modifying the main email attribute.

Step 3 – Configure manual recipient in the campaign

Open the Email campaign → Settings.

Enable:

Set recipient manually

In the recipient field, enter:

{{ customer.second_email }}

This ensures the campaign sends to the secondary email stored from the triggered event.

Common issues in this setup

Symptom

Campaign fails to send or shows missing recipient.

Root causes

• second_email attribute does not exist.

• The attribute is empty.

• Incorrect Jinja used (for example {{ event.email }} inside campaign settings instead of {{ customer.second_email }}).

How to check

• Open the customer profile after the event triggers.

• Confirm second_email is populated.

• Verify Manual recipient configuration in campaign settings.

• Run a test with known event payload.

Important notes

• Event property names are case-sensitive.

• Use event. inside scenario nodes.

• Use customer. inside campaign settings.

• Always ensure the event actually contains the email property.

• Adding a short Wait node is recommended for reliability.

Conclusion

If you want to send an email campaign to an address provided inside a triggered event, you must explicitly:

• Store the email from the event in a customer attribute.

• Configure the campaign to use that attribute as the recipient.

Depending on your business logic, you can:

• Replace the main email attribute
  or

• Store the email in a secondary attribute and use Manual recipient.

By validating attribute updates and campaign recipient configuration, you can ensure the campaign is sent to the correct email address from the triggered event.