System Performance Preservation

The process of pulling content from another system into an email involves HTTP calls from Marketing Cloud Engagement to your content management system or web site.

The send speed, response time, and overall reliability of the process depend on the state of several pieces of equipment involved in the internet connection between Engagement and the content source. Consider these guidelines to preserve your system performance:

• Make no more than three content syndication requests in an email.
• Refrain from using personalization in the URL. Create variables for holding the values, reference these variables within the URL, and use script to populate the variables. For example, https://example.com?n=%%=v(@personalizedParameter)=%%
• If the syndicated content is the same for all subscribers in the campaign, save processing time by requesting the system get the content at the beginning of the send (Before;HTTPGet) instead of separately for each subscriber. If the syndicated content is the same for all subscribers in the campaign, the system caches the syndicated content it gets from the URL so it can be used again without accessing the URL.
• Save processing time by use HTTPGet to not track the URL.
• Send to smaller lists or subsets of lists if you do have performance issue. Try to keep list sizes below 1,000 subscribers. For large lists, contact your sales representative to identify a custom process that meets your needs.