This event reacts to an external event, such as a purchase in an online shop.

Hint:

This event requires activation and correct setup of conversion tracking. Both conversion tracking with and without cookies can be used as the event. See Basics

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 behavior.

  • Conversion Registered (C) + Store Data in Profile Attribute (C): This combination stores information in a contact's profile when he completes a conversion. For example, this could be the value of the order and the date and time of the conversion.

  • Conversion Registered (C) + Increase or Decrease Profile Value (C): This combination counts the total number of times a contact completes a conversion and stores this information in his profile.

Define Event​

This area defines the specific parameters of the event.

  • Conversion Tracking: This drop-down list defines the name of the conversion tracking event. You can only select one conversion tracking per automation.

  • Group Name: This drop-down list restricts the event to conversions produced by messages in one specific group. If you select a group, three additional bullet points appear. If the MID is not included in your conversion tracking, you cannot filter the event for a specific MID.

    • Any Message: The event includes conversions that result from any message in the group. This includes conversions that result from all past and future sendouts in this group, as long as the conversion takes place when the automation is running.

    • Scheduled/Sent: The event is limited to conversions that result from one specific scheduled or sent message in the group. Select the message from the drop-down list.

    • Prepared Message: The event is limited to conversions that result from a sendout of the selected prepared message. This includes group and single sendouts of the prepared message. This also includes all past and future sendouts of the prepared message, as long as the conversion takes place when the automation is running.

  • Message Category: This drop-down list restricts the event to conversions resulting from messages in a specific message category. Since message categories are not group-specific, you can use a message category to create an automation that reacts to messages in multiple groups at once. If the MID is not included in your conversion tracking, you cannot filter the event for a specific message category.

  • Amount: These fields restrict the event to conversions of a certain value. This is the total value of purchases, not the number of items purchased. If the amount parameter is not transmitted to Engage in the conversion tracking event, you cannot filter the event for a specific amount.

    • =: The conversion value equals the value in the input field.

    • !=: The conversion value does not equal the value in the input field.

    • >: The conversion value is greater than the value in the input field.

    • <: The conversion value is less than the value in the input field.

  • Parameters: This button creates three new fields. These fields restrict the event to conversions containing certain parameters. You can add up to 10 parameters. The rules are combined with AND. The parameter in the first field must exactly match the parameter transmitted in the conversion tracking event.

    • First field: This input field defines the parameter.

    • Second field: This drop-down list defines the relationship between the parameter (first field) and the value (third field).

    • Equals: The parameter exactly matches the value in the input field.

    • Does Not Equal: The parameter does not match the value in the input field.

    • Starts with: The parameter starts with the value in the input field.

    • Ends with: The parameter ends with the value in the input field.

    • Matches [Regex]: The parameter matches the regular expression in the input field.

    • =: The parameter equals the value in the input field (only for numeric, boolean and date values).

    • !=: The parameter does not equal the value in the input field (only for numeric, boolean and date values).

    • >: The parameter is greater than the value in the input field (only for numeric, boolean and date values).

    • <: The parameter is less than the value in the input field (only for numeric, boolean and date values).

    • Third field: This input field defines the parameter value.

  • Case Insensitive: This checkbox ignores differences in uppercase and lowercase.

Hint:

Use the parameter fields to add additional values from the conversion tracking to the contact profile. To do so, add any value in the first parameter field. Leave the second and third fields empty. When you create the job (for example, ​Store Data in Profile Attribute (C)​), add an additional parameter to the job. For this parameter, check the ​Use Event Parameter​ field. The drop-down box now displays the additional parameter you created. Whatever value the conversion tracking transmits to Engage for this parameter, this value is added to the recipient's profile.

Example: The conversion sends the order ID to Engage with the parameter ORDERID. You want to add this information to the contact's profile. In the event ​Conversion Registered (C)​, you create a new parameter. The first field you enter ORDERID. The other two fields you leave empty. In the ​Edit Event-based Job​ window, select the job ​Store Data in Profile Attribute (C)​. Add an additional parameter to the job. Select the custom user attribute ​LastOrderNumber​ and click the ​Use Event Parameter​ field. From the drop-down field, you select ORDERID. When the contact completes a conversion, the conversion event sent to Engage includes the parameter ORDERID=123456. The automation stores the value 123456 in the contact's profile in the ​LastOrderNumber​ attribute.

Actions

The following actions are available: