Stashr provides comprehensive coverage for Salesforce Marketing Cloud, including:

Content Builder and Shared Content

Data Extension and Shared Data Extension configurations

Automation Studio: Specifically, automations and their related dependencies

We love this question! Here’s what’s in store: We're excited you asked!

Journey Builder Support: This feature is high on our priority list. We're actively strategizing on how to extract valuable insights from Journey Builder and determining the optimal approach for integration.

Cloud Pages Support: We have plans to include Cloud Pages in our suite of supported features. Admittedly, there are some challenges due to API limitations, but we're committed to finding solutions.

Health Checks & Monitoring: Our aim is to enhance Stashr's proactive monitoring capabilities. Imagine receiving real-time notifications when mission-critical automations you've flagged are paused or encounter errors. We're working to make this a reality.

At Stashr, we prioritize security above all. Take server-side JavaScript script activity as an instance. When interacting with the Marketing Cloud REST APIs, you require API credentials. To prevent these keys from being version-controlled, Stashr implements advanced security measures. Users can designate the keys they wish to redact. Upon commit, Stashr substitutes that value with a placeholder key. During recovery, Stashr reverses this process, seamlessly restoring the original key value, eliminating the need for manual intervention.

You can recover assets from the moment you create the instance or install Stashr. This highlights the significance of installing Stashr early, ensuring comprehensive asset protection from the get-go.

Currently, there's no time limitation on accessing commits. As long as you've created a snapshot, our aim is to keep it accessible indefinitely.