Efficient event-based Engagement usage

This guide covers how to keep your implementation efficient on event-based pricing by minimizing unnecessary event processing and storage.

Bloomreach supports multiple pricing models. If you're not sure which one applies to your contract, see Which pricing model am I on?

• On event-based pricing, monthly processed events (MPE) and maximum stored events (MES) are your commercial meters. This guide covers how to stay within those limits.

• On profile-based pricing (introduced May 2026), billing is based on billable profiles and MUV rather than event volume. This guide doesn't apply—see Pricing and usage instead.

Key concepts

MPE

MPE is the total number of events processed into or within the platform in a calendar month—including events triggered when customers view items, start sessions, open emails, and interact with campaigns and channels. This includes both system events—predefined and available by default—and custom events tailored for your business.

📘

Note

If you send or import the same event multiple times, each occurrence counts toward MPE—even if deduplication later removes the duplicate.

Duplicated events

If you send or import the same event multiple times, each occurrence is treated as a new event and counts toward MPE. However, if there is a 1:1 duplication, deduplication takes place.

Duplication can occur when the same event is sent with different attributes multiple times. To avoid this, ensure only unique data is tracked or imported.

You can use event deduplication to clean up and prevent the same event from being stored twice. However, the event will still be considered processed and counted toward your MPE, even with deduplication.

MES

MES is the maximum number of events stored in your account at any point in time. It includes all active events that haven't expired or been deleted, and excludes events that have been moved to external storage, such as Engagement BigQuery (EBQ).

Different event attributes don't count as separate events, but events with the same name and different statuses do.

What generates events

Not all platform actions generate events. The following table shows which sources count toward your event volume.

Check your tracking health

Before optimizing, check whether your event volumes reflect real user behavior. Go to Overview > Bloomreach usage to review event volume, MPE, channel dashboards, and data breakdowns by event and campaign.

Quick health checks

Unhealthy patterns and likely causes

For example, if view_item and view_category consistently exceed page_visit, that's a sign of misconfigured tracking—page visits should be driving item and category views, not the reverse. Similarly, session_start and session_end counts should track closely together; a large gap suggests session_end isn't firing correctly.

Reduce MPE

• Track only events you actively use for journeys, segmentation, or analytics.

• Avoid multiple events for the same action — for example, redundant heartbeat or scroll events.

• Use properties on a single event type instead of creating many similar types.

• Use DELTA imports to bring in only new or updated data. Sending or importing the same event multiple times counts toward MPE even if deduplication later removes the duplicate.

Keep ad events in check

Ad events should constitute at most 10–20% of your total MPE. If you send ad audiences daily to segments of customers rather than to all of them, check the conditions in your scenarios to ensure you don't send the same data repeatedly.
Before sending an ad audience to the relevant segments, check whether the customer received one the previous day and whether their qualifying condition has changed in the last 24 hours. See the Ads Best Practices Guide for more detail.

Reduce MES

For more details on your stored events, create a report in Analyses > Reports counting each event to understand your current storage footprint before optimizing.

• Use EBQ: Move older events to EBQ. This frees up in-platform storage while keeping historical data available for analysis. By expiring events in the platform, you retain the data in EBQ without it counting toward your MES.
• Set expirations: Set data expirations to automatically delete unnecessary events. Without expirations, MES grows continuously. Apply shorter retention to high-volume, low-value events like page_visit, and longer retention to high-value events like purchase and consent.
• Ensure consistent tracking: Inconsistent tracking can cause unexpected storage growth. Use the retention reference table to check whether your event volumes are in line with expected patterns.
• Delete obsolete data: Use the Data manager to delete events and properties you no longer need. This reduces MES but doesn't affect historical MPE.
• Storage benchmarks:
  • page_visit: Keep below ~5% of MES. It's high volume and often low value, so it's a good candidate for short expiry.
  • campaign and banner events: Keep each below ~30% of MES. Expire old split tests, irrelevant statuses, and low-value banner actions like shows and closes.

🚧

Data deletion

Deleting data reduces MES only—it has no effect on your MPE count.

Event tracking and retention reference

Banner retention

Campaign retention