1. Campus-Based Personalization
What it does:
Displays content tagged with the user’s campus.
How it works:
Content items can be tagged with one or more campuses (e.g., Campus A, Campus B).
Users only see content if their campus matches the tag.
Example: If an event is tagged for Campus A and B, someone at Campus C will not see it.
Setup:
Available within content list features and events.
In edit mode, toggle Campus-Based Personalization on the feature.
Works with Rock CMS or Apollos CMS, as long as the campus name matches exactly.
2. Persona-Based Personalization
What it does:
Curates content based on user personas or roles.
How it works:
Content can be tagged for specific personas (e.g., New Believer, Volunteer, Parent).
Users only see content aligned with the persona(s) tied to their profile.
Setup:
Use tags to associate content with personas.
Personas must be configured in the CMS and connected to user profiles.
3. Personalization by Engagement/Following
What it does:
Shows users content from the people, ministries, or groups they follow.
How it works:
If a user follows a pastor, ministry, or content category, they will see related content in their feed.
This creates a dynamic, user-driven personalization layer.
Setup:
Enable following functionality in Apollos.
Encourage users to follow ministries or leaders they want updates from.
Best Practices
Tag consistently: Ensure campus names, persona labels, and followable categories are spelled and matched correctly.
Test features: Use edit mode to preview personalization behavior before publishing.
Educate users: Teach your community how following works so they can customize their experience.
With these three types of personalization—Campus, Persona, and Following—you can ensure your community sees the most relevant and engaging content.