How does custom-field logic work in workflows?
Custom field logic uses your specific data fields to drive automation decisions:
How it works:
Your database contains custom fields beyond standard attributes (name, email). Automation conditions evaluate these fields to determine paths or content. "If industry equals 'healthcare', show compliance-focused messaging."
Common custom field uses:
Preference fields: Product interests, communication preferences, content topics. Status fields: Customer type, subscription level, account status. History fields: First purchase date, total spend, product categories purchased. Calculated fields: Days since last purchase, engagement score, lifetime value.
Logic applications:
Branching: Different paths based on field values. Content insertion: Merge field values into message content. Suppression: Skip sends if field conditions are not met. Routing: Different treatments for different field values.
Custom fields extend automation beyond the obvious. Your unique data enables personalization specific to your business.
Was this answer helpful?
Thanks for your feedback!