Events

Main concepts

Event is a kind of alert about users’ actions. Events are used to launch triggered campaigns, meaning that event acts as a trigger.

Examples of events-triggers:

  • user’s click on the link;

  • start and complete of user’s registration;

  • visit of a specific page on the website;

  • and others.

Events can be generated in eSputnik, as well as in CRM or CMS of e-store. In the second case, events are transferred to eSputnik through API.

To configure triggers or add new ones go to Automation > Event types.

In Automation > Event logs you can view the list of all events received by the system.

If events are not configured, list of event types and event history will be empty.

Configuration of events - System events

Only one event type — Click on the link is available to a user in eSputnik by default. This event occurs when a recipient clicks on a link for which this event was assigned.

If you need to assign an event, you need to pre-register this event. Go to Automation > Event types and press Add event type and in popup window select Click in the field Category. You should give a Title to your trigger. Then press button Add to save your event. The event, which has been just registered, is now seen in table Event types.

You can edit or delete Event any time. To do this press pencil or cross icon.

When the event has been registered, it becomes available in email editor. This event can be assigned to any link in an email. To do this you need to press Add event in link editor and select name of one of the registered events.

After sending emails containing a link with the assigned event, each click on such link will generate this event.

The system gets this event in real time and keeps it in log available at Automation > Event log.

Apart from event Click on link, events start и complete of registration, can be generated by the system if subscription form has been configured by our specialists. In subscription forms created in eSputnik events are generated automatically.

Configuration of events — API integration

eSputnik system has application programming interface (API), which allows integration your CRM and CMS into our trigger module.

To make such integration you have 2 options:

  1. Configure generation of required events in a specified format directly in your system.

  2. Publish our partner’s (SoftCube) script on your website, which will generate events.

With the 2nd option, it is easier to implement such popular triggers as Abandoned view and Abandoned cart. What is more, SoftCube specialists can configure Product recommendations based on user’s preferences received through this script.

You should contact our Technical Support for assistance in event-trigger configuration.

All events configured in this way are seen in eSputnik system in Automation > Event types.

In Automation > Event log you can find a log of events received by the system in a real-time mode.

Event-triggered scenario

Any scenario from Automation > Scenarios can be connected to any event from Automation > Event types. In this way, you can arrange automatic launch of campaign scenario by event-trigger.

To connect scenario with event select required event in Automation > Event types and press pencil icon (Edit mode). In popup window in field Connected Scenario select corresponding scenario and save changes pressing button Change.

The same can be done at the stage of registration of new event type, if required scenario already exists in the system.

When scenario and event are already connected, receipt of this event by the system will launch scenario for the contact whose email address was transferred with this event. Contact information is automatically transferred with event as its integral part.

In event configuration you can set scenario frequency to a specific contact specifying value in field Launch not more than once in … hours. Values of this field can be:

  • Empty field — scenario is launched only once

  • Value 0 — scenario is launched every time after receipt of event

  • Value more than 0 — the next scenario will be launched not earlier than in the time interval indicated after the last launch. For example, the specified time interval is 48 hours, the first receipt of the event will launch scenario at once, but all following events within 2 days will be ignored and only in 48 hours a new event will launch scenario.

Limits for repeated launch ensures that users don’t receive similar emails in case of several purchases on the same day. This feature is especially important when scenario presumes to send series of email during several days. In other words, if limits equal to series duration are set, we guarantee that users won’t get several identical series at no point.