> 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/getresponse.md).
# GetResponse
Update GetResponse subscribers with their unique share link and referrer information.
## Sync with your GetResponse List
**Step 1:** In *Program Editor > 4. Options > Integrations*, click the *Connect to GetResponse* button.
{% hint style="info" %}
Connect GetResponse before importing participants. If participants are already in your program, follow [these ESP sync options](https://support.growsurf.com/article/385-how-can-i-sync-my-growsurf-participants-to-my-esp) to send their GrowSurf data to GetResponse.
{% endhint %}
**Step 2:** Log in to GetResponse and authorize GrowSurf
**Step 3:** Once connected, choose the GetResponse list that you want to automatically sync to. GrowSurf will add/update your GetResponse Contacts every time a new participant is added or referred to your referral or affiliate program.
## Examples
[View our GetResponse tutorials](https://docs.growsurf.com/additional-integrations/getresponse/tutorials) to see different kinds of examples that you can copy/paste into your email templates.
## **Contact Fields**
GrowSurf will automatically create these new contact fields for your GetResponse Contacts.
| **Field Code** | **Type** | **Text** | **Description** | **Example** |
| ------------------------------------ | -------------------------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------- |
| **GRSF Share URL** | `[[grsf_share_url]]` | TEXT | The participant's unique referral link | |
| **GRSF Participant ID** | `[[grsf_participant_id]]` | TEXT | The participant's unique GrowSurf ID | abc123 |
| **GRSF Referral Status** | `[[grsf_participant_id]]` | TEXT | The referral status of the participant\* | CREDIT\_PENDING |
| **GRSF Participant First Name** | `[[grsf_participant_first_name]]` | TEXT | The participant's first name | Bob |
| **GRSF Participant Last Name** | `[[grsf_participant_last_name]]` | TEXT | The participant's last name | Loblaw |
| **GRSF Referrer First Name** | `[[grsf_referrer_first_name]]` | TEXT | The first name of the participant's referrer (if applicable) | Gavin |
| **GRSF Referrer Last Name** | `[[grsf_referrer_last_name]]` | TEXT | The last name of the participant's referrer (if applicable) | Belson |
| **GRSF Referrer Email** | `[[grsf_referrer_email]]` | TEXT | The email address of the participant's referrer (if applicable) | |
| **GRSF Total Referral Count** | `[[grsf_total_referral_count]]` | NUMBER | The participant's all-time referral count | 0 |
| **GRSF Lead Count** | `[[grsf_lead_count]]` | NUMBER | The participant's current lead count (pending referrals that have not converted yet) | 0 |
| **GRSF Monthly Referral Count** | `[[grsf_monthly_referral_count]]` | NUMBER | The participant's current month referral count | 19 |
| **GRSF Prev Monthly Referral Count** | `[[grsf_prev_monthly_referral_count]]` | NUMBER | The participant's previous month referral count | 200 |
| **GRSF Next Milestone** | `[[grsf_next_milestone]]` | TEXT | The text for the next/upcoming milestone reward (only applies to milestone rewards. [See example here](https://docs.growsurf.com/developer-tools/embeddable-elements#embedded-next-milestone)) | You are only 2 referrals away from winning a free t-shirt! |
| **GRSF Next Monthly Milestone** | `[[grsf_next_monthly_milestone]]` | TEXT | The text for the next/upcoming monthly milestone reward (only applies to milestone rewards. [See example here](https://docs.growsurf.com/developer-tools/embeddable-elements#embedded-next-milestone)) | You are only 2 referrals away from winning a free t-shirt! |
| **GRSF Total Invite Count** | `[[grsf_total_invite_count]]` | NUMBER | The participant's all-time invite count | 112 |
| **GRSF Total Impression Count** | `[[grsf_total_impression_count]]` | NUMBER | The participant's all-time impression count | 150 |
| **GRSF Language** | `[[grsf_language]]` | TEXT | The participant's program language (ISO code such as es or pt-BR) | es |
\**GrowSurf Referral Status* can have one of these values:
* `CREDIT_PENDING`: The participant must trigger a referral before their referrer receives credit.
* `CREDIT_AWARDED`: The participant triggered a referral, and their referrer received credit.
* `CREDIT_EXPIRED`: The participant did not trigger a referral before the referral credit expired.
You can use these contact fields in your GetResponse email templates. For example, use `[[grsf_share_url]]` to add each participant's unique referral link.
[Learn more about GetResponse merge fields here.](https://www.getresponse.com/help/personalization.html)
## **Troubleshooting Tips**
* Check the participant's activity logs if they do not sync. GrowSurf retries failed syncs for up to 7 days.
* **If the new participant is being added to GetResponse, but not all of their custom Contact fields are showing up:**
* GetResponse does not allow custom Contact fields to be saved as empty values. A missing GrowSurf field means GrowSurf has not sent a value for it yet.
---
# 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/getresponse.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.