# Plan remaining implementation Userflux's features are powered by your users behavioural data. Different use cases will require different pieces of customer data. Because of this we recommend creating a tracking plan to understand what data will need to be collected, and where from. *** ### Tracking plan template To help manage this, we've created a template you can copy and fill in {% embed url="" %} When filling in this template, consider where the data will be collected from and the type of data needed to make it happen. You can use the following list of questions below to help get an idea. * What insights do you want to know and what events are required to know it? * What marketing automation do you need to run and what events will trigger those lifecycles? * What user information do you want to use to segment your user base by? * What behavioural events and profile information are needed to power accurate product recommendations? * What analytics do you want to embed in your own product? * What events & profile information do you want to send to other tools? --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://userflux.gitbook.io/userflux-docs/plan-remaining-implementation.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.