THRON integration with your CMS or using THRON as the source of your digital assets to develop your website, will bring you the following benefits:
- Centralized content management, removing duplication and gaining full control on operational efficiency.
- Collection of relevant data on end-users and their interests, according to the content they view.
- Relevant and personalized communication with your end-users thanks to THRON Customer Experience and the recommendation mechanism built in THRON platform.
[dropdown:Content Management]When planning to integrate with THRON on any aspect, and especially to build a website, the most important thing to do is to centralize content management within THRON, making it the main source of your digital assets. This will help you to have a unique centralized content archive, removing any duplication and increasing your efficiency.
First thing to do is to upload your assets to THRON, you should publish them into a folder where you previously installed a THRON Custom Application Manager which will be used to retrieve content and display them in your website.
Applications are special THRON users which are not identified by a couple username/password, but by an appId and an appkey (optional). They can only have read access right on content and users; if needed they can impersonate a business user to perform different actions. Further information can be found in this article. Moreover, applications can only operate on a limited context which is represented by the folder tree in which they have been installed. The steps you have to follow in order to complete such integration are:
If you are using a CMS it is important to build a synchronization mechanism so that any action performed on content triggers an update to your CMS. To do so, use JSync service to monitor THRON content updates in a batch process, or subscribe to notification system in order to build a real-time synchronization.
The text of your web pages can be included in a Page content type within THRON; along with all the advantages provided by the platform such as centralized control and tracking of statistics, it will also allow you to handle multilanguage pages. Further information on how to extract the body of a page content type can be found in this article.
Make sure you classify all your content by setting up a proper classification in your TOPIC class. This will enable you to track users interests according to the content they view, and thanks to the behavior engine it will allow you to build a personalized communication with your end-users. Further information on how to create an effective tag tree can be found in this article.[/dropdown]
[dropdown:Content distribution]Leveraging THRON platform you will be able to collect relevant data on how your digital assets are used within your website. The behavior engine will constantly update content information according to the interests of the users accessing them, and will update users interests according to the content they view; this will help you build a powerful recommendation system, to provide your end users with the content they are looking for. To deliver your content we recommend you to use THRON player, since it offers all the features requested by the content intelligence to work properly. Once you have retrieved the content you want to display by using a findbyProperties request you just have to embed THRON player in order to playback such content. These are some interesting articles which illustrate how to perform optimized content searches using folders, tags or metadata. Since you are delivering your content in a specific context such as a website, we recommend you to set a new contextId and include it in your embed codes, this will help a quicker retrieval of all the statistics related to the website. Further information on Contexts can be found in this article.
For image content type you can even plan to use the getThumbnail web service, which will provide you with the thumbnail of the proper resolution to fit your div (further information can be found in this article); if you do so, or if you do not plan to use THRON player to deliver content, make sure to integrate THRON tracking library in order to collect data. [/dropdown]
[dropdown:User profiling]If you wish to deliver a relevant and contextual content message to your end users according to their interests you have to collect relevant data on the content they view the most. Content Intelligence has been specifically built to collect such data and provide you with all the information con content access performed by your end-users. If you are integrating THRON with a CMS you might want to import your already existing contacts. This can be done by using the webservices of xcontact. Once content have been created it is important that you start enriching their profiles by linking tags related to TARGET and TOPIC classes; this can be done using the webservices of itag; further information can be found in this article.
From the moment you start using THRON to deliver content through your website, new contacts will be automatically created thanks to THRON player and its integrated tracking system, or thanks to the tracking library (assuming you are not using THRON player to deliver your content).
If your website has a restricted area or any kind of contact form, allowing you to collect identities you might want to pass such information to THRON in order to improve their profilation, as long as their connected/disconnected status. Please refer to tracking library’s documentation for a deeper understanding of such feature.[/dropdown]
For a deeper understanding of the topics covered in this recipe, you might want to have a look at: [dropdown:Relevant THRON Concepts]
For a better understanding of this recipe, you might want to deepen your understanding of basic THRON concepts.
These are all the articles presenting you the definition of the basic THRON concepts:
- Access Rights
- Profiles and Channels
- Tracking Library
- Target and Topic classifications
For a quick overview of all THRON's features, have a look at this article.