Deleting Contacts can be a stresful and responsible process. It requires knowledge, prudence, and very often a supervision and approvals of authorities. Here is a shortcut to automated task of deleting unwanted, spare Contacts created from triggered sends.

After making changes to a triggered send email you need to republish its interaction. POSTman is a perfect environment for testing triggered send emails, so here is a simple trick to republish interactions directly from POSTman.

Some domains, email addresses or even name prefixes may negatively affect deliverability and sender’s reputation. SFMC has a tool – List Detective (LD) – to block inactive domains or known spammers emails. This feature is not enabled by default and to request it log a case with the SF support.

A sample prototype that displays subscriber’s data within a CloudPage. It uses CloudPages for hosting, a light-weight HTML/CSS framework, a data extension as a database, and AMPscript to display personalized content.

This is a second part or another case for using AMPScript to dynamically set a background color to table rows. In this example, I use a process loop to dynamically build a table and then apply a background color to even and odd rows.

For a “zebra-striped” effect on table rows (a table to present content not a table to control an email layout), you would use the CSS :nth-child() selector. But a quick check with a reference tool Can I Email diminish doubts that any ‘fancy’ selector is still scarcely supported by email clients.

In order to keep the system stable and prevent from unexpected or continuous high loads, the SFMC platform limits API requests. As a rule of thumb there is a tolerated limit of 2000 SOAP and 2500 REST calls per minute. Follow best practices, do the math, and you should be fine. Rate limiting does not end at the number of calls though.

To delete millions of records from a data extension you need to go beyond the Clear records function on the SFMC graphical user interface. You want to delete them from a backend…

This is an attempt to create a longer post with a collection of short and sweet recipies for data validation and reports. The post is intended to grow over time and contain frequently used SQL snippets or scenarios.

This is about a basic, manual data import from a CVS file to a data extension. Manual file import is prone to human error which may further result in a poor data quality or mismanagement of a customer consent. That could violate GDPR/CAN-SPAM principles.

This is a case study for building a dynamic email using AMPScript. Working with multilingual marketing teams in EMEA makes content localization (translation and authoring) a significant factor in planning digital campaigns (time and money). In this example I streamline a localization process by using data import and AMPScript functions. Not only do I eliminate time spent on building/fixing/testing language versions but also separate content from formatting in the final email.

Unless you strictly manage data retention policy on each and every data extension, your collection of obsolete items grows over time. Users without rights to delete items from the user interface, can move such spare items to a Trash folder which then can be emptied by someone with delete permissions.