Experience ID Change Event

About Experience ID Change Events

When contacts undergo changes in your directory, you can automatically set off different tasks, such as sending notifications (such as emails or Slack messages), creating tickets (in Qualtrics, Freshdesk, or elsewhere), and much, much more. These tasks can be triggered by contact data changes, subscription changes, or interaction changes.

Setting up an Experience ID Change Event

1. Go to the stand-alone Workflows page.
   
2. Click Create a workflow.
3. Select Started when an event is received.
4. Name your workflow.
5. Select where to create your workflow.
   
   Attention: Experience ID change events can only be created as stand-alone workflows.
6. Click Create workflow.
7. Search for and select Experience iD Change.
   
   
8. Select the kind of change you want to monitor:
   • Contact data change: When contact data is added, updated, or deleted.
   • Directory subscription change: When a contact subscribes to or unsubscribes from a directory.
   • Mailing List subscription change: When a contact subscribes to or unsubscribes from a mailing list.
   • Interaction change: When interaction data fields, including transactional and enrichment data, are added, updated, or deleted.
9. Click Next.
10. If you are monitoring contact data changes, see Contact Data Changes for instructions on how to finish configuring your task. If you are monitoring interactions and transactions, see Interaction Changes.

Contact Data Changes

After setting up your Experience ID Change Event, follow these steps to configure the event for contact data changes. The event can be set off by contact data being added, updated, or deleted.

1. Select which directory to monitor for contact changes.
   
2. Select the types of changes to monitor. You can choose from the following:
   • Contact data has been created
   • Contact data has been deleted
   • Contact data has been updated
   Attention: Contacts opting in or opting out will not trigger this event.
3. Select Add embedded data field and select a field from your directory if you want to add embedded data fields for use in your workflow. This step is optional. The fields you add can be used in the tasks and conditions within your workflow.
4. Click Save.

Subscription Changes

After setting up your Experience ID Change Event, follow these steps to configure the event for contact subscription changes. The event can be set off by contacts subscribing or unsubscribing from a mailing list or directory.

1. Select which directory to monitor for contact subscription changes.
   
2. If you selected Mailing List subscription change while setting up your event, select a specific list from the directory to monitor.
3. Select what subscription behaviors you want to be notified about. You can choose from the following:
   • Subscribes to the list/directory
   • Unsubscribes from the list/directory
4. If desired, select Add an embedded data field and choose a field from your directory if you want to add embedded data fields for use in your workflow. The fields you add can be used in the tasks and conditions within your workflow.
5. Click Save.

Interaction Changes

After setting up your Experience ID Change Event, follow these steps to configure the event for interaction data changes. The event will be set off by interaction data fields being added, updated, or deleted.

1. Select which directory to monitor for interaction changes.
   
2. Select the type of changes to monitor.
3. Click Add a data field and select a field from your directory to add interaction data fields for use in your workflow. The fields you add can be used in the tasks and conditions within your workflow.
   Qtip: Adding interaction fields is recommended if you want your workflow to be triggered by a particular interaction change. Adding embedded data fields is recommended if you want to add additional information to your workflow
4. Click Save.

Setting Conditions for an Experience ID Change Event

Conditional statements apply All or Any to define when a task should be triggered. In “all” conditions, every condition listed below must be met. It is similar to joining statements by “and.” In “any” conditions, any of the conditions can be met, but not all have to be. It is similar to joining statements by “or.”

Example: In this example, only 1 of the 2 conditions must be met for the task to be triggered.

The conditions you set for an experience id change event can be based off of various pieces of information about the contact.

Conditions for Contact Data Changes

• Contact: Contact information like first name, last name, email address, and more.
• Contact ID: The Qualtrics ID associated with each contact.
• Embedded Data: Embedded data stored for the contact.
• Event Type: The specific event the contact triggered; either Contact Created, Contact Deleted, or Contact Updated.

Conditions for Interaction Data Changes

• Event Type: The specific event the contact triggered; either Interaction Created, Interaction Updated, or Interaction Deleted.
• Main Contact Data: Data saved within the contact, like contact created data, email, first name, and more.
• Other Contact Data: Interaction data and embedded data stored for the contact. This is selected in the event set-up.
• Transaction ID: The ID of an individual transaction.

FAQs