Platform allowances

The modules you have contracted determine which platform allowances apply to your license. For example, you're only metered on mobile push notifications if you've purchased the App module. Your sales order lists the exact allowances you're measured against, together with the amount of usage included.

How your allowance is calculated

Your allowances are based on your contracted billable profiles—the number in your agreement, not your live count.

For example, if your contract is for 1 million billable profiles:

The multipliers in this example are illustrative only. Your actual allowances depend on your contracted tier. See your sales order for the exact amounts.

Event storage

Applies to: Customers with the Loomi AI Platform package.

Event storage measures the total number of events currently stored in your Bloomreach project. It's a snapshot of your stored footprint at a point in time—not a count of events ingested this month.

📘

Note

Your total event storage allowance is specified in your contract.

Calculation rules

• Snapshot, not flow: Event storage reflects how many events are stored right now, not how many arrived this month—historical events accumulate over time.
• Measured daily: Changes can take 24–48 hours to appear in the dashboard.
• Monthly trend: The usage dashboard shows the average snapshot value per month.
• Compliance: At the end of the month, your daily average storage volume determines whether you're compliant. Read Efficient profile-based Engagement usage for details.

⚠️

Important

If your event storage number looks high, it's likely because stored events accumulate across your entire history, not just the current period. Events aren't automatically deleted after a month.

What counts

All events stored in the platform count toward event storage. Events of type=notification_state generated by multiple mobile apps are excluded—see Multiple mobile apps per project for details.

What should you consider?

• Events accumulate over time. Event storage reflects your total stored footprint. A project running for 2 years has 2 years of stored events.
• Your snapshot was taken at a high-traffic moment. A spike in event volume during the snapshot window will be reflected in the current value.
• You recently ran a large import. Imported events count toward your stored footprint.

Profile updates

Applies to: Customers with the Loomi AI Platform package.

Profile updates measure the number of update operations Bloomreach processes against your profiles each month. It's request-based, not attribute-based. What matters is how many operations are processed, not how many attributes change in each one.

⚠️

Important

Multiple mobile app events (type=notification_state) are excluded from profile updates. See Multiple mobile app per project for details.

Calculation rules

• One operation on one profile = 1 update, regardless of how many attributes are included.
• Batch operations count per profile: one API call updating 5 profiles = 5 updates.
• Repeated operations count every time: updating the same attribute 5 times in separate calls = 5 updates.
• No-op updates count: setting an attribute to its current value still counts as 1 update. This is because Bloomreach still processes the update operation even if the value does not change.
• Anonymous profiles included: operations on anonymous profiles count the same as identified ones.
• Compliance: At the end of the month, your total volume of profile updates determines whether you're compliant. Read Efficient profile-based Engagement usage for details.

What counts

For example, updating 5 attributes in one API call counts as 1 profile update.

What doesn't count

These event types are excluded only when they are internally generated by Bloomreach. If the same event types are imported or tracked externally, they may count toward your allowance.

• campaign
• merge
• ab test
• experiment
• anonymization
• voucher
• banner
• consent
• managed_endpoint
• clarity
• recommendation
• notification_state

If any of these event types are imported or tracked via Omniconnect, they aren't considered internally generated and count against your profile update allowance.

What should you consider?

• Your integration updates profiles on every visitor interaction. High-traffic days accumulate updates quickly if each tracked event triggers a profile update.
• Repeated syncs of the same data count every time. A daily CRM sync that pushes the same attributes counts each run, even if values haven't changed.
• Batch imports count per profile row. A 500,000-row import = 500,000 updates.
• Set-property actions in scenarios or campaigns count per profile affected.

Email orchestrations

Applies to: Customers who have purchased the Email package or Enterprise Engagement package.

Email orchestrations measure the number of emails Bloomreach attempts to deliver. The metric counts at the point of send attempt—after the message has been personalized and assembled, and a delivery attempt is made. Emails that fail before reaching the send stage—for example, due to missing or invalid consent—aren't counted.

Calculation rules

• Counted at send attempt: An email counts when a delivery attempt is made. Messages that don't reach the send stage—for example, those blocked due to missing consent (recorded as enqueue_failed)—aren't counted.
• Retries count: If a failed send is re-enqueued (by taking a specific action in scenario) and a new delivery attempt is made, the retry counts as an additional orchestration.
• Webhooks excluded: Emails routed via webhooks aren't counted here—they count as API orchestrations.
• Annual allowance: Usage accumulates across the full contract year, not per month.
• Compliance: At the end of the month, your total email orchestrations used year-to-date determine whether you're compliant. Read Efficient profile-based Engagement usage for details.
• Top-up: If you're running out of your annual allowance before your contract anniversary, contact your Account Manager.

📘

Note

The usage dashboard shows both month-to-date and year-to-date usage. The allowance is annual. A high-volume month draws from your annual budget rather than triggering an overage.

What counts

• Campaign emails
• Scenario-triggered emails
• Transactional emails via channel API

What should you consider?

• Retries count. If your sending pipeline retries for failed deliveries, each retry adds to your orchestrations count.
• Transactional volume adds up quickly. Order confirmations, password resets, and triggered emails count the same as marketing emails.
• Consent failures don't count. Emails blocked before the send stage due to missing or invalid consent are excluded.
• Message allowances aren't included in your orchestrations allowance and must be purchased separately.

Mobile message orchestrations

Applies to: Customers who have purchased the Mobile Messaging package or Enterprise Engagement package.

Mobile message orchestrations measure the number of SMS, MMS, WhatsApp, and RCS messages Bloomreach orchestrates for sending. The allowance is annual and shared across all four channels.

Calculation rules

