Mapp Engage

Mapp Engage carries your email through your own Engage system, so the integration is made with a system user from your Engage account rather than with an API key. To set up Mapp Engage for integration with EmailElement, you'll need:

• An API user in Mapp Engage
• The Response Queue switched on for your account, carrying bounces and unsubscribes
• The base API URL of your Engage system
• One sender domain, on a domain your Engage system hosts

Create an API User

Every call is authenticated with the email address and password of a system user, and only a user whose type is API or Hybrid can be used. Make an API user rather than reusing a person's login: keeping the two apart shows who made which change.

1. In Mapp Engage, go to User Management > System Users > System Users.
2. Click New.

3. Under Type, select API User.

4. Enter the email address, first name and last name, and set Role (Messaging) to Client Administrator.
5. Leave Send password notification email ticked so the password is sent to that address, and click Save.

Switch On the Response Queue

EmailElement reads what happened to each email from the Response Queue on your Engage account. Mapp switch that on for you, and they decide which types of response it carries. Ask them for mtaResponse, which is bounces, and unsubscribe. Without those two we never learn that an address bounced or that somebody unsubscribed inside Mapp, and neither reaches us any other way.

Ask them to include the external transaction id on both. That is the value EmailElement sends with every email, and it is what ties a bounce back to the send it came from.

Find Your Base API URL

Take the address you sign in to Engage with and drop the page path. Signing in at https://email.yourdomain.com/home/login.jsp makes the base API URL https://email.yourdomain.com. EmailElement adds the rest of the address itself.

Set Up Mapp Engage in EmailElement

1. Go to Send Integrations and click Create Send Integration.
2. Choose the integration type, pick Mapp Engage from the list, and click Next.
3. Enter a name for the integration.
4. Select the sender domain. Mapp Engage takes one domain per integration, so a second domain is a second integration.
5. Enter the Base API URL, then the Username and Password of the API user. The username is that user's email address.
6. Click Create.

Saving the integration creates a group and a message in your Engage system, both named after the sender domain it sends from, and every email the integration sends goes out through them. Leave both in place. Changing the sender domain on the integration makes a new group and a new message, and later sends go out under the new From details.

Switch On Transactional Sending

Saving the integration creates the group, and Mapp Engage will not report what happened to an email until that group has transactional sending switched on. That setting can only be changed in Mapp Engage.

1. Sign in to Mapp Engage and go to Audience > Group Management > Groups.

2. Find the group named after your sender domain and click the pencil to open it. EmailElement shows the group number on the send integration.

3. Open the Sendout Options tab.

4. Expand Transactional Messages, set Transactional Message Mode to On, and enter u=<%{user['PK']}%>m=<%${message['PK']}%> as the pattern for the TMID.

5. Click Save. Saving with the pattern empty leaves the mode off without saying so.

Add the Reply-To Header

Mapp Engage does not pass on the reply-to address EmailElement sends with the email, so a reply goes back to the group's own address instead of yours. One custom header on the group fixes that for every send.

1. On the same group, open Sendout Options and expand Customized Email Headers, then click the + beside Email Headers.

2. Enter Reply-To as the header name and <%parameter.ReplyToName%> <<%parameter.ReplyToAddress%>> as its value.

3. Click Save.

Switch Off Mapp Engage Tracking

EmailElement puts its own tracking pixel in the message and rewrites the links before the email is handed over, so opens and clicks are already counted. Leaving Mapp Engage to do it as well counts every open and click twice and replaces our links with Mapp's, which breaks the reports.

1. On the same group, open the Tracking & Links tab.

2. Under Message Tracking, clear every box: Track HTML Opens with Invisible Tracking Pixel, Track Text Message Links, Track HTML Message Links, Track Personalized Links and Track System Links.

3. Click Save.

Test the Integration

1. Click Run Test on the integration.
2. The result is reported for each sender domain on it.
3. One domain succeeding is enough for the integration to go active.

Troubleshooting