I am currently implementing Marketing Cloud in Agile methodology for one of my clients and I am facing a big challenge regarding the release management in Marketing Cloud.
My client has many deployment environments:
- 3 levels of testing environment
- 1 Staging environment
- 1 Production environment
Marketing Cloud will be integrated with Service Cloud and many systems like Apache Kafka and Tibco.
As for Service Cloud, we have many dev orgs and 1 full sandbox.
To simplify the deployement of Salesforce (Service and Marketing) my client wants to use only the staging environment for sprint development and then push to production at the end of each sprint.
We all know that Marketing Cloud doesn't provide a testing environment unless if I dedicate a Business unit for testing (with a manual commit to production business unit).
The Service Cloud Sandbox will be connected to the staging environment and used during the sprint for developing new user stories.
I wanted to know how you management in general the release management in Marketing Cloud especially with many deployment environment (at least staging and production). How you managed the switch between a Salesforce Sandbox and Prod ? One of the ideas would be to use a Test population in the production environment but I prefer not do this..