Usage and Billing

To inspect various metrics that reflect your organization's use of Iterable, metrics which may impact your bill, and to review your saved payment information, visit the Usage and Billing screen.

# In this article

# Usage and Billing screen

The Usage and Billing screen displays various metrics related to your Iterable organization's messaging, contacts, Catalog, and data usage:

To view the Usage and Billing screen, navigate to Settings > Billing.

To change the date range for the metrics displayed here, use the date selector. All metrics are calculated in the PST time zone.

To view these metrics broken down on a per-project basis, click View project breakdown for any category.

# Messaging usage metrics

The Messaging section of the Usage and Billing screen displays the following metrics:

• Emails sent - Count of emails sent during the selected date range, across all the Iterable projects in your organization.

• SMS and MMS sent - Count of outbound SMS and MMS campaign messages sent during the selected date range, across all the Iterable projects in your organization. Includes bounces; does not include send skips or segment count.

• SMS and MMS received - Count of outbound SMS and MMS campaign messages received during the selected date range, across all the Iterable projects in your organization. Does not include segment count.

• Push Sent - Count of push notifications sent during the selected date range, across all the Iterable projects in your organization.

• Successful SMS Verifications - Count of successful SMS verifications. This number does not include verification attempts where the code is incorrect.

# Detailed SMS metrics

Below the overall Messaging metrics, you'll see these detailed SMS and MMS usage metrics:

• SMS sent - Count of outbound SMS campaign messages sent during the
  selected date range, across all the Iterable projects in your organization. Includes bounces; does not include send skips or segment count.

• SMS segments sent - Count of outbound SMS segments sent during the selected date range, across all the Iterable projects in your organization.

• SMS received - Count of inbound SMS campaign messages received (such as replies) during the selected date range, across all the Iterable projects in your organization. Does not include segment count.

• SMS segments received - Count of total inbound SMS segments received during the selected date range, across all the Iterable projects in your organization.

• MMS sent - Count of outbound MMS campaign messages sent during the selected date range, across all the Iterable projects in your organization. Includes bounces but not send skips.

• MMS received - Count of inbound MMS messages received (such as replies) during the selected date range, across all the Iterable projects in your organization.

To view a breakdown of usage by SMS service, click on each metric name to expand.

• Iterable SMS - Messages or segments that were sent or received through Iterable SMS services.

• Telnyx Direct - Messages or segments that were sent or received through your Telnyx account.

• Twilio Direct - Messages or segments that were sent or received through your Twilio account.

Here are some important considerations when reviewing these metrics:

• SMS campaign metrics vs SMS usage and billing metrics

  SMS metrics displayed on the Usage and Billing page do not always match SMS campaign metrics. This is because every SMS campaign includes metrics for what was sent, bounced, skipped, and delivered, and doesn't reveal or consider either the number of segments sent or whether the message was SMS or MMS. Billing for SMS services is based on actual data usage, not campaign performance.

• SMS sent vs SMS segments sent

  One SMS campaign can correlate to multiple SMS segments. Segmentation occurs when the SMS message exceeds a predetermined character limit. Therefore, the number of SMS campaign messages sent may not be equal to the number of SMS segments sent.

  For a complete explanation of SMS segments, character encoding, and size limits, see SMS Overview.

• SMS processing delays

  After Iterable sends a message request to the SMS provider, there can be a delay before receiving the final delivery status of the message back from the provider. The time of the final status determines when an SMS is billed. This may cause SMS messages sent on one day to be charged on the next day. You'll most likely notice this impact for SMS messages sent on the last day of a billing period.

# Examples

These examples illustrate why SMS campaign can differ from SMS usage and billing metrics:

Single SMS segment

For an SMS campaign with a single segment, the number of SMS sent equals the number of segments sent. You'd see metrics such as:

• 363,657 total SMS sent (campaign metric)
• 363,657 SMS sent (usage and billing metric)
• 363,657 SMS segments sent (usage and billing metric)

Multiple SMS segments

For an SMS campaign with 3 segments,metrics could look like this:

• 363,657 total SMS sent (campaign metric)
• 363,657 SMS sent (usage and billing metric)
• 1,090,971 SMS segments sent (usage and billing metric)

Variable SMS segments

If an SMS campaign sends messages that vary in length from one user to the next (because of dynamic data), here's what that can look like:

• 363,657 total SMS sent (campaign metric)
• 363,657 SMS sent (usage and billing metric)
• 581,851 SMS segments sent (usage and billing metric)

MMS Campaign

For an SMS campaign that sends MMS messages, total SMS equals MMS sent, like this:

• 363,657 total SMS sent (campaign metric)
• 363,657 MMS sent (usage and billing metric)

Delayed SMS

If your SMS campaign was partially delayed, some messages were sent the next day, that may impact billing. Here is a snapshot of that scenario:

• 363,657 total SMS sent on January 31st (campaign metric)
• 290,925 SMS sent on January 31st (usage and billing metric)
• 290,925 SMS segments sent on January 31st (usage and billing metric)
• 72,732 SMS sent on February 1st (usage and billing metric)
• 72,732 SMS segments February 1st (usage and billing metric)

# User metrics

In Users, you'll find the following metrics:

• Current - The total number of users saved by your Iterable organization, across all its projects, as of today's date. This metric is not impacted by the date selector.

• Users added - The total number of users added, across all of your Iterable organization's projects, during the selected date range. Deleted users do not decrease this number, it won't reflect whether your total user count increased or decreased.

• High water mark - The highest number of users saved by your Iterable organization, across all its projects, during the selected period. Includes the date when this peak value was reached.

• Active users (Lifetime value) - The total number of users that have been sent an email within in the last 90 days, across all Iterable projects.

• Active users added - The total number of users added within the selected period that have been sent an email within the last 90 days.

# Custom event usage metrics

The Custom events section of the Usage and Billing screen displays the following metrics:

• Current - The total number of custom events saved for your Iterable organization, across all its projects, as of today's date. This metric is not impacted by the date selector.

• Custom events stored - The total number of custom events stored as of the last date of the selected period.

• High water mark - The highest number of custom events stored for your Iterable organization, across all its projects, during the selected period. Includes the date when this peak value was reached.

  TIP

  You can reduce your total custom events stored by setting data retention policies, which define how long Iterable stores your custom events before deleting them. To learn more, read Managing Custom Event Retention.

# Catalog usage metrics

The Catalog section displays these metrics:

• Catalog references - The sum of Lookup references, Collection references, and Product recommendations for the selected date range.

• Lookup references - The total number of catalog lookups made by Iterable to support #catalog Handlebars references, during the selected date range, across all your organization's Iterable projects.

• Collection references - The total number of catalog lookups made by Iterable to support #catalogCollection Handlebars references, during the selected date range, across all your organization's Iterable projects.

• Product recommendations - The total number of product recommendation references resolved by Iterable during the selected date range, across all your organization's Iterable projects.

# Payment information

To enter a credit card or manage an existing payment method, use the widget in the Payment information section at the bottom of the Usage and Billing screen:

# Questions?

If you have billing-related questions, please contact billing@iterable.com.