You are here:
Types of Data Usage in Marketing Cloud Engagement
The types of data that you use and receive bills for depends on the Marketing Cloud Engagement features you use. Data usage can appear to differ depending on the report, data view, or extract you're looking at. For example, standard reports don't always include data usage that can increase your bill, such as test sends.
This table describes the data usage types in Marketing Cloud Engagement.
| Label | Description |
|---|---|
| CloudPages Impression | A successful request for a published page (200 OK). Examples of CloudPages impressions include landing pages, Microsites, MobilePush pages, and Interactive Email pages. Currently, Code Resources aren’t considered or counted as CloudPages impressions. |
| Contact | A subscriber added to any contact database in your Marketing Cloud Engagement instance. A contact is also any other subscriber to whom you sent a message via any channel using the Marketing Cloud Engagement. For more information, see Contact Definition and Count Determination in Contact Builder. |
| Einstein Content Selection Impression | An Einstein Content Selection block or an Einstein Content Test block included in an email send. Two more impressions are consumed for each email that a user opens, regardless of how many Einstein Content blocks are in the email. |
| Einstein Email Recommendations Impression | Any opened email that contains one or more Einstein Recommendations based products or content. There’s no limit to the number of recommendations in the email. Only the number of opened emails is counted for billing purposes. |
| Einstein Web Recommendation Impression | An API call for content or product recommendations. A single page can generate multiple impressions depending on how it’s built and the APIs that it calls. For example, a page with content recommendations and product recommendations is two API calls and is therefore billed as two impressions. |
| Email Attachment | Any file attached to an email and sent to a subscriber, billed as one attachment per attached file. For example, if you attach two files to an email and send to 100 subscribers, the total usage is 200 email attachments. |
| Email Usage | An email message sent to a subscriber. Examples of email usage include normal email sends, normal email sends CC, normal email sends BCC, triggered send, triggered send CC, and triggered send BCC. For example, if you send an email to 100 subscribers and BCC 2 more emails, the total usage is 300 Emails: 100 normal email sends and 200 normal email sends BCC. |
| GroupConnect Transactional Message | A LINE Message, Facebook Message, or a Reseller Message that is sent to a subscriber. From a billing perspective, LINE and Facebook messages are considered the same in terms of utilization, whereas GroupConnect Reseller Messages have a different utilization multiplier. |
| High Priority Triggered Send (HPTS) | A message that has the priority field on the Triggered Email Message Interaction set to High. An HPTS is billed in addition to a Triggered Email. See Email Usage definitions. For example, if you set a triggered send with high priority and send 100 triggered emails, the total usage is 100 HPTS and 100 emails. |
| Interactive Email | An email message that has an Interactive Email Form block included in the email. For example, if you include an Interactive Email Form block in an email and send to 100 subscribers, the total usage is 100 Interactive Email impressions and 100 Emails. Interactive Email Form blocks can also be included in CC and BCC messages and counted as extra usage. |
| Landing Page Impression | A successful request for a published Landing Page (200 OK). This impression is only used with the legacy Landing Page feature in Email Studio. |
| Short Message Service (SMS) Message: | A mobile phone message that the Marketing Cloud Engagement SMS service sends to a subscriber, and a message sent back to Marketing Cloud Engagement (SMS MT and MO messages). Only messages sent from Marketing Cloud Engagement (SMS MT Messages) are included in the data usage. Usage is based on the subscriber’s country code. Marketing Cloud Engagement (SMS MT Messages) are counted regardless of whether the message was delivered or undelivered. For more information about SMS deliverability, see Supported and Unsupported Markets in MobileConnect. |
| Multimedia Message Service (MMS) Message | An SMS Message that’s sent to a subscriber using the Outbound Media template. Only messages sent from Marketing Cloud Engagement (MMS MT messages) are included in the data usage. This service is available only in the United States. |
| MobilePush Message | A successful MobilePush message sent to a device. |
Examples of MobilePush messages and usage:
- Each Alert generates 1 MobilePush Message per device.
- Each Alert + CloudPages page generates 1 MobilePush Message per device. An additional CloudPages Impression can also be consumed.
- Each Inbox Message generates 1 MobilePush Message per downloaded device. Each badge app icon added to an Inbox Message generates 1 additional MobilePush Message per device. An additional CloudPages Impression can also be consumed.
- Each Alert + Inbox Message generates 2 MobilePush Messages per device. Each badge app icon added to an Inbox Message generates 1 additional MobilePush Message per device. An additional CloudPages Impression can also be consumed.
- Each In-App Message generates 1 MobilePush Message per Contact, regardless of whether the message was downloaded or viewed on any of the contact's devices. Each opted-in device generates 1 additional MobilePush Message. Opted-in devices use background push notifications for optimal in-app message deliverability.
Additional information about the methods that we use to bill a specific usage type are available in your Marketing Cloud Engagement contract.
Did this article solve your issue?
Let us know so we can improve!
