Personalization
Activate personalization
note
If you are using Uniform Canvas to manage layout in your application this section doesn't apply. If you are using Canvas, no additional configuration is required in your front-end application. You should skip this section.
Activating personalization in your application involves adding components that can execute personalization instructions. By default, Uniform executes personalization on the client. However, Uniform also supports edge-side personalization.
Personalization modes#
Uniform supports a variety of personalization modes. Each has its own advantages and disadvantages. The available modes depend on the rendering mode you use.
| Server side (SSR) | Static site (SSG) | |
|---|---|---|
| Description | The application renders on a server in its entirety before it reaches the client. | The application is rendered at build-time. |
| Time to first byte (TTFB) | Affected by time needed to load content. | Optimized by content being fetched at build-time. |
| Scalability | Increased server load requires increased server costs. | Instant and global. |
| Application size | Application size is irrelevant because the application renders on demand. | Very large sites may take a long time to render. |
| Personalization modes |
|
|
Client-side#
warning
Classification must be enabled before you can add personalization to your app. For more information, see the guide on classification activation.
Edge-side#
If you are using a CDN that supports running custom logic, you can move the execution of personalization from the client to the edge.
tip
Instructions on configuration for specific CDNs is available in the CDN integrations section:
The configuration for edge-side personalization is basically the same as client-side personalization. The difference is that the output mode for the Uniform context is changed to edge mode.
tip
Next steps: If you haven't already done so, you must configure the component responsible for executing personalization. The steps needed depend on the CDN you deploy your app to.
Server-side#
This is a traditional server-side rendering mode (SSR), where the application renders on the server with all the data and state it has access to at the request time.
tip
Before you start, classification must be enabled before you can add personalization to your app. For more information, see the guide on classification activation.