> 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" %}
**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
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 Program Editor and navigate to the *Installation* tab.
**Step 2:** Continue through the installation steps until you reach the step that asks how GrowSurf will know a referred friend signed up.
**Step 3:** Click the Tally icon and follow the instructions GrowSurf shows (see image below).
**Step 4:** Then finish the remaining installation steps.
## How It Works
Tally notifies the page when someone submits a form and includes the submitted answers in the event. The GrowSurf code block listens for that, reads the respondent's email address, first name, and last name, and adds them to your program as a referred friend. Nothing changes inside Tally, and you keep your current embed.
The code block only processes submission messages from the Tally origin. 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 respondent's email address, first name, and last name. The email address is required, while the first and last names are optional. For each field, GrowSurf uses the first match in this order:
* 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
* If you haven't embedded your form yet, open your form in Tally, click Share, and select Standard under Embed Form. Copy and paste the iframe HTML code snippet into the page where you want the form to appear.
* While following the instructions GrowSurf shows, you may skip any steps that you have already completed in a 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.growsurf.com/integrations/tally.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.
