5 Best Practices To Make The Most of Salesforce Marketing Cloud<\/strong><\/h2>\n\n\n\n1. Account Set-Up<\/strong><\/h3>\n\n\n\n- Keep in mind that every contact in marketing cloud in Salesforce will be counted as a contact whether you send it to them or not.<\/li>
- Use accelerators<\/a> to understand how the system will work for you.<\/li>
- Enable enhanced FTP to ensure the highest level of security and facilitate the automation of data import processes.<\/li>
- Have two admin accounts so that you can have one account as a failsafe option in case of any inadvertent circumstances.<\/li>
- Utilize Roles and Permissions to make sure only authorized users have access to Marketing Cloud features.<\/li>
- If SAP is purchased and activated, warm up the IP correctly before sending bulk emails.<\/li>
- Use notification services to get instant alerts and resolve the issues.<\/li>
- Get accustomed to reading validation errors for quick amendment of errors.<\/li><\/ul>\n\n\n
![\"Email](\"https:\/\/email.uplers.com\/blog\/wp-content\/uploads\/2022\/03\/1-manaing-email-campaigns.png\")
<\/a><\/div><\/div>\n\n\n\n2. Email And Content Builder<\/strong><\/h3>\n\n\n\n- Have a folder structure and naming convention<\/a> in place to organize content builder assets. Salesforce naming conventions will come in handy during this process.<\/li>
- Import the content that you need rather than importing everything together.<\/li>
- Host the images in the content builder for best performance.<\/li>
- If AMPScript is used for personalization, the attribute ought to have a default value. You\u2019d observe this being practiced across some of the best <\/strong>Salesforce marketing cloud examples out there.<\/li>
- It is not recommended to use SSJS scripts within emails since their performance is slow. Instead, use AMPScript\/GTL to achieve the desired functionality.<\/li><\/ul>\n\n\n\n
Our email experts can help you with ESP integration and migration across 50+ ESPs. Learn more>><\/a><\/p>\n\n\n\n3. Data<\/strong><\/h3>\n\n\n\n- One of the most widely adopted <\/strong>Salesforce data model practices involve creating data extensions by using primary keys to enable performances and apply indexes to the data.<\/li>
- Always work in TLS and secure your code as you are dealing with confidential information.<\/li>
- Unless the audience size is too small (<10,000), utilize data extensions to store contact data. The reasons being, they are scalable and query activity can be used to perform advanced segmentation. API calls can be used for advanced integration and the performance is better compared to lists.<\/li>
- If there are multiple campaigns running with different segments, it\u2019ll be useful to have a naming convention and folder structure setup. This is one of the leading Salesforce campaigns<\/a> best practices.<\/li>
- If the data is being manually imported and cleaned, then it is best to use Automation Studio to automate this process using import activity and SQL queries.<\/li>
- If Journey Builder is used for any type of engagement flows, a correct data model has to be in place in Contact builder to map out all the relationships between various data extensions.<\/li><\/ul>\n\n\n\n
4. Journey Builder<\/strong><\/h3>\n\n\n\n- Understand that Journey Builder is not suitable to implement a high-volume prospecting email campaign<\/a> with speedy delivery.<\/li>
- Typically, you can build a longer-term sales cycle through this tool.<\/li>
- It is not recommended to combine multiple business goals into a single journey. Instead, split the journeys to make the flow manageable.<\/li>
- It is a good practice to have an exit criterion in place so that a contact can exit the journey when specific conditions are met<\/a>. Ensure that you abide by all Salesforce contact management <\/strong>best practices while setting up Journey Builder.<\/li>
- Utilize the goal feature of the journey but note that there can only be a single goal per journey.<\/li><\/ul>\n\n\n\n
5. Analytics<\/strong><\/h3>\n\n\n\n
- Keep in mind that every contact in marketing cloud in Salesforce will be counted as a contact whether you send it to them or not.<\/li>
- Use accelerators<\/a> to understand how the system will work for you.<\/li>
- Enable enhanced FTP to ensure the highest level of security and facilitate the automation of data import processes.<\/li>
- Have two admin accounts so that you can have one account as a failsafe option in case of any inadvertent circumstances.<\/li>
- Utilize Roles and Permissions to make sure only authorized users have access to Marketing Cloud features.<\/li>
- If SAP is purchased and activated, warm up the IP correctly before sending bulk emails.<\/li>
- Use notification services to get instant alerts and resolve the issues.<\/li>
- Get accustomed to reading validation errors for quick amendment of errors.<\/li><\/ul>\n\n\n
<\/a><\/div><\/div>\n\n\n\n2. Email And Content Builder<\/strong><\/h3>\n\n\n\n
- Have a folder structure and naming convention<\/a> in place to organize content builder assets. Salesforce naming conventions will come in handy during this process.<\/li>
- Import the content that you need rather than importing everything together.<\/li>
- Host the images in the content builder for best performance.<\/li>
- If AMPScript is used for personalization, the attribute ought to have a default value. You\u2019d observe this being practiced across some of the best <\/strong>Salesforce marketing cloud examples out there.<\/li>
- It is not recommended to use SSJS scripts within emails since their performance is slow. Instead, use AMPScript\/GTL to achieve the desired functionality.<\/li><\/ul>\n\n\n\n
Our email experts can help you with ESP integration and migration across 50+ ESPs. Learn more>><\/a><\/p>\n\n\n\n
3. Data<\/strong><\/h3>\n\n\n\n
- One of the most widely adopted <\/strong>Salesforce data model practices involve creating data extensions by using primary keys to enable performances and apply indexes to the data.<\/li>
- Always work in TLS and secure your code as you are dealing with confidential information.<\/li>
- Unless the audience size is too small (<10,000), utilize data extensions to store contact data. The reasons being, they are scalable and query activity can be used to perform advanced segmentation. API calls can be used for advanced integration and the performance is better compared to lists.<\/li>
- If there are multiple campaigns running with different segments, it\u2019ll be useful to have a naming convention and folder structure setup. This is one of the leading Salesforce campaigns<\/a> best practices.<\/li>
- If the data is being manually imported and cleaned, then it is best to use Automation Studio to automate this process using import activity and SQL queries.<\/li>
- If Journey Builder is used for any type of engagement flows, a correct data model has to be in place in Contact builder to map out all the relationships between various data extensions.<\/li><\/ul>\n\n\n\n
4. Journey Builder<\/strong><\/h3>\n\n\n\n
- Understand that Journey Builder is not suitable to implement a high-volume prospecting email campaign<\/a> with speedy delivery.<\/li>
- Typically, you can build a longer-term sales cycle through this tool.<\/li>
- It is not recommended to combine multiple business goals into a single journey. Instead, split the journeys to make the flow manageable.<\/li>
- It is a good practice to have an exit criterion in place so that a contact can exit the journey when specific conditions are met<\/a>. Ensure that you abide by all Salesforce contact management <\/strong>best practices while setting up Journey Builder.<\/li>
- Utilize the goal feature of the journey but note that there can only be a single goal per journey.<\/li><\/ul>\n\n\n\n
5. Analytics<\/strong><\/h3>\n\n\n\n