GetFeedback

Resuming Incomplete Surveys

By default, when a respondent closes a survey without submitting it the response is recorded as incomplete. If the respondent opens the survey link again a new survey session will begin. To let respondents resume their incomplete survey season, use our gf_id merge field in your survey link. Learn more about merge fields

If you’re sending your survey using Send to List, Salesforce automation, or Quick Launch, we include gf_unique and gf_id by default, so you don’t need to add these as additional merge fields.

To allow respondents to resume incomplete surveys:

  1. From your survey, select and copy your survey URL by navigating to Distribute > Survey Link.
  2. Copy and paste your link so you can edit it.
  3. Add a question mark ? to the end of the link, then add the gf_id merge field in lowercase.
  4. Add an equals sign = to the end, then enter a value that identifies the respondent taking the survey (for example, their name or email address).

The value assigned to the gf_id merge field won’t display in your responses. To track information, like a respondent’s name or email, you may need to use additional merge fields.

This key will look like: gf_id=mergefieldvalue (replace mergefieldvalue with your parameter, such as the respondent’s name).

gf_id tells GetFeedback that the user can resume their survey session, and the parameter is unique to that respondent so we know exactly which survey session to resume.

To test gf_id with your survey:

  1. Add ?gf_id=yourname (replace 'yourname' with your own name) to the end of your survey link. Your link with gf_id appended may look something like this:
    • www.getfeedback.com/r/xxxxxxxx?gf_id=Jill
  2. Start the survey and answer 1 or more questions, but don’t finish the survey.
  3. Close out the survey in your browser before you submit your answers.
  4. Open the survey a second time. You should be brought to the section of the survey where you left off.
  5. Once you complete the survey, you can open the survey link to start a new response.

You can combine gf_id with any number of merge fields to track additional information about each respondent.

Choose the value for your unique parameter, like name, email, or a contact ID if you're using Salesforce. You can also use values like Case ID, or Event ID.

You'll most likely be using a dynamic merge field that pulls data from your Salesforce, Pardot, or Marketing Cloud.

For example, if your unique parameter is an email address, your survey link may look like this example. This example uses Salesforce merge field syntax, but the formatting can vary depending on where you’re sending the survey from.

  • www.getfeedback.com/r/xxxxxxxx?gf_id={!Contact.Email}

Example: To let respondents resume a survey and also track their sure that their email address to know who submitted the response add the gf_id and email merge field. The example link below shows what your survey link might look like:

  • www.getfeedback.com/r/xxxxxxxx?gf_id={!Contact.Email}&Email={!Contact.Email}

Combine gf_id with our other special parameter, gf_unique to prevent duplicate responses. Using gf_id and gf_unique together allows respondents to resume surveys, but only complete the survey once. Learn more about preventing duplicate responses

If you use both gf_id and gf_unique, your link would look like this example: www.getfeedback.com/r/xxxxxxxx?gf_id={!Contact.Email}&gf_unique={!Contact.Email}

If you use a parameter specific to a person instead of a case or event, that person can’t take this survey again. If you plan on sending the same survey on a recurring schedule, like for a quarterly NPS program, it’s best to use a merge field with a date range included. This allows respondents to answer this survey next quarter when the date range is updated for Q2 of that year.

This example shows how you can add a date range to your link:
www.getfeedback.com/r/xxxxxxxx?gf_id={!Contact.Email}-H1-2019&gf_unique={!Contact.Email}-Q1-2023