Book Image

Automating Salesforce Marketing Cloud

By : Greg Gifford, Jason Hanshaw
Book Image

Automating Salesforce Marketing Cloud

By: Greg Gifford, Jason Hanshaw

Overview of this book

Salesforce Marketing Cloud (SFMC) allows you to use multiple channels and tools to create a 1:1 marketing experience for your customers and subscribers. Through automation and helper tasks, you can greatly increase your productivity while also reducing the level of effort required in terms of volume and frequency. Automating Salesforce Marketing Cloud starts by discussing what automation is generally and then progresses to what automation is in SFMC. After that, you’ll focus on how to perform automation inside of SFMC all the way to fully running processes and capabilities from an external service. Later chapters explore the benefits and capabilities of automation and having an automation mindset both within and outside of SFMC. Equipped with this knowledge and example code, you'll be prepared to maximize your SFMC efficiency. By the end of this Salesforce book, you’ll have the skills you need to build automation both inside and outside of SFMC, along with the knowledge for using the platform optimally.
Table of Contents (20 chapters)
Section 1: Automation Theory and Automations in SFMC
Section 2: Optimizing Automation inside of SFMC
Section 3: Optimizing the Automation of SFMC from External Sources
Section 4: Conclusion

Understanding the importance of structure

Speaking of structure, after seeing how we were able to structure our lightning component solution in a component-based architecture, it's important that we also highlight different solution structures in order to more easily understand how your project might fit together as individual pieces interlaid with the generalized functionality. We'll take a look at some common design patterns for solutions, as an alternative to the component design pattern we used previously, but first, let's define a few key terms.


The Model means data that is required to display in the view. This is a representation of the critical information used within your architecture. Unlike the other components of this architecture, the Model is not dependent on either the Controller or View and can further define rules and meaning for the data being utilized in your application.


The View represents UI components such as Extensible Markup...