Once you have decided whether your integration will be done Server side or Client side, the next decision to be made will be which method of implementation you will use. Client Side sites can choose between JSON or API. Meanwhile, Server side sites are limited to using APIs.
This topic is intended to help Retailers who are implementing RichRelevence products on their websites understand the two implementation options, Server Side or Client Side.
What are the benefits of this feature?
Understanding the way each of the two implementation methods works is important, no matter which product or products from the RichRelevance lineup you are implementing.
What are the drawbacks of this feature?
Retailers will want to work closely with their Rich Relevance team to get the most out of their implementation. While many features are self-service, taking advantage of the RR team and the training provided will help avoid hiccups in implementation.
How It Works
When a shopper visits a site that uses a RichRelevance product, the site sends information about the shopper and the site to the Relevance Cloud and receives personalized content in return. This call to the Relevance Cloud and the response can be made from the shopper’s browser (which we call a client-side request) or from the merchant’s server (a server-side request).
- Access to additional debugging and testing tools
Both client-side and server-side sites can use API calls to communicate with the RichRichRelevance server.
The API calls are documented in detail in both this core integration category as well as in product specific locations for product specific features.