The Contact property value change feature in Advanced Automation allows you to build journeys that respond automatically when a contact’s data changes.
You can use this feature in two ways:
Starting Trigger – Start an automation journey when a contact property value changes.
Wait for Trigger – Pause a journey until a contact property meets the condition you specify.
This functionality helps you create dynamic, event-driven automations that adapt to each contact’s real-time behavior or profile updates.
When setting up Contact property value changes, the available conditions depend on the field type.
Below are the supported conditions for each type:
Is equal to
Is not equal to
Is equal to any of
Is not equal to any of
Is empty
Is not empty
Examples
City is equal to “Kochi”
Tags is equal to any of (“VIP”, “Lead”)
First name is empty
Is equal to
Is not equal to
Is equal to any of
Is not equal to any of
Is empty
Is not empty
Is greater than
Is less than
Examples
Age is greater than 18
Spend (₹) is less than 5000
Score is not equal to 0
Is equal to
Is not equal to
Is empty
Is not empty
Examples
Signup date is equal to 2025-11-01
Last purchase date is not empty
1. Welcome series when a lead is qualified
Property: Lifecycle Stage (Text)
Condition: Is equal to “Qualified”
Action: Start a 3-email welcome + demo CTA sequence.
2. Re-engage when city becomes target location
Property: City (Text)
Condition: Is equal to any of (“Bengaluru”, “Kochi”)
Action: Start localized content flow with city-specific offers.
3. High-value buyers get VIP onboarding
Property: Total Orders (Number)
Condition: Is greater than 3
Action: Enroll in VIP onboarding and send perks.
4. Flag incomplete profiles
Property: First name (Text)
Condition: Is empty
Action: Start a short profile-completion nudge sequence.
5. Anniversary campaign based on signup date
Property: Signup date (Date)
Condition: Is equal to [specific date]*
Action: Trigger an anniversary thank-you email with a coupon.
Tip: Use dynamic date injection or a daily equality check to match dates.
1. Wait until interest is selected before sending content
Property: Interest (Text)
Wait until: Is not empty
Then: Branch content by selected interest.
2. Hold until cart value crosses threshold
Property: Cart Value (Number)
Wait until: Is greater than 2000
Then: Send “free shipping” or “VIP checkout help.”
3. Pause until user provides phone number
Property: Phone (Text)
Wait until: Is not empty
Then: Send WhatsApp opt-in prompt (if applicable).
4. Compliance step — don’t send until age verified
Property: Age (Number)
Wait until: Is greater than 18
Then: Continue with age-restricted content.
5. Nurture resumes once purchase date exists
Property: Last purchase date (Date)
Wait until: Is not empty
Then: Send post-purchase tips and cross-sell.
1. Route leads missing key fields
Property: Company (Text)
Condition: Is empty
Action: Assign to SDR for enrichment task.
2. Suppress free email domains from sales path
Property: Email Domain (Text)
Condition: Is equal to any of (“gmail.com”, “yahoo.com”, “outlook.com”)
Action: Move to self-serve nurture instead of direct sales.
3. Escalate churn-risk based on score
Property: Health Score (Number)
Condition: Is less than 40
Action: Trigger CSM alert and send recovery playbook.
Is equal to | Value exactly matches your input. |
Is not equal to | Value is anything except your input. |
Is equal to any of | Matches if the value equals any one item from your list. |
Is not equal to any of | Excludes values that match any item in your list. |
Is empty | Field has no value (blank/null). |
Is not empty | Field has any value. |
Is greater than (Number only) | Numerically greater than your input. |
Is less than (Number only) | Numerically less than your input. |
For “any of” / “not any of”, enter a comma-separated list (e.g., VIP, Lead, Trial).
Empty checks detect truly blank or null values.
Each field type supports only its listed conditions — this is by design.
For Date fields, pair a daily check with “Is equal to” for recurring triggers like birthdays, anniversaries, or renewals.
When using Wait for Trigger, always include a timeout path (e.g., “If not met in 7 days → send fallback or exit”).
With Contact property value change triggers, Mailercloud now gives you the flexibility to react instantly to user data updates — whether that means starting a new journey, pausing until conditions are met, or improving data routing.
Use this feature to deliver more personalized, relevant, and timely automation flows.
