Custom Events feature inside Aritic PinPoint allows you to track advance behavior and activity of the visitors and contacts. Once you define the custom events, then you can trigger the tracking through Javascript Event API added along with the Aritic PinPoint tracking code and Events HTTP API.

Data from Custom events for each contacts can be used inside defining dynamic email templates that can be used to highly personalize the email content sent to each contact through automation workflow.

Define a Custom Event

1. From Aritic PinPoint Dashboard, navigate to the Settings from top right menu and then go to “Custom Events” under “Marketing Setup.

2. From this Custom Events Dashboard, click on New button to add and define a new custom event.

3. From the new pop-up, add Name of the Custom Event, Alias of the event.

Note: Alias should not contain any number or symbols, it should be only alphabates. Alias are used to identify and trigger the custom events. Each alias should be unique among all the used custom event alias.

Add Payloads value inside each of the Payloads. You can leave right side not blank. These Payloads are going to receive the event values through Javascript Event API or Events HTTP API.

Note: Payload values should not contain any number or symbols, it should be only alphabates. Each value should be unique among a defined custom event.

4. Once add all the fields, click on “Save & Close” button. This defines a custom event inside Aritic PinPoint.

Track Contact and Trigger Custom Event

Inside Aritic PinPoint, Custom Events can be triggered through following 2 methods-

  1. Javascript Event API
  2. Events HTTP API

Javascript Event API

Aritic PinPoint supports two callbacks, onload and onerror accepted as the fourth argument. The onload method is executed once the Aritic PinPoint tracking pixel has been loaded on the page. If the tracking pixel fails for whatever reason, onerror will be executed.

at('send', 'pageview', {}, {
onload: function() {
redirect();
},
onerror: function() {
redirect();
}
});

You can attach custom parameters or overwrite the automatically generated parameters to the above created Custom Event Alias action as you could to the tracking pixel query. To do that, update the last row of the JS code above like this:

at('send', 'testname', {email: 'my@email.com', firstname: 'Kim', productname: 'Bag'});

Note: Above used “testname” is the Alias, as defined in above Custom Event creation field.

Above code will send all the event data automatic to Aritic PinPoint and also add email, firstname and productname event.

Aritic PinPoint event tracking code also supports company fields. This script code can assign a company to your tracked contact based on company name. Then you have to add company or companyname parameter to tracking code along with other companies fields ( companyemail, companyaddress1, companyaddress2, companyphone, companycity, companystate, companyzipcode, companycountry, companywebsite, companynumber_of_employees, companyfax, companyannual_revenue, companyindustry, companyindustry, companydescription…):

at('send', 'testname', {email: 'my@email.com', firstname: 'Kim', company: 'Aritic', companyemail: 'aritic@aritic.com', companydescription: 'description of company', companywebsite: 'https://aritic.com'});

To load the event: The JS tracking request is loaded asynchronously, you can ask JS to call a function when a request is loaded. To do that, define a onload function in options like this:

at('send', 'testname', {email: 'my@email.com', firstname: 'Kim'}, {onload: function() { alert("Tracking request is loaded"); }});

Events HTTP API

You can use Custom Event API to track contact and trigger custom events. Detail about the custom event API is available here.

Personalize Email Template with Data from Custom Event

Using Custom Events data you can personalize your email templates inside Aritic PinPoint. You can use following tag tokens to personalize your email templates inside text field:

{customevent=productname}

In above tag token, “productname” is the payload of the custom event.

Trigger Personalized Emails through Automation Workflow using Custom Events Data

Once you have created email templates using above Custom Event tag tokens; you can trigger these personalized emails for each contact through automation workflow.

To trigger the email from automation workflow; the contact has to be in a segment and the “Custom Event” trigger can be found inside Decision of the workflow.

Note: This trigger from Automation Workflow works only when the custom event get data from Custom Event API.

In above workflow, after adding “Custom Event” decision, you can add “Send Email” action.

Uses of Custom Events

Browser and Mobile Visits:

You can use custom events to track the browsers your visitors use frequently and also determine how often they visit from a mobile device.

Tracking Logins to External Site:

You can use custom events to send to Aritic PinPoint information about users who are actively logging in to your external website where you have a login-only section. The custom event is triggered upon login. Once the information is saved to contact records, you can segment and create lists based on the recent logins. You can opt for some useful filters like specific time frames and total number of times the event was completed.

Shopping Cart Abandonment:

Often on a B2C company website, visitors do not complete the entire purchase process even after adding items to their carts. Create custom event to trigger when a visitor has calculated shipping, and add these contacts to a separate segment. Use this list to send a reminder to complete the purchase.

Limitations of Custom Events

You can create up to 200 custom events in Aritic PinPoint Enterprise account. You will be notified as you approach your limit. You can delete some of your unused events to continue creating new ones without exhausting your limit.

Once you reach the limit, new events will be added under Unexpected events in your events manager.