Stood Flows · Marketing Cloud add-on · 1.3.2

The same folder, now with the business units that send the email

A Marketing Cloud business unit sits next to the Salesforce orgs it feeds. It is refreshed in the same background run, read through one retrieve-only path, and answers the question the CRM side cannot: what does the reach actually cost.

Cost and reach

The first view puts three numbers side by side: contacts the licence pays for, contacts in Contact Builder, and contacts actually reached by a send in the last 90 days. The gap between the first and the third is the same shape as unassigned CRM seats: paid capacity that moves nothing. Send volumes by campaign and month come from the send jobs, so the trend is visible before anyone asks for a report.

Data Extensions: who writes it, who reads it

Every data extension is placed on a map from its origin (a Connect sync, an import, a query, an API push) to the journeys, automations and queries that read it. Two shapes matter: an extension nobody reads, kept in sync at every cycle, and two extensions holding the same audience under different names. Both cost contact rows and both are invisible from inside Marketing Cloud's own folders.

What is known not to work yet

Anything that only the SOAP API exposes (data extension listing in some packages, lists, audiences, automatic business-unit discovery) depends on the package the customer grants, and the connection diagnostics say so by name. Super messages are read from the contract, not from Marketing Cloud. Send-level tracking needs a tracking scope; until then consumption is derived from cadence.

In the app

Captured from the application itself, built from the current source tree and opened read-only on the Meridian demonstration workspace.