| Page Properties | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Then, sort the content. This step is optional. If you don’t, it defaults to release date descending, most recent first.
Some kind of copy and paste “formula” <<< actually maybe just visualize this formula above. Copy/paste doesn’t achieve a lot and it’s just repetitive?
...
Must do
...
Optional
...
Sort content (optional)…
...
Content bucket(s): ____
...
+ Session status: ____ + Tags: ____
...
Copy and paste the form below
I’d like this module to… |
Show these content type(s): This field is required. The rest are optional.
Then sort it all by: |
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Pull content types (required)
First, decide which type of content you’d like to appear in the module.
...
Note that the module will appear empty whenever there aren’t sessions with the specified status. For example, you might not choose Live now if your event has a lot of downtime in between live sessions.
...
| Expand | ||
|---|---|---|
| ||
You can narrow down any content type using tags. Optional. You can pick one or multiple tags. If you don’t specify tags, any content from the bucket can be pulled into the module. If you do specify tags, only content that has that tag applied to it will appear in the module. Choose one or more tags:
|
...
These are custom tags that you create then apply to each piece of content that you’d like to appear in the module. Layout tags are the simplest way to group content. Usually, they match your site’s page or module titles. For example, if a module is titled Leadership, you can make a
You create these custom tags. They’re topics or interests. Attendees select from these tags during onboarding.
|
Tags
You can narrow down any content type to show only content that has specific tags applied to it.
Choose any profile, layout, and/or access level tags
Profile tags are any tags attendees select when they create their profile. For example, an onboarding question might ask about their interests, with multiple options like Leadership and Design. Any of these tags can be applied to related content and pulled into the module.
Note that every attendee will see the same content, even if they didn’t select Leadership as one of their interests. If you want to show attendees personalized recommendations, see the options below.
If the module you’re creating isn’t related to any profile tags, you should create a new layout tag. Usually, a layout tag simply matches the module title or page title. For example, if a module is titled Featured Sessions, create a Featured Sessions tag and add it to each piece of content that you’d like to appear in that module.
Access level tags are… You have content behind a ticket paywall. You want to group it together in one module.
Make personalized recommendations using tag types
Recommend content with dynamic tags
To recommend content based on profile tags that attendees select:
Choose any profile tag type(s)
People will only see the tags they selected in their profile setup. For example, if the module pulls interest tags, one person will only see content tagged with Leadership, and another will only see content tagged Design.
Note that if someone didn’t select any tags for that type, they’ll see content with any tag. For example, if they didn’t select interests, they’ll see content about any interest.
The require_some_preferred use case… encourage users to see other content to broaden their horizons.
To show attendees content based on access level:
Access level tag type: to only show attendees content that matches their access level
Recommend content/matchmaking/dynamic
content changes per person. require users to have the tag in order to see it
add_users_tag_types []
Recommendations or locked content.
you choose the tag type (i.e. “interests”) and it will recommend content with interest tags that match what the attendee selected (i.e. “food“ and “sports”)
require_some_preferred_tags_of_type:
Recommendations or locked content where you want to encourage users to see other content they didn’t buy tickets for or to broaden their horizons.
need use case / example for this, don’t understand
SHOULD I TIE THIS IN ONLY WITH PROFILE TAGS?
...
| Anchor | ||||
|---|---|---|---|---|
|
Optional, Only pick 1
If you don’t choose a sort, it defaults to release date descending (most recent first.)
Sort by… GROUP THESE OR ADD DESCRIPTIONS FOR USE CASES?
Release date (ascending=most recent is last, or descending=most recent first)
Not just for sessions. For example, a library content page might not become available until a specific date.
when it’s viewable, which is usually well before the session starts, so people know it’s happening and can add it to their schedule.
Start date (ascending=most recent is last, or descending=most recent first)
Only sessions
when the session actually begins
Alphabetical
by title or speaker’s first name
Numerical (ascending or descending)
use it if the first character in the title are numbers. Example:
1 Session2 Sessionnote that it won’t sort letters. Example:
Session 1Session 2will not sort in numerical order
Random
different every ime you reload the page
Popularity - Tag score then date <<confirm that. scrilla said “prob” in a comment
| Warning |
|---|
Unsure if these are for modules/what they are
Pretty sure these aren’t for modules
|
...