How personalized integrations work

inSided offers two possibly integrations, either using the API or using pre built components.



The community API allows for all content, personal and public, to be embedded anywhere. inSided also offers a range of pre built integration components that can be configured in the control environment and placed on the website using a piece of embed code.

Personalizing the experience

For use cases involving users’ own social content to be presented or created, the customer’s identity has to be verified. This can work in various ways.

Community content is related to user records that can be selected using an email address or, if configured, a Single Sign-On (SSO) ID that belongs to the customer. If the user’s identity has been verified by the channel that integrates to the community, a data link can be made with the API. For example, a mobile iOs or Android app which allows the customer to be logged in, could present his or her community topics created or private messages received.

Creating a new community account

For people that are new to the community, a community user account can be created on the spot, using the API. As a Single Sign-On (SSO) module often is available and the customer’s email address will probably be known, the only needed piece of information left would be the community username. If the customer is asked to provide one, its validity and availability can be checked and the user account can be automatically created within the community. The user can then proceed with any use case involving new community content, possibly without ever visiting the actual community destination. All powered by a small set of API calls.