Stop enterprise agents from burning their customer's Salesforce event quota with CDC quota optimization | Ampersand Changelog

Stop enterprise agents from burning their customer's Salesforce event quota with CDC quota optimization

When an enterprise agent wants to know when a specific field changes, they must listen to Salesforce change events and filter the non-relevant changes.

The problem is Salesforce has no native way to filter updates for specific fields, and every change event will be sent. Salesforce allocation is shared for all integrations across an organization, and these events can easily exhaust a customer’s entire quota for the day.

Ampersand now supports Change Data Capture (CDC) Quota Optimization which moves the filter inside the customer’s Salesforce, so changes to unwatched fields never become events that eat up quota.

Before · filter after delivery
The customer's Salesforce
Field changes
Events sent, allocation spent
Every change becomes a billed event. Filtering happens after delivery, which is too late to matter.
After · filter at the source
The customer's Salesforce
Field changes
Ampersand filter, running as an Apex trigger
Events sent
Only a watched change becomes an event. The rest never leave the org, so they are never counted.

How it works

For each object opted in, Ampersand adds a filter inside the customer’s Salesforce.

  1. A checkbox field is created on the object
  2. An Apex trigger sets that field whenever one of the watched fields changes
  3. Change Data Capture is configured to emit events only when the field is true

Changes to other fields never produce an event, so allocation is not spent.

Opt in

CDC quota optimization is opt-in, per object. The customer’s org keeps its allocation for the changes that matter, and every other integration in that org benefits from freed up shared allocation.

When the allocation empties, data stops flowing across every Salesforce integration in the org. Cutting an agent’s Salesforce consumption gives that capacity back to the whole org.

This applies to update events and reduces change event delivery, not REST API calls. Fetching each record still counts against the customer’s API limit.

A new take on native product integrations