A practical guide for deploying Salesforce Data 360 changes from a sandbox to another sandbox or production using a DevOps Data Kit and Change Sets.
Salesforce Data 360 changes can be developed in a sandbox and promoted to:
Salesforce Marketing Intelligence is the central business intelligence (BI) and analytics layer within the new, agentic Marketing Cloud Next ecosystem.
Built natively on the core Salesforce platform, it consolidates the capabilities previously known as Datorama and integrates them deeply with Data 360 (Data Cloud), Agentforce, Einstein AI, and Tableau Next. Its primary purpose is to automatically ingest, harmonize, and analyze massive amounts of cross-channel marketing data so marketers can prove ROI and optimize campaign spend in real time.
Salesforce Marketing Cloud Next uses different domain configurations for different capabilities. The three main domain types are:
| Domain type | Primary purpose | Typical example |
|---|---|---|
| Custom Domain | Landing pages, forms, and images | pages.example.com |
| Branded Domain | Email link tracking and SMS URL shortening | link.example.com, sms.example.com |
This document outlines the internal, automated connection architecture of Salesforce Data Cloud (formerly Data 360) regarding how it nattively links to its primary Home Org, the system users involved, and the required administrator security configurations.
When Data Cloud is provisioned and enabled inside a Salesforce org, the underlying platform-to-platform connection is automatically configured. No administrative credentials or manual OAuth configurations are required to link Data Cloud to its own Home Org.
A runbook for connecting a Salesforce CRM org (Sales Cloud / Service Cloud) to Salesforce Data 360 using the Salesforce CRM connector, then bringing CRM data in through data bundles and data streams.
Naming note: Salesforce renamed Data Cloud to Data 360 on October 14, 2025. Salesforce says you may still see "Data Cloud" in the product UI and docs during the transition, and the functionality is unchanged. This guide uses "Data 360" and keeps UI labels exactly as they appear (for example, Data Cloud Setup). Source: https://help.salesforce.com/s/articleView?id=data.c360_a_data_cloud.htm&language=en_US
How this was written: Steps are summarized in my own words from the Salesforce Help, Trailhead and developer pages listed under each section and in References. Salesforce updates these pages often, so confirm labels against the linked pages before you run this in production. Resea
A runbook for connecting Marketing Cloud Engagement to a Salesforce CRM (Sales Cloud / Service Cloud) org using Marketing Cloud Connect.
Based on Salesforce's Trailhead module Marketing Cloud Connect Setup and a Salesforce Help knowledge article. Steps are summarized in my own words; check the linked sources for the latest screens and labels. UI labels can change between releases (for example, the user checkboxes appear as AgentExchange in current Trailhead and AppExchange in older guides).
| SELECT su.emailaddress, | |
| su.subscriberkey AS ContactKey, | |
| j.journeyname,j.versionnumber,ja.activityname AS EmailName, | |
| s.eventdate AS SendTime, s.jobid, s.listid, | |
| b.eventdate AS BounceTime, b.BounceType,b.SMTPBounceReason, b.SMTPMessage, b.SMTPCode | |
| FROM [_sent] AS s | |
| INNER JOIN [_journeyactivity] AS ja | |
| ON s.triggerersenddefinitionobjectid = ja.journeyactivityobjectid | |
| INNER JOIN [_journey] AS j | |
| ON ja.versionid = j.versionid |
| <script runat="server"> | |
| Platform.Load("core","1.1.1"); | |
| var subkey = "SubscriberKey" | |
| var email = "email@email.com" | |
| var api = new Script.Util.WSProxy(); | |
| var sub = [ | |
| { | |
| SubscriberKey: subkey, | |
| EmailAddress: email, |
| <script runat="server"> | |
| Platform.Load("core","1.1"); | |
| var prox = new Script.Util.WSProxy(); | |
| var de = DataExtension.Init("my_data_extension"); | |
| var data = de.Rows.Retrieve(); | |
| for (var i = 0; i < data.length; i++) { | |
| var row = data[i]; | |
| try { | |
| var subscriber = { |
| <script runat="server"> | |
| Platform.Load("core", "1"); | |
| try { | |
| var de = DataExtension.Init("DataExtensionExkey"); | |
| var payload = { |
