Alternate Character (AC) fields can be saved on the user profile so Japanese-script details can be captured once and reused across events and communications.
At a glance
Who it affects: Event managers and stakeholders supporting Japan-based events; registrants providing Japanese-script details
Where to find it: User profile fields + event registration fields (path labels to confirm)
Prerequisites: AC fields enabled for the hub/event; Marketo mapping only if integration is in use
Deployment status Source notes show this feature in Staging. Publish/announce only once production deployment is confirmed.
A reusable set of AC fields is stored on the user profile (not captured only per event).
AC field IDs stay consistent across languages; labels localise to the event language (JP/KR/etc.).
AC fields are designed to be usable across events, emails, and integrations.
AC fields use one consistent schema across languages.
The same underlying field keys are used everywhere, but the visible labels translate based on the event language.
Once the attendee’s AC fields are populated, they can be reused instead of re-entered each time.
ac_first_name
ac_last_name
ac_company_name
ac_title
ac_department
Confirm AC fields are enabled for the hub (and available for event setup).
Add the AC fields to the registration data captured for relevant Japan-based events.
Use AC fields in email templates where Japanese-script personalisation is required.
Screenshot placeholder
Capture: Registration form showing AC labels displayed in Japanese
Alt text: “Registration fields list showing Alternate Character fields labelled in Japanese.”
Marketo (if enabled): source notes indicate the corresponding fields already exist in Marketo, so AC values can be mapped without creating new Marketo fields.
Consider including AC fields in exports/reporting for operational workflows (badge printing, admin checks), where applicable.
If an attendee’s AC fields are missing, emails should fall back to standard profile fields (see “Email merge fields upgrade”).
UI labels may vary by event language; field keys remain stable.
Do AC field keys change by language? No. Field keys are consistent; only labels localise.
Is this Japan-only? The localisation model supports non-Latin scripts generally (e.g., Japanese, Korean), but Japan is the primary use case for this rollout.
Last updated
