Changes in Agenda 3

Watch our webinar on these changes

If you've worked with previous version of the Agenda you should feel comfortable working with the new version as well, changes introduced in version 3 mostly relate to streamlining and simplify names of various options.


Session tags are now managed separately from sessions, meaning there's a new section in Backstage for managing them and that the way you link tags in the XLS files is different.

Having tags as a separate entity helps ensuring colours and labels are consistent throughout the app.


fp_ext_id name tag tag_color tags.0


sess1 Registration      


sess2 Breakfast Food #ff0000 food  
sess3 Welcome Keynote #00ff00 keynote  
sess4 Working lunch Food #ff0000 food workshop

tag and tag_color have been replaced with tags. You can assign multiple tags per session, to add a new one simply increase the number at the end of the field (starting with 0) ex. to add three tags:

fp_ext_id name tags.0



sess5 Breakout food workshop keynote


fp_ext_id label background_color
food Food #ff0000
keynote Keynote #00ff00
workshop Workshop #0000ff

Note: If you continue to use tag and tag_color, those fields will be used as a fallback when displaying sessions, but filtering will not work on those sessions.

Tip: Pick easy to remember IDs when creating tags instead of randomly generated ones. This way you can efficiently update sessions.xls.


Location links now have to be specified using ID of the location as set-up in the Maps module.


fp_ext_id name location location_link
sess1 Registration Lobby loc1
sess2 Breakfast Lobby loc1
sess3 Welcome Hall A hall-a
sess4 Working lunch Chalet Suisse chalet



fp_ext_id name
loc1 Lobby
hall-a Hall A
chalet Chalet Suisse

Note: You can still continue using location field (Location label in Backstage), but the linking won't work. Use this if you don't have maps set-up on your event

Note: Inactive location option has been removed due to above behavior.

Note: To personalize location in-app, you can use Location label field in Backstage (location in XLS) with template fields. ex. Table {{activatedPerson.dinner_table}} will appear as Table 2 in-app for participants who have dinner_table field set to 2.

Registrations and targeting

Names of options used for visibility and appearance of sessions in-app have updated with a new language:

Old name New name
Status Appearance
Auto Default
Inactive Hidden
Active N/A
Unregistered N/A
Registered With registration checkmark
Target status Appearance when targeted or registered
Auto Default
Inactive Hidden
Active Without registration checkmark
Unregistered N/A
Registered N/A

Note: Rules on when each of the settings is applied have changed to match the new wording. Previously Target status value would be applied only for targeted sessions, now it applies to both -targeted and registered sessions.

Tip: To completely hide a session from the app you can either delete it, or set both Appearance and Appearance when targeted or registered to Hidden.

Configuring session list

Previously configuration was split between multiple preference panes, now all configuration options can be found in Sessions > Preferences > Session list.

Track session formatting

Number of options available for displaying track sessions has been reduced and language has been made clearer:

Old name New name
Format of the slots in the session list Track sessions to display
Selected sessions are presented OUTSIDE their slot N/A
Selected sessions are not presented WITHIN their slot All
Shows either the selected session or the slot N/A
Shows only selected sessions N/A
Shows selected sessions or their slot when none is selected Targeted or registered only (or all if no targeted or registered)
Shows only master sessions None (master session opens detail page)

Tip: Missing options can be still reproduced in combination with Automatically expand master sessions and content filters.

In-App Filtering

Apps will no longer automatically generate filtering options based on session data, instead filters need to be set-up manually in Backstage. Filters can be only enabled for choice metadata fields.

In-addition to choice fields, automatic filters can be configured for registration status, tags, and bookmarks.


Backstage configuration


In-App Filtering


In-app filtering configuration

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Please sign in to leave a comment.