> For the complete documentation index, see [llms.txt](https://docs.storylane.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.storylane.io/hubs-docs/integrations-hub/integrations/dynamics-365.md). # Dynamics 365 Storylane integrates with Dynamics 365 to create new leads and send demo analytics Storylane directly integrates with Dynamics 365. With the integration, you can: * Create new leads * Update demo analytics for leads {% hint style="warning" %} ### **Capturing Leads** There are few ways in which you can identify new leads. You can refer the article on [Lead Tracking](/analytics-and-performance/lead-attribution.md#lead-attribution-tracking) to learn more {% endhint %} ### How to Integrate * To get started, reach out to Storylane support team to setup Dynamic 365 Integration ### Storylane Custom Properties Once the integration between [Dynamic 365](https://learn.microsoft.com/en-us/dynamics365/sales/) and Storylane is successful, below custom fields are created for each lead record: `Demo Name` - last viewed demo * type: String * name: **sl\_last\_demo\_name** `Demo Viewed At` - when the demo was viewed last * type: DateTime * name: **sl\_last\_demo\_at** `Demo Time (secs)` - time spent in seconds * type: Integer * name: sl\_last\_demo\_time\_secs `Demo Complete (%)` - percent of steps completed * type: Percent * name: sl\_last\_demo\_completion\_percent `Demo Link` - link to the demo * type: Url * name: sl\_last\_demo\_link `Demo CTA Clicked` - CTA url clicked by user * type: Url * name: sl\_last\_demo\_cta `Demo Checklist Completed` - checklist of features completed * type: boolean * name: sl\_last\_demo\_checklist\_completed `Demo Sessions` - total count of demo sessions by the lead * type: Integer * name: sl\_demo\_session --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.storylane.io/hubs-docs/integrations-hub/integrations/dynamics-365.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.