This doc covers information on sending server side events into Freshpaint.
When to track events server-side vs. client-side
The Javascript source is the easiest way to collect data with Freshpaint. The Javascript source automatically collects data from your site and lets you retroactively create events from the collected data.
We recommend that you track events server-side in the following scenarios:
Offsite events: when a user interaction is not on a website or app (for example, using your API)
Revenue events: the event for completing a purchase (for example, a user may click the 'Purchase' button, but that purchase may time out)
Sometimes you can make an argument for tracking an event either client-side or server-side. We recommend that you should only consider tracking events server-side in the following scenario:
Essential events to operations: For example, events that you trigger a critical email drip from (so that users don't get left out or sent the wrong emails).
Sending Server-side events to Freshpaint
To send server-side events to Freshpaint, you should use the Freshpaint HTTP API. Take a look at HTTP API reference for how to go about sending events to Freshpaint.
By default, server-side events will be sent to all active destinations. Active destinations are destinations you have configured and enabled in Freshpaint.
If you don't want server-side events to be sent to all active destinations, you can have more granular control by following the options listed here.
Supported Server Side Destinations
Not all destinations accept server-side events. Here's a list of destinations you can send server-side events to:
