Marketing Cloud Next and Tableau Next are both built on Data 360, so in Gearset you deploy their components through a DevOps Data Kit. A Data Kit carries the components together with the order Salesforce needs to publish them in the target org. In Gearset, select Data Kit as the deployment method in Pipelines or Compare & Deploy, then pick your kit. Gearset will then automatically retrieve every component in the kit, pre-select them, keep Salesforce's publishing sequence, and activate the kit in the target after deployment.

For step-by-step instructions, see:

Although selecting a Data Kit in Gearset will automatically pre-select all Data Kit components for deployment, some teams may want to verify that all relevant components have been included in the Data Kit in the first place. Most Marketing Cloud Next and Tableau Next components don't appear in the comparison under the name you see in Salesforce, as Salesforce wraps them in a generic Data 360 record.

For example, a Tableau Next visualization will appear in the comparison as a Data kit object template, not as its own metadata type. This behaviour extends to other Tableau Next and Marketing Cloud next components (e.g. dashboards, workspaces, semantic models, identity resolutions, market segments).

While the metadata type won't align with what you see in the Salesforce UI, selecting any item in the comparison will allow you to open its XML. Every Data kit object template has a sourceObjectType tag that names the real Salesforce component type, and a sourceObject tag with its API name. For example, a Tableau Next visualization in Salesforce will show as "Actions by Usage", and in the XML will show:

Because Gearset will automatically pre-select all components in the Data Kit, to check what's included in the whole kit at once, you can select the DevOps Data Kit item instead. Its deploymentOrder tag lists every component in the kit, in publishing order, with its type:

For each component, the devName tag will reveal the API name shown in Gearset, and the type will reveal the underlying Salesforce component. For example, in the below Marketing Cloud Next Data Kit, the IdentityResolution can be found under the Individual_MKT API name, which is a Data kit object template.

Or in the below example, the Data calculated insight template can be found with the NTO_Email_Count_Calculated_Insight API name.

When you add a Data Kit to a comparison, you'll see many more items than the components you built: most of these are Data package kit objects. Salesforce creates one Data package kit object for every member of the kit, including members that don't appear as items of their own (e.g. standard data model objects).

Data package kit objects simply record the Data Kit each component belongs to:

If a Data package kit object begins with SSOT in the referenceObjectName, then these are standard data model objects and should exist in any org with Data 360 enabled. These items will typically not have a corresponding Data kit object template in the comparison and won't be in the Data Kit's publishing sequence, as they already exist in each environment.