For transactional emails, reporting is usually calculated per day, since there is no such thing as a campaign. Transactional emails are usually one to one. We have come up with Tag concept for emails in order to group some emails (by tags). By using the email tags, it’s now easy to check reports for a specific group of emails. For example: order_confirmation or signup.
NewsmanSMTP supports multiple tags per email.
Adding the tags is straight forward: Use X-NZ-Tags email header. Tags are separated by comma.
Ex:
X-NZ-Tags: order_confirmation,customer_101
The email tagging feature is also supported in the REST API.
Tags can pe added in the message.send method.
Some of our users requested more flexibility when choosing how they want their emails to be tracked.
We have implemented the mail header X-NZ-Track which can take any of the following options separated by comma:
- open – enable email open tracking by adding the pixel image
- click – enable tracking of links in both html and plain text version
- txt_click – enable tracking of links just in the plain text version
- html_click – enable tracking of links just in the html version
If the header is used it overrides acount settings.
Examples:
X-NZ-Track: open,click
// tracks both open and click in html and plain text version
X-NZ-Track: txt_click
// tracks just click in plain text version
We’ve released a quick update today which allows you to “identify” easily every email sent.
For this we have a new email header: X-NZ-Metadata
.
All data sent in this email header will be saved to the database and later on can be retrieved by API call: send.info
.
Also the value of the X-NZ-Metadata
header will be sent with all webhook calls in the meta array.
Here is a quick example of adding custom email header X-NZ-Metadata
with Swift mailer:
$message->getHeaders()
->addTextHeader("X-NZ-Metadata", "My custom string: ID or JSON, etc.");