Organize different types of transactional emails using the Transactional Groups feature. To set up the Reporting interface to show reporting data organized by Transactional Group, you will need to assign a particular Transactional Group to each email you send.
Creating Transactional Email Groups
Create and manage Transactional Email Groups in your account under Settings → Authoring → Transactional Groups. Click the Edit Icon. In this account, three Transactional Groups have been created. All accounts come with a "Default Transactional Group" that cannot be modified or deleted. Any email that is not assigned a Transactional Group will automatically be grouped into the Default Transactional Group.
Transactional Email Groups can be created and managed in your account under Settings → Transactional Settings → Transactional Groups.
Assigning Transactional Groups via API
In Settings, next to each Transactional Group is its unique numeric identifier. This numeric identifier can be specified when calling the SendTransactionalEmail method to assign that particular email message to the TransactionalGroup. Specifically, within the Options input parameter, specify the parameter “TransactionalGroupID”. For example, the Options input parameter may be: “OpenTrack=True, ClickTrack=True, TransactionalGroupID=333128” for a transactional email message that is an order confirmation for the sending organization.
If a TransactionalGroupID is not specified in the Options input parameter, the email message is grouped into the Default Transactional Group.
Assigning Transactional Groups via SMTP Relay
Include the Group's name in the subject line in curly brackets. For example, if your group name is "Spring" and your subject line is "Test" then your subject would say: Test {Spring}.
As noted above for the API method, if a Transactional Group Name is not specified in the Subject, the email message is grouped into the Default Transactional Group.
Combine broadcast messages and transactional messages for effective communication. |
|
Comments
0 comments
Article is closed for comments.