How Iterato attaches console logs and session data for developers

"The app is slow" isn't a bug report. Iterato bundles each piece of feedback with the technical context developers need, so support and engineering stop going back and forth.

What comes with each feedback

• The event that triggered the prompt and its route

• Browser and device details

• Console errors and logs captured around the moment of feedback

• Session data and the user context you set with setUser()

Example

A user says "the checkout button does nothing after I enter my address". Alongside it, the team sees:

{
  "event": "checkout_submit",
  "route": "/checkout",
  "browser": "Chrome 123",
  "error": "TypeError: Cannot read properties of undefined",
  "trace": "CheckoutForm.tsx:184"
}

The product manager gets the "why"; the developer gets the "how".