Sequence audiences, reunion wording and registered activity summaries

In GiveCampus Events, available controls depend on your permissions and the interface used by your institution.

For an editable event-sequence outreach with the relevant permissions/features, use its Recipients → Add Recipients controls to add supported sources to the existing audience. The audience editor adds inclusion conditions to the outreach's existing query rather than requiring a single list. Review the generated recipients, exclusions and overlaps; a source-list name does not automatically provide “you were invited because…” wording.

Provide explicit per-recipient group/reunion wording through supported custom recipient fields, such as a precomputed reunion anniversary and class year, and insert the offered merge tokens. Do not assume the editor calculates an anniversary from class year or resolves a recipient's membership in multiple lists to one preferred label. Inspect and test the actual resulting substitutions.

For a complex-event reminder, the Outreach Activities token (selected in the token picker) uses a linked event registration and its registration group. It renders activities with completed activity tickets, including guest names, ticket types, date/time and location; activities with no such tickets are omitted rather than rendered as empty weekend-schedule sections. This is a registration-group summary, not necessarily an individual guest-only itinerary. An unregistered invitation audience or a recipient without the required linked record cannot be assumed to produce that content. Select the token from the current editor; standard event-email template tokens are a separate interface.

For a brunch open to both reunion and non-reunion alumnae, consider a free general event admission option with only the desired activities selected, provided the overall event configuration and affiliation restrictions allow both audiences. They still register within the parent event; this does not create a direct activity-only checkout that bypasses parent registration. Use a separate event if a fully independent registration is required. Preview both intended audiences before launch.