- 4 Minutes to read
- Print
- DarkLight
Profile Data Changed (New) (C)
- 4 Minutes to read
- Print
- DarkLight
Mapp Engage registers this event when the profile data of a contact changes.
The event settings determine what type of change triggers the event.
Any profile change to any profile attribute.
Any profile change in one or more specific profile attributes.
A specific change of one or more specific profile attributes.
Mapp Engage registers various types of changes.
Profile data changes in the user interface.
Profile data changes transmitted via API.
Hint:
Mapp Engage does not register this event for changes to existing profile values that are made by an import or XML job (asynch SOAP)
API Methods for This Event
The following API methods fire this event:
userUpdateProfile
userReplaceProfile
userReplaceProfileByEmail
The API method membershipUpdateAttribute does not fire this event.
Hint:
The designation (C) means contact-related. In general, you only combine contact (C) events with contact (C) jobs. For more information, see Contact (C) vs. System (S) Automations.
General
Name | Defines the name of the automation. The name is used to identify the automation in the system. The maximum length is 100 characters. |
Description | Provides information about the automation. The description makes it easier to identify the automation in the system. |
Event | Selects the type of event that, when combined with a job, forms the automation. Every time this event occurs, the system executes the dependent job. The job is defined in the Edit Event-based Job window. |
Recommended Automations
An automation is a combination of an event plus a resulting job. The following combinations are recommended. It is possible to create other combinations, as well, but not all combinations of events and jobs result in meaningful system behaviour.
Profile Data Changed (C) + Send HTTP Request (C): This automation sends an HTTP request every time a profile is updated. The request includes the new profile data. You can use an HTTP request to send standard user attributes, custom user attributes, or member attributes.
Profile Data Changed (C) + Store Data in Profile Attribute (C): This automation stores data in a profile attribute whenever the profile of the contact is updated with a certain value. For example, stores the date of profile change.
Profile Data Changed (C) + Add Member to Group (C): This automation adds a contact to a new group whenever the profile of the contact is updated with a certain value. You can use this automation to sort contacts into different groups that match their newsletter preferences.
Profile Data Changed (C) + Send Prepared Message to Contact (C): This automation sends a prepared message to a Contact when their profile is updated with a certain value. You can use this automation to confirm the profile update. For example, if a contact changes their email address, send a prepared message with a confirmation link to confirm the new address.
Define Event
This area defines the specific parameters of the event.
Profile Change: Defines whether the event reacts to any profile change, or is limited to specific profile changes.
Any: The event includes any change that is made to any profile attribute. No specific attribute is defined. No specific new value is necessary.
Specific: The event is limited to profile changes to a specific attribute. Mapp Engage does not check the existing profile attribute value, but only the new value.
Select by Profile Value: This button creates three new fields. These fields limit the event to certain profile changes. For example, you limit the event to recipients who change a custom profile attribute that is named Newsletter_Frequency to the value Daily. You can add up to ten attributes. The rules are combined with AND.
First field: Selects the profile attribute according to which the event is limited. The field displays all standard and custom attributes in the system.
Second field: Defines the relationship between the attribute (first field) and the value (third field).
Third field: Defines the profile change value.
Any Change: Any change to this specific attribute is considered an event. The new value can be any value, including empty.
Equals: The new attribute value exactly matches the value in the input field.
Does Not Equal: The new attribute value does not match the value in the input field.
Starts with: The new attribute value starts with the value in the input field.
Ends with: The new attribute value ends with the value in the input field
Contains: The new attribute value contains the value in the input field
Matches [Regex]: The new attribute value matches the regular expression in the input field.
=: The attribute value equals the value in the input field (only for numeric, boolean, and date attributes).
!=: The attribute value does not equal the value in the input field (only for numeric, boolean, and date attributes).
>: The attribute value is greater than the value in the input field (only for numeric, boolean, and date attributes).
<: The attribute value is less than the value in the input field (only for numeric, boolean, and date attributes).
Case Insensitive: This checkbox ignores differences in uppercase and lowercase.
To select contacts who change their title (gender) to Mr. or Mrs., enter
= 1 for contacts who set their title to Mr., and
= 2 for contacts who set their title to Mrs.
Hint:
Note: To create the case "attribute has any value or is empty," select Matches [Regex] in the second field and enter .* in the third field.
Define Selection
Selection: This drop-down list defines a selection. Applying a selection to a contact (C) event limits the event to contacts whose profile is changed in the specified way and who also fulfil the selection criteria.
To search for a selection in the system, click the symbol.
Actions
The following actions are available:
Edit Job: This button saves the changes and opens the Edit Event-Based Job window.