This event fires when a member is added to the group with a double opt-in process.

  • First the contact is invited to the group with the notification mode ​​Invite​​.

  • Second, the contact confirms the subscription (opt-in) by clicking on a confirmation link in the message.

The event only fires after the second step!

Included

Not Included

This event includes the following ways to add members to a group in Mapp Engage,all with the notification mode ​Invite​ and only after the successful confirmation.

  • Members imported via CSV or XML file into a group. This includes file import in the Mapp Engage interface, with an automation or via the API.

  • Single members added to a group individually in the Mapp Engage interface.

  • Single members added to a group individually with an automation.

  • Members added with certain API methods. ​​

This event does not include:

  • Recipients automatically added to the group as a result of using the API methods ​messageSendSingle​ and ​messageSendTransactional​.

  • Members added anywhere in the system with the notification mode ​Add with Message​ or ​Add without Message​.

  • Members created with Control XML.

API Methods for this Event​

The following API methods fire this event: ​membershipSubscribe​ and ​membershipSubscribeByEmail​

The API methods​messageSendSingle​and​messageSendTransactional​are not related to this event, even though the recipients of single messages are added to the group during sendout.

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.

Event

Job

Description

Subscribed to Group (C)

Send Prepared Message to Contact (C)

This automation sends a prepared message to each new subscriber. The prepared message is sent after the opt-in process is complete. The prepared message does not replace the opt-in messages.

Subscribed to Group (C)

Store Data in Profile Attribute (C)

This automation stores information in a recipient's profile when he subscribes to a new group. This includes subscriptions via API or in the user interface. For example, this information could be the event processing date, which in this case is the subscription date.

Subscribed to Group (C)

Add Member to Group (C)

This automation adds a contact to a group when he subscribes to a different group. A subscription always includes an opt-in confirmation step. The member is thus added to two groups at once.

Define Event​

This area defines the specific parameters of the event.

Setting

Description

Group Name

This drop-down list limits the event to members added to a certain group. Use the symbol to search all groups in the system.

Select by Profile Value

This button creates three new fields. These fields create a selection. They limit the event by selecting only contacts with certain profile attribute values. New members added to the group who do not have the specified profile attribute values are ignored. It is possible to add up to 10 attributes. The rules are combined with AND.

  • First field: This drop-down list selects the profile attribute according to which the event is limited. Standard and custom attributes are listed.

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

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

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

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

    • Ends with: The attribute value ends with the value in the input field

    • Matches [Regex]: The 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).

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

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

Define Selection​

Setting

Description

Selection

This drop-down list defines a selection.

Applying a selection to a contact (C) event limits the event to those contacts who fulfill the selection criteria.

The selection is applied in addition to any profile value restrictions.

Use the to search for a selection in the system.

Actions

The following actions are available: