The Iteratively web app allows all stakeholders to collaborate on a single source of truth for analytics definitions. It keeps everyone in sync on what data to track, when, and why, and maintains a consistent schema across engineering, product management, data science, and other consumers of analytics data.
The Overview page outlines recent activity in your company and lets you manage your Sources and Destinations.
In Iteratively, Sources represent the main parts of your product, e.g. your iOS app, Android app, web app, and backend. Create a new Source for every standalone part that will send events to your analytics backends.
Every Source has a name, runtime, and a set of destinations associated with it.
A Source's runtime defines the platform-language combination used by that part of your application (e.g. Node.js — TypeScript). Iteratively uses this information to generate the correct tracking library for engineers implementing your tracking plan.
A Source's set of destinations defines the analytics providers that will receive events from this particular Source.
In Iteratively, Destinations represent the analytics providers events will be sent to from your Sources.
Every Destination has a vendor, access token, and a set of sources associated with it.
A Destination's vendor identifies a particular analytics provider you're working with. Iteratively uses this information when generating a tracking library for your engineering team to make sure it sends events to all the right places.
A Destination's set of sources defines the parts of your applications that will send events to this particular Destination.