We’re making subscription event tracking more accurate—and a lot less noisy—for new organizations.
Today, Iterable logs a subscribe or unsubscribe system event any time a related profile field is updated. The issue? If the user’s subscription status didn’t actually change, we still logged the event. That meant extra noise without added value.
Starting with organizations created on or after December 15, 2025, Iterable will handle these updates more intelligently:
If a subscription update doesn’t change a user’s subscription state, Iterable will still process the event (so journeys and webhooks trigger as expected), but won’t store subscription-related system events when no actual subscription changes occur.
Ultimately, this change means that:
- Subscription events are still tracked and processed by Iterable.
- All subscription events still trigger journeys and webhooks as expected, whether or not the subscription state actually changed.
- Subscription events are not stored when no actual subscription changes occur.
- You'll see fewer redundant subscription events in your exports and user profiles.
This update applies to new organizations effective today. Existing organizations will receive the same improvement in a future release, with no expected disruption to your existing journeys and webhooks that rely on subscription event triggers or data.
To learn more about how subscribe and unsubscribe events are tracked and the full impact of this change, see Subscribe and Unsubscribe Events.
