What is the difference between client-side and server-side connection mode?
Last updated
Was this helpful?
Last updated
Was this helpful?
Freshpaint destinations operate in one of two connection modes. Some destinations support both while others only support one or the other.
Events will be sent directly from the user's web browser to the destination. If the destination also supports server-side connection mode, then events from other sources, including mobile and server, will be sent first to Freshpaint's servers and then on to the destination.
If you are using addEventProperties or identify calls to add data to your events, this data will be kept with the user profile which will be stored in a Freshpaint cookie in order to track the user across multiple subdomains. If you are adding a large amount of data, the cookie can grow and exceed the size that browsers can handle; bloated cookies can potentially degrade app and site performance. If you are having this issue, you can use addPageviewProperties or set up custom events to capture the data instead.
All events will be sent to the destination from Freshpaint's servers. Your website will not send data directly to the destination. Instead, your website and all other sources will send data to Freshpaint. Our servers will translate the data and send it to the destination.
HIPAA mode can only be used in server side connection mode
In general, server-side mode is preferred if it is supported by your destination. You'll see a more complete set of data since adblockers won't be able to interfere with communication to the destination. HIPAA mode can only be used in server side connection mode.
However, client-side mode may be a better choice for certain destinations as the destination's native web SDK may offer additional features. Depending on the destination this could include functionality like user surveys, live chat, notifications, or enriched event data. Refer to the destination's first-party documentation for specifics.
