Format affiliations and understand guest grouping in offline event imports

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

Use the event's current import template and exact configured affiliation labels/options. In its Affiliations column, the parser separates affiliations with commas, separates a label from values with a colon, and separates multiple values with hyphens. For example, if these labels/options exist: Alumni:2001,Parent:2026. Keep this entire value in one quoted CSV cell when it contains a comma. Do not insert spaces or substitute labels that are not configured on the event.

When an affiliation has selectable values, the validator requires a value even if that affiliation is called Parent or Student. A blank year will fail for such a configured affiliation; do not invent a year. Multiple values within one affiliation must be enabled and respect its selection limit and permitted options. Multiple different affiliation labels are distinct from allowing multiple values for one label.

Each offline row creates a new registration, registration group and attendee. There is no shared-group key in this path to attach several CSV rows as guests of one registrant. Repeated email addresses do not mean a group. Use a supported registration/guest workflow or ask support to assess the grouping request before importing. A post-import merge tool is not available in this workflow.