Dynamic email sender

The dynamic email sender feature lets you send one campaign from different email accounts, depending on who the recipient is. Instead of using one sender for everyone, the system checks a specific attribute assigned to each recipient and automatically chooses the right sender account based on that. The selection is based on a Brickworks schema, where the mapping between attribute values and sender accounts is defined.

This is designed for multibrand or multilingual operations where each market or brand requires a dedicated sender account. For example, a company that operates in multiple regions can ensure that recipients in each region receive the email from the correct regional sender account, with the appropriate IP pool and sender identity.

Requirements

• At least two email sender accounts must be configured in the workspace.
• You must have the following user permissions:
  • create and edit schemas
  • create and edit records
  • if you plan to create versioned schemas, then you need permissions to publish records.
• The recipients of the email must have a profile attribute whose values correspond to the mappings defined in the Brickworks schema. You choose which attribute to use - any profile attribute can serve as the basis for sender account assignment.

Creating a Brickworks schema with mapping

Before you can use the dynamic sender in a campaign, you must create a Brickworks schema that maps profile attribute values to sender accounts.

Getting the sender account ID

In further steps, you will need the IDs of the sender accounts. To find the ID of a sender account:

1. Go to Settings > Email accounts.
2. Click the sender account you want to use.
3. Copy the ID from the URL of the page.

   

Creating the schema

In this part of the process, you will create a schema with the following fields:

1. Go to Data Modeling Hub > Brickworks.
2. Create a new schema. For more information on creating schemas, see:
   • Creating a schema
   • Field types
3. In the Fields tab, add the following fields:
   1. Add a String field:
      • In API name, enter profile_attribute_name
      • Select the following options for this field:
        • Required field
        • Block record-level overwriting - This setting requires you to provide a default value for this field in each record — enter the name of the profile attribute used for matching.
   2. Add a String field:
   • In API name, enter attribute_value
   • Select the following options for this field: Required field and Unique values only.
   3. Add a Number field:
   • Set the type to Integer.
   • In API name, enter sending_account
   • Select the Required field checkbox.
4. Save the schema.

Adding records

After creating the schema, add a record for each sender account you want to map:

1. Open the schema and go to the Records tab.
2. For each mapping, add a record with the following values:
   • In profile_attribute_name, the value is already provided due to the Block record-level overwriting option in the field setting.
   • In attribute_value, enter the attribute value that identifies this group of recipients (for example, PL).
   • In sending_account, enter the ID of the sender account assigned to this group.

   

3. Repeat for each sender account you want to map.

To learn about limits on schemas and records, see Limits and constraints.

Example

In this example, three records are added to the schema:

In this example, recipients with region = PL will receive the email from account 6235, recipients with region = DE from account 6236, and so on.

Selecting the schema in a campaign

Once the schema is ready, select it when creating an email campaign:

1. In the Content section of the campaign, select Dynamic sender.
2. In the Email account allocation schema field, select the schema you created.

For the full email setup, see Creating emails.