> 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

### Step 1: Create a source in Rudderstack

Choose add a source.<br>

<figure><img src="/files/92DlT1AT6QquqTGiRXBh" alt=""><figcaption></figcaption></figure>

Select "Javascript" and name your source.

<figure><img src="/files/5Kq2sYU2nHs2dsup9kXx" alt=""><figcaption></figcaption></figure>

After clicking "Continue", skip "Install SDK" part and click on Connect in side menu.<br>

<figure><img src="/files/hWZzAASPt8HC8HYN61Ag" alt=""><figcaption></figcaption></figure>

Copy "Data Plane URL" and "Write key" from  dashboard.<br>

<figure><img src="/files/se3129kS1VB7VN4wzXVV" alt=""><figcaption></figcaption></figure>

### Step 2: Connect to source

Paste write key and data plane url into the "Rudderstack" section of the Formsort integration.

<figure><img src="/files/16f3jAchFZQSwpY40Hio" alt=""><figcaption></figcaption></figure>

By default, [Analytic Events](/integrations/getting-data-out/analytics.md) are not enabled and must be toggled on.

<figure><img src="/files/qhZk9MXXfGANbXNVcnoZ" alt=""><figcaption></figcaption></figure>

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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.formsort.com/integrations/integration-reference/rudderstack.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.