Now that you’ve completed the Itly setup, you’re ready to pull down your tracking plan. Your tracking plan is defined in the Iteratively web application and pulled into your project’s code base in the form of type-safe auto-generated code. All code is stored in a single, human-readable file and imported/included as needed.

itly pull {source-name}

The pull command takes one argument: the name of the source that defines your project. For example, a source name might be ios, android, web, or backend. Sources are associated with a tracking plan and define a scope for the analytics events. The events tagged to a particular source will appear in the auto-generated code. Those that haven’t been tagged will not. This ensures that your event is tracked consistently on all the sources it’s applicable to.

The pull command will also tell you what, if anything, has changed since the last time you pulled your team's analytics spec. The changes are your automatically created TODO for getting your analytics tracking plan up-to-date.

As your project progresses, you and your team will inevitably make changes to your tracking plan. Iteratively will notify you when those changes are made and when you’re ready, you can pull down the changes and incorporate them into your project.