Data 360176 tasks
Design Data 360 Solution Architecture
Get a Data 360 solution design for a specific use case: a readiness check, the platform limits that apply, the options, and a phased plan for building it. Much of this work is advisory, and it often ends with a plan or recommendation rather than anything built in an org.
Method
How MeshMesh does it
- Reads the specification or discovery material for the use case, such as a set of spec files for a retail CX project or notes from a discovery call.
- Queries the org to check whether Data 360 is enabled and ready.
- Lists the platform limits that shape the design. Examples are calculated insight SQL limits, segments that cannot query calculated insight outputs, and data model object category restrictions.
- Builds and tests pipeline pieces where the design calls for them: ingestion, data model, segment and activation.
- Lays out display or integration options with their blockers, such as Related List Enrichment against a custom LWC using ConnectApi queries.
- Delivers a readiness report and phased plan. When the use case is a poor fit, it says so plainly, for example in a draft follow-up email.
Identity Resolution, Zero Copy, Einstein Studio and the Ingestion API come up most often in this work. For the rest of the cloud, see the Data 360 overview.
Products
Products and features it works with
Bars show how many of this capability's tasks touched each product.
- 1B2C Commerce3 tasks
- 2Data ActionsData 3603 tasks