Sometimes using a Query Activity to de-duplicate data before an email send isn’t feasible. You can do it in AMPScript if you don’t mind sorting your external rows.
In this code block, you just need to use a variable to keep track of the previous value that you’ve displayed. When the current row doesn’t match the previous one, output it.
Sending tons of emails to certain email domains can be tricky, even if your sending IP address reputation is good. In Salesforce Marketing Cloud, you can utilize an Audience Exclusion Script to isolate domains for special sending treatment — like throttling or sending at a certain time of day.
Here’s an example that utilizes the AMPScript domain() function and the emailaddr personalization string that’s present in every send context.
Email #1 – Exclude emails to comcast.net domains with an exclusion script:
domain(emailaddr) == "comcast.net"
Email #2 – Exclude emails except comcast.net domains with an exclusion script:
domain(emailaddr) != "comcast.net"
Email #2 would be configured with some throttling or be deployed only at a certain time of day.
Code goes here:
This solution will work for sends to Lists, Groups or Data Extensions.
If Exclusion Scripts are not enabled for your User-Initiated or Triggered Send Definitions, SFMC support can enable them for you.
Suppose you want to output a day of the month with a proper suffix (e.g. 1st, 13th). There aren’t any formatting functions in AMPScript to do it, but you can do it with a set of if-statements:
Once you’re satisfied that it works, you can simply remove the for-loop and un-comment the set @day = Format(Now(),"dd")) line
Say you need to find the lowest of three numbers in an email — numbers you’ve retrieved from a Data Extension. Here’s one way to do it in AMPScript with a set of inline-if statements:
I built a landing page that posts to itself and runs this pruneRows() function. I configured a Data Extension that contains the keys to delete. The script retrieves all of the rows with that key, deletes them and updates the DE of keys with the results.
You may have to experiment with the number of Row Keys to retrieve at a time. If the number is too high, the landing page will time-out. In my scenario, I found that processing 50 at a time worked well (line #8).
For further reading: