Server or Client Side?

Last Updated 2021-04-02

Implementation Options

You can setup Cloudmattr to track Users and Events in 2 ways, Client side and Server side, or both. For the most part, both options support the same things, but we'll outline what each one supports and doesn't so you can decide your best route moving forward.

Client Side Support

When setting up Cloudmattr with the Client Side Library, you'll be able to set it up directly on your website by your developer, or using a tag manager, such as Google Tag Manager very easily. This is help if you're looking to leverage the Campaigns functionality.

What you can do:

  • Create and Update Users
  • Create Events for Users

When should you setup with the Client side library?

You should use this option if you only want to leverage the Campaigns functionality, but don't need SSO (single sign on) from your website to Cloudmattr, or if you want to set it up client side on your website without working in your backend to implement.

Server Side Support

Setting up Cloudmattr provides a more seamless experience for users, where you can leverage the platform to automatically sign in your users from your website to Cloudmattr. This will automatically sign them in, and be able to interact with your Knowledge Base, Boards, Roadmaps, etc.

What you can do:

  • Create and Update Users
  • Authenticate Users (SSO)
  • Create Events for Users

When should you setup with the Server Side API?

If you're looking for a fully integrated implementation that creates a fully automated experience for your users and taking advantage of all the features available in Cloudmattr, we highly recommend using this option.

Using Both Options (Hybrid)

Use both? Sure! There's no issue with using both, as long as you keep your User ID's consistent AND you don't track the same events both Server and Client Side.

For example, you might want to track your Users via the Users API, but prefer to track your Events via Google Tag Manager. Or track some Events server-side, and others in GTM (we do this).

Tracking Plan

Before getting started, you should start with creating a tracking plan where you outline what user properties and events you'll be tracking.

See our Tracking Plan template here, which can get you started and start building out your own custom plan.

Was this article helpful?