Marketing Automation Tool Events

Here are all the Events logged into Profiles as they interact with your Marketing Automation tool activities.

The Event data associated with each Event allows you to create Segments in Audience to easily target Profiles in your APSIS One activities.


In this article


Enter Flow

The Profile entered a Marketing Automation flow. Here are the types of data associated with this Event:

activityId: The ID for the particular activity that is considered the source of the Event. To locate an activity ID, open the activity. On your browser, take a look at the URL: the ID is the series of characters at the end of the URL. For example: "d9dda47c-6145-4a6d-96bb-63ec2c87b280".

dstNodeId: Refers to the ID of the destination node, or the ID of the specific node that the Profile moved onto. In this case, the ID corresponds with the node that follows the Listen Node in this particular flow.


Move Profile

The Profile moved, in a Marketing Automation flow, from one node to another. Here are the types of data associated with this Event:

activityId: The ID for the particular activity that is considered the source of the Event. To locate an activity ID, open the activity. On your browser, take a look at the URL: the ID is the series of characters at the end of the URL. For example: "d9dda47c-6145-4a6d-96bb-63ec2c87b280".

srcNodeId: Refers to the ID of the source node, or the ID of the specific node that the Profile moved from.

dstNodeId: Refers to the ID of the destination node, or the ID of the specific node that the Profile moved onto.


Exit Flow

The Profile left the Marketing Automation flow. Here are the types of data associated with this Event:

activityId: The ID for the particular activity that is considered the source of the Event. To locate an activity ID, open the activity. On your browser, take a look at the URL: the ID is the series of characters at the end of the URL. For example: "d9dda47c-6145-4a6d-96bb-63ec2c87b280".

points: The abstract numeric value assigned to the Profile upon reaching the Finish node and completing the flow.

srcNodeId: The ID of the specific node that the Profile left the flow on.

reason: The reason the Profile left the Marketing Automation Flow. A string (text) value.

Read about the possible values below:

  • Finished: The Profile reached the Finish Node and completed the flow.

  • MatchTags: The Profile matched the Tag specified in the Flow Settings under Terminate.

  • OverLimit: The Profile has entered the flow the maximum amount of times specified in the Flow Settings.

  • CheckedProfile: The Profile didn't pass a Check Profile node, and the path for those who don't match was the final node of the flow, where they left.

  • Reset: The Profile was removed from the flow when pausing and reactivating the flow.

  • NodeDeleted: The Profile was in a node that was deleted, and left the flow.

  • MissingConsent: The Profile is missing consent for the node's given channel.

  • TooManyHardBounces: The Profiles email address bounced enough times to reach the bounce limit.

  • MissingEmail: The Profile does not contain an email Attribute, necessary for the email node.

  • MissingSMS: The Profile does not contain an SMS Attribute, necessary for the SMS node.

  • ProfileNotRetrieved: Technical error that prevented the Profile from being found by an email node. Please contact support.

  • ProfileLocked: The Profile was locked in Audience.

  • AttributeNotFound: The Profile does not contain the Attribute necessary to complete the email node.

  • AttributeValueNotFound: The Profile does not contain the Attribute Value necessary to complete the email node.

  • UnknownReason: Unknown reason. Please contact support.

  • WebhookError: The Webhook node returned an error, resulting from a failed request.

  • InsufficientCredits: Your APSIS One account does not contain enough SMS credits, so the Profile left the flow in the SMS node.

  • Bounce: The Profile's email address or mobile number bounced in the Email or SMS node.

  • Timeout: The Profile didn't perform an action specified by the Wait for Event node, and the path for those who don't act in time was the final node of the flow, where they left.


Third Party Events

Whenever an email or SMS message is sent through the Marketing Automation Tool, the Events are then part of the tool's domain. Check the Email or SMS tool Events for more information.

Did this answer your question?