Data 360 · Data Actions

Integrate Data 360 Pipelines

Get data moving into and out of Data 360 through data actions, ingestion and data graphs, and connect it to other systems and back to CRM records. Most of this work involves events, the Ingestion API, Identity Resolution, the CRM Connector and Data Graphs.

11 tasks
Method

How MeshMesh does it

  1. Builds a pipeline from a Data 360 segment to an activation, then an activation-triggered Flow that acts on CRM records.
  2. Adds Apex enrichment and a Marketing Cloud Engagement callout. It deploys the Apex classes, data extension, event definition, email and journey that the pipeline needs.
  3. For cross-org work, ingests records through the Ingestion API and maps them to a data model object. It then deploys a Platform Event-triggered Flow and an Apex parser on the receiving org.
  4. Checks prerequisites along the way, for example finding that Marketing Cloud Connect was not installed.
  5. Publishes a segment and verifies its members, then QAs the pages built on top of it.
  6. Cleans up the data actions it no longer needs.
  7. Leaves steps that can only be done in the Setup UI to a human, such as setting a platform event as a data action target.
Products

Products and features it works with

Bars show how many of this capability's tasks touched each product.

  1. 1Data ActionsData 3603 tasks
Data Actions

Related capabilities