> For the complete documentation index, see [llms.txt](https://docs.growsurf.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.growsurf.com/integrations/tally.md).

# Tally

Add referral tracking to your Tally form to automatically recognize new leads that come through referrals.

{% hint style="info" %}
**Please note the following requirements to make Tally work with GrowSurf**:

* Your form must be embedded on your own webpage (you cannot use the stand-alone `https://tally.so/r/xxxx` webpage).
* Your form must ask for an email address.
  {% endhint %}

## Prep Your Form <a href="#prep-your-form" id="prep-your-form"></a>

If you have an embedded Tally form on your website that you want to add referral tracking to, follow these instructions:‌

**Step 1:** Open the GrowSurf campaign editor and navigate to the *Installation* tab.‌

**Step 2:** Continue through the installation steps until you reach the referral tracking method section.​‌

**Step 3:** Click the Tally icon and follow your campaign-specific instructions.‌

**Step 4:** Once your Tally form has been prepped, continue on with the rest of the GrowSurf installation process.‌

## How It Works <a href="#how-it-works" id="how-it-works"></a>

Tally tells the page it sits on when someone finishes a form, and hands over every answer with it. The GrowSurf code block listens for that, reads the respondent's email address and name, and adds them to your campaign as a referred friend. Nothing changes inside Tally itself — you keep the embed you already have.

The code block only accepts that message from Tally, so another script on your page cannot fake a submission. If you serve your form from your own domain instead of tally.so, change `TALLY_ORIGIN` in the code block to match that domain.

GrowSurf looks for the email address first, then the name. It reads these questions, in order, and uses the first one it finds:

* Email address: a question of the email type, otherwise a question whose wording contains "email", otherwise any answer that is itself an email address
* First name: a question worded "first name", otherwise the first word of a whole-name question ("Name", "Full name", "Your name", "First and last name")
* Last name: a question worded "last name", otherwise the second word of that whole-name question

A question worded "company", "business", "username", "middle name", "screen name" or "file" is never treated as the respondent's name, and an answer that is not text — a checkbox group, a file upload — is skipped. If GrowSurf finds no email address, nothing is sent and no participant is added.

## Additional Tips <a href="#additional-tips" id="additional-tips"></a>

* While following your campaign-specific Tally instructions in the GrowSurf campaign editor, you may skip any steps that you have already completed from previous setup in Tally.
* If you run into issues or have any questions, please reach out to [GrowSurf support](https://support.growsurf.com/) for assistance.


---

# 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.growsurf.com/integrations/tally.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.