> For the complete documentation index, see [llms.txt](https://docs.formsort.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.formsort.com/integrations/integration-reference/rudderstack.md).
# Rudderstack
This page covers setting up the Formsort -> Rudderstack integration
### Step 1: Create a source in Rudderstack
Choose add a source.
Select "Javascript" and name your source.
After clicking "Continue", skip "Install SDK" part and click on Connect in side menu.
Copy "Data Plane URL" and "Write key" from dashboard.
### Step 2: Connect to source
Paste write key and data plane url into the "Rudderstack" section of the Formsort integration.
By default, [Analytic Events](/integrations/getting-data-out/analytics.md) are not enabled and must be toggled on.
Analytic Events are ways to track information about a flow, and the answers given by the user. By toggling on "enabled events", Formsort will send the information collected from users at specific times, based on your selection. For more context, please see our reference for Analytics Events [here](/integrations/getting-data-out/analytics.md).
The [shape of the event payload](/integrations/getting-data-out/event-payload-shape.md) is configurable.
---
# 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.formsort.com/integrations/integration-reference/rudderstack.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.
