Here is a good way to display a grid of external content in an email without repeating a significant amount of AMPScript. It utilizes an XML string and uses XPATH to retrieve content using the BuildRowSetFromXML() function.
Slide deck from my ExactTarget Connections Conference 2014 presentation
Double Wide v2 – Responsive Email Pattern
All AMPScript Functions
Product Data Extension
Email Init Section
Content Area Init Section
Content Area Body
Questions? Comments? Feel free to leave a comment below.
Data Extensions in the Salesforce Marketing Cloud platform are simply database tables in which you can store data you need for your campaigns.
You can add rows to data extensions using:
With the API, you have a few options — SOAP being the most complex, AMPScript the simplest:
You can use AMPScript in emails, landing pages or SMS keyword configurations. I’ll use AMPScript in this example.
Here’s how you add or update a single row in a data extension named My_Test_DataExtension using the UpsertDE() function:
Here’s a breakdown of the UpsertDE() arguments in this example:
- The name of the data extension to receive the data
- Number of columns you’re using to check to see if there’s a matching row already in the data extension. (This means there will be only 1 pair of name and value arguments following this parameter. You could specify more.)
- The lookup column
- The lookup value
- Column 1 to update
- Column 1 update value
- Column 2 to update
- Column 2 update value
For further reading:
UpsertData() (for SMS keywords)
UpdateData() (for SMS keywords)
One cool thing you can do in the Salesforce Marketing Cloud is offer your subscribers a unique coupon code as part of a promotional email campaign. Here’s how to do it.
To start, create a “CouponCodes”Data Extension with the following columns:
Next, generate your own list of unique coupon codes in Excel. Include a “CouponCode” column header. Save the worksheet as CSV or Unicode (tab-delimited).
Then, import your coupons into the data extension with the adhoc import button:
Finally, add this AMPScript to your email. This code will try to find a coupon row for the specified email address in the CouponCodes data extension. If it finds one, it’ll return the coupon code. If not, it will “claim” an unclaimed code and associate it with the specified email address. The bit about the message context — that will prevent you from claiming coupon rows when you’re doing a send preview when building the email.
Keep these things in mind:
- Make sure you upload enough coupons for your target audience so you don’t run out of unclaimed coupons. For recurring coupon campaigns, you should build a system to monitoring unused coupon codes.
- Make sure the target of the coupon code (e-commerce site, POS system, etc) is using the same set of coupon codes as your campaign.
- You can also do this in an SMS campaign.
- The data extension name in the
claimrow() function cannot be a variable
- Any data extension referenced in a
claimrow() function must exist
For further reading:
Data Extension AMPScript Functions
MobileConnect Coupon Scenario
Update 5/28/2013: Added additional gotchas about claimrow() function
Update 2/9/2015: Added empty() check after claimrow() function
Update 3/9/2016: Move code snippet to gist, added variable declaration for emailaddr
Update 7/24/2017: Removed unnecessary lookup. Thanks, Brian (see comments below).
When you’re creating a dynamic email in Salesforce Marketing Cloud using AMPScript, things can get muddled up with non-HTML code real fast — so muddled it’s hard to recognize the basic layout of the email. Sometimes it’s helpful to hide the AMPScript in a way that doesn’t affect the functionality. Here’s a trick that I use on a regular basis.
Hide your init block in with a styled DIV
I normally use these at the top of an email for initialization of variables, etc. Simply edit the content area to view the full code.
DO NOT use HTML comments to hide AMPScript. It will screw up the automatic text version of your email!
Even though your email will pass validation in Salesforce Marketing Cloud, if you don’t check for positive lookupRows() results with rowcount() before using the row() function, then you may end up with a run-time error that aborts your send.
These kinds of errors are a pain to track down in the SFMC platform. Save yourself some debugging/support call time.
Don’t do this: