Iterable Observability Enhancements

Improved error reporting capability for Iterable destination.
Available Plans
  • free
  • starter
  • growth
  • enterprise

  •   less than a minute  

Today, we released some important observability and error reporting enhancements for the Iterable destination, applicable to both Event Stream (cloud mode) and Reverse ETL connections.

With these changes, faulty events previously misclassified with an HTTP 200 status code but failed to deliver to Iterable are now correctly marked with the relevant error codes and Iterable API responses.

You will see improved error reporting in the RudderStack dashboard for:

  • Events sent to Iterable with non-existent user IDs.
  • Validation errors due to data type mismatch for the fields passed in the events.
  • Disallowed event names.

As a result of these changes, you may observe an increase in reported errors (based on traffic, event volume, and issues with sent events), giving you improved visibility and enabling faster resolution.

Contact the RudderStack team for more information on this enhancement.

Questions? Contact us by email or on Slack