AMPscript Day 4 - Statement IIF() Function Guide

 Salesforce Marketing Cloud (SFMC) - IIF() Function Guide

What is IIF()?

IIF() is a shorthand AMPscript conditional function used to return one value when a condition is true and another value when false. Syntax: IIF(condition, value_if_true, value_if_false)

Use case to perform:

Use Case 1: Personalized Greeting IIF(Gender == "Male","Mr.","Ms.") 

Use Case 2: Loyalty Member Classification IIF(MemberStatus == "Gold","Premium Benefits","Standard Benefits") 

Use Case 3: Dynamic Discount Assignment IIF(TotalPurchase > 10000,"20% OFF","10% OFF") 

Use Case 4: Age Verification IIF(Age >= 18,"Adult","Minor") 

Use Case 5: Cart Abandonment Journey IIF(IsCartAbandoned == "True","Complete Your Purchase Today","Thank You For Shopping") 

Use Case 6: Mobile App Adoption IIF(IsAppUser == "Yes","Open App","Download App") 

Use Case 7: Lead Scoring IIF(LeadScore > 80,"Hot Lead","Cold Lead") 

Use Case 8: Dynamic Subject Line IIF(OpenCount > 5,"We Miss You Less!","We Miss You!") 

Use Case 9: Membership Discount Nested IIF for Gold/Silver/Bronze discounts

Data Extension: This DE stores input attributes (customer/lead data) for personalization, segmentation, and dynamic messaging.

>Now that we have a DE, will proceed to Email Studio> Create new content and select a black template> Drag and drop HTML.

Flow Diagram:

Code:

%%[

/*Declare All Variables*/

VAR @Gender, @Greeting, @MemberStatus, @Benifits, @TotalPurchase, @Discount, @Age, @Classification, @IsCartAbandoned, @SubjectLine, @IsAppUser, @OpenCTA, @LeadScore, @LeadStatus, @OpenCount, @DynamicSubject, @Tier, @NestedDiscount

/*Declare values from Attribute*/

SET @Gender = AttributeValue("Gender")

SET @MemberStatus = AttributeValue("MemberStatus")

SET @TotalPurchase = AttributeValue("TotalPurchase")

SET @Age = AttributeValue("Age")

SET @IsCartAbandoned = AttributeValue("IsCartAbandoned")

SET @IsAppUser = AttributeValue("IsAppUser")

SET @LeadScore = AttributeValue("LeadScore")

SET @OpenCount = AttributeValue("OpenCount")

SET @Tier = AttributeValue("Tier")

/*Apply Logic*/

/* Use Case 1: Greeting */

SET @Greeting = IIF(@Gender == "Male", "Mr.", "Ms.")

/* Use Case 2: Loyalty */

SET @BenefitsTier = IIF(@MemberStatus == "Gold", "Premium Benefits", "Standard Benefits")

/* Use Case 3: Discount */

SET @Discount = IIF(@TotalPurchase > 10000, "20% OFF", "10% OFF")

/* Use Case 4: Age Verification */

SET @Classification = IIF(@Age >= 18, "Adult", "Minor")

/* Use Case 5: Cart Abandonment */

SET @SubjectLine = IIF(@IsCartAbandoned == "True" OR @IsCartAbandoned == true, "Complete Your Purchase Today", "Thank You For Shopping")

/* Use Case 6: App Adoption */

SET @AppCTA = IIF(@IsAppUser == "Yes", "Open App", "Download App")

/* Use Case 7: Lead Scoring */

SET @LeadStatus = IIF(@LeadScore > 80, "Hot Lead", "Cold Lead")

/* Use Case 8: Dynamic Subject Line */

SET @DynamicSubject = IIF(@OpenCount > 5, "We Miss You Less!", "We Miss You!")

/* Use Case 9: Nested Membership Discount */

SET @NestedDiscount = IIF(@Tier == "Gold", "30% OFF", IIF(@Tier == "Silver", "20% OFF", "10% OFF"))

]%%

Render Email: %%=v(@Greetings)=%%<br>

%%=v(@Benifits)=%%<br>

%%=v(@Discount)=%%<br>

%%=v(@Classification)=%%<br>

%%=v(@OpenCTA)=%%<br>

%%=v(@LeadStatus)=%%<br>

%%=v(@DynamicSubject)=%%<br>

%%=v(@NestedDiscount)=%%<br>

Output:

*Numeric Fields: Do not wrap numeric values in quotes when running mathematical comparisons (e.g., > 10000 or >= 18), as quotes force the compiler to treat them as text, breaking mathematical evaluations.

*A salutation is a formal greeting used at the very beginning of a letter, email, or official message. It is the direct way you address the person you are writing to before diving into the main content

*A nested discount is a conditional logic structure where one IIF() statement is placed inside another IIF() statement.

Instead of evaluating only two options (True or False), a nested structure allows your code to evaluate multiple conditions in sequence until it finds a match.

Avoid nesting IIF() deeper than 3 levels (e.g., Gold ➡️ Silver ➡️ Bronze ➡️ Baseline).

Q&A

Q: What happens in Use Case 1 if a subscriber's Gender field is completely blank?

• Answer: The current expression IIF(@Gender == "Male", "Mr.", "Ms.") will check if it equals "Male". Since a blank/null value does not match "Male", the condition falls through to the false branch and outputs "Ms.". The Fix: To avoid misgendering blank records, wrap it in a data check to supply a neutral fallback: SET @Salutation= IIF(Empty(@Gender), "Customer", IIF(@Gender == "Male", "Mr.", "Ms."))

Q: In Use Case 5, what happens if IsCartAbandoned contains invalid text strings instead of a boolean value?

• Answer: If the data syncing from your web platform contains mixed text strings (such as "yes", "y", or "1"), the rigid boolean script IIF(@IsCartAbandoned == "True" OR @IsCartAbandoned == true...) will fail and default to the "Thank You For Shopping" message. The Fix: Expand the boolean safety logic to catch alternative indicators: SET @SubjectLine = IIF(@IsCartAbandoned == "True" OR @IsCartAbandoned == true OR @IsCartAbandoned == "Yes", "Complete Your Purchase Today", "Thank You For Shopping")

Q: Why are we declaring all 9 use cases inside a single block at the top of the email instead of calculating them inline as they appear?

• Answer: Placing calculation scripts scattered inside HTML structure forces the Salesforce Marketing Cloud parser engine to repeatedly pause, execute script logic, and resume rendering layout cells. Wrapping code elements inside a unified initialization block speeds up processing times, reduces server timeouts on massive sends, and makes your email architecture much easier to debug.

---