Now that you've taken a thorough look at your email's performance, it's time to strategize next steps for re-targeting guests who have yet to take action or receive the message.

When you suspect a message has not been received:

In the previous article, we discussed keeping a watchful eye on the email domains that end up with a status of Delivered. 

Quick refresher: Let's say you sent the Save the Date to 10 people with an @hooli.com domain, and you garner 0 opens or clicks...it's likely that a corporate firewall is preventing your emails from reaching @hooli.com.

There are two best practices for getting your message into Hooli employee hands:

1. Export your email analytics and grab those Hooli emails. Follow up with note via a personal email.

2. Take it a step further! Reach out to Hooli's IT department and ask them to add all emails coming from the "@event.splashthat.com" email alias to a White List. You can even provide the IT department with the 3 IP addresses that Splash sends emails from...

• 198.37.152.18

• 167.89.13.135

• 192.254.115.244
  
  Cool note: Adding Splash's domain to a whitelist will allow event messages from future events to bypass the firewall settings.

Bounce Remediation

Emails cannot be re-sent to bounced addresses.

If you try to add addresses that have previously bounced to an event or specific email, they'll be automatically skipped, flagged as Invalid, and marked in red.

To view and correct all bounced addresses for your event refer to our Help Center article Bounced Emails: How to identify and correct for a cleaner guest list

Sometimes, the reason a perfectly valid email bounced on your first attempt was corrected. Maybe you sent to an email that didn't exist yet but now it does!

If that's the case, you can individually or mass remove invalid flags. This will allow you to re-send the email to your bounced recipients.

Click to continue to Lesson 9: Developing a post-event email strategy