• 1 message to 1 recipient = 1 orchestration.
• Counted when the message is sent, regardless of delivery status.
• Webhooks excluded: Messages routed via webhooks aren't counted here—they count as API orchestrations.
• Annual allowance: Usage accumulates across the full contract year. All channels (SMS, MMS, WhatsApp, RCS) share the same allowance.
• Compliance: At the end of the month, your total messaging orchestrations year-to-date determine whether you're compliant. Read Efficient profile-based Engagement usage for details.
• Top-up: If you're running out of your annual allowance before your contract anniversary, contact your Account Manager.

📘

Note

The usage dashboard shows both month-to-date and year-to-date usage. The allowance is annual. A high-volume month draws from your annual budget rather than triggering an overage.

What counts

• Campaign SMS, MMS, WhatsApp, and RCS messages
• Scenario-triggered SMS, MMS, WhatsApp, and RCS messages
• Transactional mobile messages via channel API

What should you consider?

• SMS character limits can multiply your count. A single SMS campaign may be split into multiple message parts based on character limits. Each part counts as a separate orchestration.
• All 4 channels share one annual allowance. A high-volume month on one channel (for example, SMS for a flash sale) draws from the same budget as your WhatsApp and RCS usage.
• Transactional volume adds up quickly. Order confirmations, delivery updates, and OTPs sent via SMS or WhatsApp count the same as campaign messages.
• Message allowances aren't included in your orchestrations allowance and must be purchased separately.

📘

Note

The usage dashboard shows a breakdown by channel (SMS/MMS/WhatsApp/RCS). All channels draw from the same shared annual allowance.

Mobile push notifications

Applies to: Customers who have purchased the Mobile App package or Enterprise Engagement package.

Mobile push notifications measure the number of push notifications Bloomreach sends to mobile devices. It's counted when the notification is produced by the sending pipeline, not at delivery confirmation.

Calculation rules

• 1 notification to 1 customer = 1 count, even if that customer has multiple devices or platforms (for example, both Android and iOS). A notification sent to a customer with both Android and iOS devices counts as 1, not 2.
• Counted at production time, not at delivery confirmation.
• Webhooks excluded: Mobile push routed via webhooks isn't counted here—it counts as API orchestrations.
• Annual allowance: Usage accumulates across the full contract year, not per month.
• Compliance: At the end of the month, your total mobile push notifications used year-to-date determines whether you're compliant. Read Efficient profile-based Engagement usage for details.
• Top-up: If you're running out of your annual allowance before your contract anniversary, contact your Account Manager.

What counts

• Campaign push notifications
• Scenario-triggered push notifications

What should you consider?

• A sale, campaign, or product launch can drive a high volume of push notifications in a short period. These draw from your annual budget.
• Message allowances aren't included in your orchestrations allowance and must be purchased separately.

📘

Note

The usage dashboard shows both month-to-date and year-to-date usage. The allowance is annual. A high-volume month draws from your annual budget rather than triggering an overage.

API orchestrations (webhooks and managed endpoints)

Applies to: Customers who have purchased the Extensions add-on or Enterprise Engagement package.

API orchestrations measure the number of outbound API calls Bloomreach makes to external systems—webhooks triggered by campaigns or scenarios, and managed endpoint calls served by Bloomreach on your behalf.

Calculation rules

• Webhooks: Counted when the outbound request is sent.
• Managed endpoints: Counted when the request is served.
• Annual allowance: Usage accumulates across the full contract year. Both webhooks and managed endpoints share the same allowance.
• Compliance: At the end of the month, your total API orchestrations used year-to-date determine whether you're compliant. Read Efficient profile-based Engagement usage for details.
• Top-up: If you're running out of your annual allowance before your contract anniversary, contact your Account Manager.

📘

Note

Emails and mobile messages sent via webhooks are excluded from email orchestrations but count here as API orchestrations.

What counts

• Webhook calls executed by campaigns or scenarios.
• Webhook calls triggered by transactional or channel API.
• Managed endpoint calls served by Bloomreach.

What should you consider?

• Webhook calls count per customer, not per API call. A single batch webhook call that serves 100 customers counts as 100 API orchestrations—one per customer affected.
• Emails sent via webhooks count here, not as email orchestrations. If you route emails through a webhook to an external ESP, each routed message counts as an API orchestration.
• Managed endpoint calls count when the request is served, not when it's triggered.

📘

Note

The usage dashboard shows both month-to-date and year-to-date usage. The allowance is annual. A high-volume month draws from your annual budget rather than triggering an overage.

Loomi BigQuery

Applies to: Customers who have purchased the Loomi BigQuery add-on.

Loomi BigQuery measures the volume of data your BigQuery queries process each month. It's based on bytes processed—the amount of data scanned to run your queries—not the size of the results returned.

Calculation rules

• Bytes processed, not bytes returned: A query that scans 500 MB to return 10 rows counts as 500 MB.
• Each execution counts separately: Running the same query twice processes the data twice.
• Dry runs excluded: Validation-only jobs that don't process data don't count.
• Monthly allowance: Resets at the start of each calendar month.

📘

Note

The usage dashboard displays usage in GB for readability. Your contract specifies the allowance for your subscription.

What counts

• BigQuery query jobs that process data
• Repeated executions of the same query

What should you consider?

• Unoptimized queries scan more data. Queries without filters or partitioning may scan your entire dataset even if you only need a small result. Always use a time filter to limit the size of a query.
• Repeated executions add up. Scheduled queries or dashboards that run frequently each consume their full bytes-processed quota.
• If you're approaching your monthly limit, review your query integrations for optimization opportunities. Read Efficient profile-based Engagement usage for details.