Marketing Cloud Next - Consent Management: Billing and Utilization

Note: This article is a companion article for the Consent Management: Frequently Asked Questions resource. Check that article out for additional details and other frequently asked questions.

Does the Communication Subscription Consent object in Salesforce CRM consume data storage?

Yes. CommunicationSubscriptionConsent is a standard Salesforce CRM object, and its records count against the org's Core CRM data storage allocation. The practical impact is modest for most orgs: records aren't pre-populated (a row isn't written until an explicit consent action occurs), so storage growth tracks active consent updates, not the number of Contacts or Leads. The Core CRM object is separate from the Data Cloud Communication Subscription Consent DMO; DMO storage sits in Data Cloud.

Does ingesting consent data into Data Cloud consume credits?

No, when it arrives through an internal Salesforce connector. Consent data flowing in via the Salesforce CRM connector is part of the internal data pipeline: "As of August 7, 2025, usage of this type is included with Data 360 and doesn't consume credits." Ingestion from external sources (e.g., a Snowflake or S3 pipeline) is a different usage type and does consume credits. 

See: Data Services Billable Usage Types for Data 360

Once consent data is in Data Cloud, does its storage consume credits?

Storage is billed only for usage above the org's allocation ("Storage Beyond Allocation"). Consent rows within the allocation don't incur an incremental storage charge. 

See: Data Services Billable Usage Types for Data 360

Does mapping or migrating consent from CRM to Marketing Cloud Next consume credits?

Bringing CRM consent into the Data Cloud Communication Subscription Consent DMO through the CRM connector is internal-pipeline ingestion and is zero-cost. Mapping consent to the correct Contact Point Types is a configuration step, not a metered usage type. Credits are consumed by what you do with the data afterward — queries, segmentation, activation, Calculated Insights, and Identity Resolution — not by the mapping itself.

Does including consent in a segment or Calculated Insight consume credits?

Yes. Segmentation and Calculated Insights are metered Data Cloud usage types billed on records processed. Building a segment that references consent, or a Calculated Insight used to surface consent, draws down credits each time it runs. Design these with high contact volumes in mind. 

See: Data Services Billable Usage Types for Data 360

Does running Identity Resolution on consent data consume credits?

Yes. Identity Resolution is billed under the Batch Profile Unification usage type, calculated on source profiles processed (after the first run, only new or modified profiles count). Configure the ruleset but run it only when data sources are properly mapped and ready.

Can duplicate consent records increase credit consumption?

Yes. Ingesting the same individuals from more than one source without an intentional data-model design can create duplicate rows, which increase the record counts that downstream metered operations will process. This is a design consideration, not a defect.