Marketing Cloud Engagement | How to Stop Automation Processing Based on a Specific Field Value Using a Verification Activity

The Marketing Cloud Verification Activity only evaluates the "record count" of a Data Extension (DE). It cannot directly evaluate specific "field values" as a condition (e.g., stopping the automation if IsUpdatedThisMonth does not equal True).

To meet this requirement, the best practice is to verify "the count of records resulting from a data extraction based on the condition." Follow the steps below to configure this workaround.

1. Create a Helper Data Extension and Extract Data

First, create a temporary Data Extension (referred to as the Helper DE) to store only the records that meet your specific criteria, and create an SQL Query Activity to extract the data.

1. Create the Helper DE: Create a simple Standard Data Extension containing only the necessary primary keys (e.g., Name it Check_IsUpdated).

2. Create the SQL Query Activity: Create a query to extract only the records matching the condition (IsUpdatedThisMonth = 'True'). Refer to the sample code below:

SELECT
    SubscriberKey
FROM
    [Original_Data_Extension_Name]
WHERE
    IsUpdatedThisMonth = 'True'
/* Adjust the value (e.g., 1 for Boolean, 'True' for Text) based on your data type */

3. Configure Data Action: Select [Overwrite] for the Data Action on the Helper DE and save.

2. Configure the Verification Activity

Set up a Verification Activity to evaluate the record count in the staging DE created in Step 1.

1. Create a new [Verification] activity in Automation Studio.

2. Select the "Helper DE (Check_IsUpdated)" created in Step 1 as the target.

3. Configure the conditions as follows:

   • Condition: [Count], [Is Equal To], 0

     • This detects if there are 0 records meeting the condition (meaning the required data does not exist).

4. Configure the action as follows:

   • Action: [Stop Automation]

   • Notification: Enter an email address to receive a notification when the automation stops, if necessary.

3. Construct the Automation

In the Workflow tab of Automation Studio, arrange the activities in the following order:

1. Step 1: The "SQL Query Activity" created in Procedure 1.

   • Extracts data matching the condition into the Helper DE.

2. Step 2: The "Verification Activity" created in Procedure 2.

   • If the Helper DE has 0 records, the automation stops here.

3. Step 3 and beyond: Email Send Activities, etc.

   • These run only if the verification passes (i.e., there is at least 1 record meeting the condition).

This configuration ensures that subsequent processes are safely stopped if records with specific values do not exist.