Default Send Relationship
This feature is available in Unaric Segment Enable, Plus, and Advanced.
Define a default configuration for newly created sendable Target Data Extension.
How it works
You can define a default setting for the name of the field that you always configure in the Send Relationship (normally, the name of the Contact Id/Email that you use in Data Extensions as the starting point of your Selections).
Enabling this setting will not affect any sendable Target Data Extensions previously created, but will ensure every new sendable Data Extension has the right field configured in the Send Relationship. This can be very helpful to avoid setting the wrong Send Relationship, with the consequences it can have in your All Subscribers billing with Salesforce.
After setting up, a default send relationship, when a user creates a Sendable Data Extension:
- If present, the field with that name will be automatically selected as part of the Send Relationship.
- If not present, the Send Relationship will be left empty forcing the user to define it before they can save it.
Still, users can edit this mapping before saving the new Target Data Extension by clicking the expand arrows in the Send Relationship field and selecting a different field.
In case the Send Relationship setting is blank, the below error message will appear upon trying to save the Data Extension.
Besides, if the user tries to create the Selection with a field named different from what you defined in the Default Send Relationship, they will receive a warning message.
Setup
- Navigate to Admin Panel > Settings.
- Click on Show Relationship in the Send Relationship Settings section.
- Enable this feature by sliding the Default Setting toggle to the right. It turns blue and has a checkmark when this feature has been enabled properly.
- In the Send Relationship field, enter the name of a specific field that will be used as the default Send Relationship setting and choose whether to create this relationship with either the Subscriber Key or Subscriber Id.
The name field is case-sensitive.