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):

• EMAIL SENT
• OPENS
• URL CLICKS (interior content)
• UNSUBSCRIBES
• BOUNCES
• 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!

New Feature: Transactional Email Event API

We're pleased to launch the Event API for JangoSMTP, a system that can call any web service or web page on your server upon a specified event. The following events can trigger a call to your web service:

1. A sent email
2. An open of an email
3. A click of a URL in an email
4. An unsubscribe
5. A bounce
6. A complaint, via Feedback Loop

Why is this important?

Using the event-triggered API, you can now easily sync transactional email data with your own database or CRM system. You only need one script on your web server to handle the calls from JangoSMTP. The calls from JangoSMTP are made in real-time of an event happening.

How do I set this up?

To set up event-based web service calls, go to Settings --> Advanced and click on the Edit Button to the right of Transactional Event API.

Check the boxes next to the events to which you would like calls made and specify what URL should be called, with what parameters, and with what action type, POST or GET.

How is the Event API different from the Standard API?

The standard API, available at http://api.jangomail.com, allows a programmer to interact with JangoSMTP much like a user would interact with JangoSMTP through the web-based interface. You can pull reporting data, and send transactional email through the standard API. The event API pushes data to your system when an event like a click or an open happens. The standard API needs to be polled by your system to retrieve open or click data.

Other useful notes:

1. If there are 1,000 consecutive failures when calling a specific web service for a specific event, then calls to the web service will cease until the URL or one of the parameters is modified. A failure is any HTTP response that is not status 200.
2. When you first designate a web service and its attributes, JangoSMTP will call the web service for the last seven days worth of data. So if you specify a web service for the "open" event today, open data from the last seven days will immediately be posted to the web service.
3. The parameter values will be URL-encoded before they are passed to your web service via HTTP POST or GET.
4. You need not specify all parameters for a particular event. You only need to specify those parameters whose values you'd like your web service to receive.
5. Every time JangoSMTP makes a call to your web service, it is recorded in the Event API Log, which can be viewed under Reports --> Logs --> Transactional Event API. From here you can see a list of all successful and failed calls to your web service.