CMS Publications is Required
Below guide applies for Sitecor and Optimizely (former Episerver). Head over here for Drupal specifications.
In this Article
Access Model for Privacy
In order to respect the privacy of our customers, we have given APSIS One a sophisticated access model for use when determining who can read or update a Profile. For more information about this see the Allowed Operations section in the article on attributes in the data model.
Generally this model does not allow for reading a profile utilising only a cookie id since that is openly available in the browser of your web visitors. This means that CMS integrations must be given special permissions to read any data since they utilise the visitors cookie ID when evaluating a segment.
Does CMS Publication expose my data to anyone who has access to a persons cookie ID?
No, absolutely not! The CMS publications enables reading data with a cookie id for authenticated systems only. This means that even after publication is done, only systems that you have connected to your account with API Credentials are allowed to read it.
How Change Publication Status
After installing a CMS integration on your account, CMS publication is done directly from the Segment Builder.
When viewing your segments you will notice that they now display a CMS Publication status.
1. To changes this status, simply edit a Segment and click Settings in the bottom bar
2. Click Publish this Segment to the CMS.
3. Save the Segment.
Upon visiting your Segment list again, you will notice that the CMS Publication Status now reads Published.
What's Next