Skip to main content

SFMC AMPscript Loop - Real-Time Project Scenarios

 Real-Time Project Scenarios


Loops: A single customer can have multiple related records. Without loops, SFMC can only easily display one value.

Loops are used when a subscriber has multiple related records that need to be displayed dynamically in an email, CloudPage, or SMS. They eliminate hardcoding and allow Salesforce Marketing Cloud to process and display an unlimited number of records using the same code.

E-Commerce


%%[
VAR @rows, @count, @i, @row, @item
  • Product Recommendations: SET @rows = LookupRows(

        "Product_DE_AMP",
        "Scenario",
        "Product Recommendation"
    )
  • Abandoned Cart Emails: (SET @rows = LookupRows( "Product_DE_AMP", "Scenario", "Abandoned Cart")

  • Order Summary: SET @rows = LookupRows( "Product_DE_AMP", "Scenario", "Order Summary" )

SET @count = RowCount(@rows)

FOR @i = 1 TO @count DO

    SET @row = Row(@rows,@i)
    SET @item = Field(@row,"ItemName")

    OUTPUT(CONCAT(@item,"<br>"))

NEXT @i
]%%



Banking
  • Transaction Summary

  • Reward Points

Healthcare

  • Appointment Details

  • Test Results

Education

  • Course Lists

  • Student Progress

Loyalty Programs

  • Points Earned

  • Rewards Redeemed

Preference Center

  • Interest Categories

  • Subscription Management


What is a Loop?

A loop is used to execute a block of code repeatedly until a condition is met.

Which Loop is Most Common in SFMC?

FOR Loop.

Why Use Loops?

To process multiple records dynamically and avoid hardcoding.

Which Functions Are Commonly Used with Loops?

  • LookupRows()

  • RowCount()

  • Row()

  • Field()

  • IF

  • ELSEIF

  • ELSE

  • MOD()

  • AND

  • OR


Golden Interview Formula

LookupRows()

RowCount()

FOR Loop

Row()

Field()

Output()


Remember:

Fetch Records → Count Records → Loop Through Records → Read Row → Read Field → Display Data

This is the foundation of dynamic personalization in Salesforce Marketing Cloud.




Comments

Popular posts from this blog

A/B Testing

Confluence link 1:  https://elearningit24.atlassian.net/wiki/external/MzA3YWUxNjI3YzBkNGZiZmFlZTc1ZGIzYmU1ZmM1MmQ   What is A/B Testing? A/B testing, also known as split testing , is a controlled experiment where two versions of a webpage, email, ad, or any digital asset are tested against each other to determine which one performs better. Why? Higher open rates Better Engagement Increased Sales and Lead conversion Reduced unsubscribed rates Date Driven- No assumption & Proven Results Test Type Subject Line Email Content Area From Name Send Date & Time Pre Header   Email Test Template: Friendly and Personalised Straight to the point & Action Oriented Confluence Link 2:  https://elearningit24.atlassian.net/wiki/external/NDk0Zjg0ODk3YjAwNDI5ZjkxOTVmMTAxNTQ3ZjlhNmQ Subject Line A/B Test: A/B Testing Use Case: Optimizing Email Subject Lines for Higher Open Rates Scenario- Subject Line: A company wants to increase the open rates of its promotional emails in Sa...

Email Marketing Campaings

Use Cases of Standard Data Extensions 1. Customer Data Storage Scenario : A retail business wants to store customer information, such as names, email addresses, and purchase history, for email marketing campaigns. Solution : Use a standard data extension to store and manage customer data securely and efficiently. Data Extension Structure Field Name Data Type Length Required Primary Key SubscriberKey Text 50 Yes Yes FirstName Text 50 Yes No LastName Text 50 Yes No EmailAddress EmailAddress N/A Yes No PurchaseHistory Decimal N/A No No Sample Records SubscriberKey FirstName LastName EmailAddress PurchaseHistory 001 John Doe john.doe@example.com 1500.50 002 Jane Smith jane.smith@example.com 200.00 https://mc.s8.exacttarget.com/cloud/#app/Email/C12/Default.aspx?entityType=none&entityID=0&ks=ks%23Subscribers

SQl Query

  Workflow: Journey Builder> Automation Studio> New Automation Enter Query: Drag and drop Schedule in  Start with a Starting Source and the SQL Query> Choose Query> Create New Query Activity> Name your file and add your query (Field name thats part of the DE you create separately- Example: FirstName, LastName, Subscriber Key) Create a new DE in Email Studio with the query field> Select The test DE which was created: Select Target DE and Save & Run Workflow: Select All Activities and Run Workflow: Activity Details: Run Completed with updated DE Edit/ add another query: Copy Source DE and create a new DE with same fields that we are running in SQL: Run the updated SQL Query added Activity and DE updated with Records: Completed Status: Received error: When the Query field and the DE created field does not match When an existing Query is being run, if we try to run another query Fixed the error by matching same field Waiting for existing query to complete