Projects, events and feedback: how Iterato organises your data

Iterato organises everything in three levels: a project contains events, and each event collects feedback. Knowing the IDs at each level makes setup and reporting much easier.

Project

The top-level container. Each business or department can create one or more projects, and every project has a unique project_id. You use it to initialise the SDK and to filter feedback through the API.

Event

A specific moment where you want feedback, such as onboarding, a completed purchase or a new feature toggle. Each event has a unique event_id, for example checkout-success-239sdj or feature-toggle-darkmode.

Feedback

A single response tied to one event. It includes the reaction, user info, browser logs, an AI summary of the conversation, IP details and more.

Project
├── Event 1
│   ├── Feedback 1
│   └── Feedback 2
└── Event 2
    └── Feedback 3

Tip

Create one event per decision you want to make. "Why do people abandon checkout?" deserves its own event, separate from general site feedback.