You can set an alternate unique ID when you want your Automated Program to treat each entry as a separate journey, even if multiple entries share the same email address. This is useful for programs that track repeated actions such as orders or registrations.
Quick Reference (Advanced Users) - Click to Expand
- Where to set: Settings → Program Settings → Alternate Unique Identifier
- Why use it: Allows multiple entries with the same email address
- Common fields: Order ID, Submission ID, Registration ID
- Requirement: Field must exist on all records entering the program
- Reporting: Journeys and step tracking follow the alternate ID
Try it like this: Create a program that processes every form submission separately. Set “Form Submission ID” as your Alternate Unique ID so each submission enters as its own journey.
What the Alternate Unique ID Does
By default, Act-On uses a contact’s email address as the unique identifier. This means a contact can only enter and move through a program once at a time.
When you choose an alternate unique ID, Act-On uses that field instead of the email address. This allows:
- Multiple entries for the same email address
- Separate journeys for repeated actions
- Parallel program processing for the same contact
Alternate unique IDs work well for:
- Event or session registrations
- Order workflows
- Form submissions
- Ticket or case creation
How to Set an Alternate Unique ID
- Open your Automated Program by going to Automation → Automated Programs and selecting the program to edit.
- Select the Settings tab:
Find the Alternate Unique Identifier dropdown and choose the field you want to use instead of Email Address.
- Save your program.
Important: Every contact entering the program must have a value for the alternate ID field. Contacts missing the field cannot enter the program.
When to Use an Alternate Unique ID
Alternate IDs are best when you want to track actions rather than people. Use them when:
- Each order must trigger a confirmation sequence
- Each loan, mortgage or credit ID requires a specific message for that agreement
Best Practices
- Select a field that is guaranteed to be unique for each entry
- Verify your lists and segments always contain the alternate ID field
- Document your chosen ID in the program description for your team
- Test with several entries to ensure the behavior is correct