​
Purpose of the document

Describe the scenarios for using Allyy’s personalized content recommendations in the Client’s Content Management System

​
Option 1: Real-Time Recommendation API

Integrate directly with our real-time Recommendation API. Each time a personalized page is rendered, the CMS sends a request with the visitor ID and receives a list of recommended content items in response. Link to the API documentation here

Pros:

✅ Simple and fast to integrate.✅ Minimal implementation effort, reducing potential errors.

Cons:

❌ Adds 200–300ms latency to page load (may impact user experience)❌ Depends on Allyy.io’s uptime — in rare cases of downtime, fallback logic is required on the CMS side

​
Option 2: Recurrent Database Load into the CMS

We periodically push content recommendations directly into a dedicated table in your CMS database (e.g., daily or more frequently). This requires permission to write to a specific table in the CMS.

Pros:

✅ Zero delay during page loads✅ Recommendations can be easily combined with other CMS data

Cons:

❌ Requires write access to the CMS database, which may be restricted due to internal security or GDPR policies

​
Option 3: File-Based Data Transfer via Cloud or SFTP

We deliver content recommendation files (CSV format) to your cloud storage or SFTP server. If your CMS supports file import, it can regularly ingest and update its content from these files.

Pros:

✅ Zero delay during page loads✅ Easy to merge with existing CMS content

Cons:

❌ Only feasible if your CMS supports scheduled file imports