Principles

As with the JS Tracker, the RESTful Tracker allows you to identify your users and track all your events, but unlike with the JS Tracker:

  • You'll have to fire all the events yourself (the JS Tracker does the page views tracking for you) ;
  • The identification of the users rely on email address only, so you'll have to pass it in each and every call to the tracker ;
  • We'll not be able to automatically identify the users who have clicked in your emails.

Therefore the RESTful Tracker is mostly useful if you want to track events on the server-side or on a client that is not a browser (e.g.: a Mobile App).

If you don't know which tracker to use or if you can do a browser side implementation, we recommend you to go for the Javascript Tracker which will do most of the work for you.

Combine the JS and the RESTful Tracker

The RESTful Tracker can be used in combination together with the Javascript Tracker. You just have to keep the email address of the user consistent across the trackers.
For example you can use the JS Tracker to identify and track users behaviour on your website and the RESTful Tracker to track the orders on server side.

Principles


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.