How delta processing works
After reading, you know when Changes only saves work and when an action still handles everyone.
A scheduled action normally handles every current member of the audience on every run. With the Processing scope set to Changes only, it handles only the people who joined since its last successful run. For a large audience that changes little between runs, that is far less work.
What it needs
Section titled “What it needs”CAB has to know who joined. That requires Track membership changes between runs, which your administrator turns on. See CAB Settings. Without it, the actions show a hint instead of the choice.
Delta processing is set per scheduled action. Actions you run by hand always handle all results.
When an action handles everyone
Section titled “When an action handles everyone”An action falls back to the full audience whenever CAB can’t be sure who joined since its last successful run:
- on its first run,
- after a run whose action failed or only partly succeeded,
- after a run that didn’t activate the action,
- when the comparison with the previous run isn’t available.
Handling everyone is always safe: people who are already in a campaign aren’t added twice. After a failed run, the next one covers everyone who joined since the last success, so nobody is missed.
Campaigns
Section titled “Campaigns”A campaign add set to Changes only adds the people who joined. People who were in the audience before aren’t handled again, so their member status and fields stay as they are. Someone removed from the campaign by hand isn’t added again just because they’re still in the audience.
With Campaign Cleansing and Limit cleansing to this Audience, cleansing checks only the people who left the audience, not every campaign member. CAB turns on the limit by itself when you combine Changes only with cleansing. You can turn it off again; cleansing then checks the whole campaign while additions stay limited to the changes.
Data extensions
Section titled “Data extensions”Between full refreshes, a data extension add sends only the people who joined. Existing rows aren’t updated, rows deleted in Marketing Cloud aren’t added again, and people who left stay in the data extension. Delta runs between full refreshes sets how often a full refresh happens. Without it, the window warns: Members who leave the audience are never removed from the data extension. See How integrations work.
Final actions
Section titled “Final actions”A final action set to Changes only gets only the people who joined. The same Flow or Apex class runs with the same input values. People who left are never handed to a final action, under either scope. See How final actions work.
What it isn’t
Section titled “What it isn’t”Delta processing saves work; it doesn’t decide who may be contacted. To keep someone out for good, use your organization’s suppression, such as an exclusion in the audience.
- Processing scope. Whether a scheduled action handles the full audience or only the changes.
- Full refresh. A run of a data extension add set to Changes only that sends everyone again.

