This doc covers information on sending server side events into Freshpaint.
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).
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.
HTTP APIBy 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.
Not all destinations accept server-side events. Here's a list of destinations you can send server-side events to:
Active Campaign
Adobe Analytics
Amplitude
Autopilot (now Ortto)
Azure Synapse Analytics
Basis
BigQuery
Bing Ads
Braze
Crisp
Customer.io
Databricks
Facebook Conversions API
Floodlight
Freshsales
Gainsight CS
Google Ads
Google Analytics
Heap
Hubspot
Impact.com
Iterable
Klaviyo
Kustomer
LeadSquared
Mixpanel
MySQL
Panolpy
Pintrest
Postgres
Reddit Ads
Redshift
S3
Sendinblue
Snowflake
Spotify (Podsights)
StackAdapt
Tiktok Ads
Vero
Zendesk
X Ads (Twitter)
Last updated
Was this helpful?
Was this helpful?
