Monday, May 20, 2013

For Maximum Visibility, Push Events To Your Own Server

If you haven't made use of this cool JangoSMTP feature, you should give it a long, hard think.

Our transactional email event API is a system that can call a web service or web page on your server when triggered by any of these transactions within and around your emails. (And we're sure you're watching these pretty closely):
  • URL CLICKS (interior content)
  • COMPLAINTS (via Feedback Loop)
This key event data in the life cycle of your email is pushed - in real time - directly to your server. So, you're always in the know about the overall success of your transactional email. Plus, you can make adjustments and improvements on the fly to strengthen ROI.

How to set up your event-based push
  1. Go to Settings > Advanced > Transactional Event API
  2. Click on the tab for every event you want a call to your web service or page
  3. Enter the details for your web service or page

Try this while you're there
Custom coding can be used to create unique notifications, logging or custom integration into your own back end. We're always up for developing new ways to help you make JangoSMTP your own - so ask us to jump in and help any time.

For the record
Transactional email event API is a relatively new feature for JangoSMTP. We've had a Standard email API, which you can learn more about in this PDF tutorial.

Here's the key difference between the two: The Event API pushes event data (opens, clicks, etc.) to your system as the event occurs. The Standard API needs to be pulled by your system to retrieve open or click data. Before you consider the new API a "lazy man's lobster" version of the old, remember that technology evolves. And as it does, we're on the lookout to bring it to you fast. But everyone has a preference, so it's up to you to choose what works best for your company.

If you have any questions about Event API or any other JangoSMTP features, hit us up. We'd love to hear from you.

Until then, have a great rest of the week!