Skip to main content

Configure your Exit URL with an external survey service

  • Updated

 

Applies to: Admins configuring post-call customer surveys for VideoEngager video calls

This guide works with any survey or web-form provider that can read values from URL parameters (query string). Google Forms and SurveyMonkey are shown as examples.

Goal

After a call ends, redirect the visitor to a survey or a feedback form and pass useful context in the URL—like {{interactionId}}, {{tenantId}}, {{lang}}, {{callIds}}.

Quick setup 

  1. Create your survey (any web form/survey provider that supports URL parameters).
  2. Decide what to pass (recommended: IDs, not personal data).
  3. Build the Exit URL by appending query parameters, for example: 
    https://example.com/survey?interactionId={{interactionId}}&tenantId={{tenantId}}&lang={{lang}}&callIds={{callIds}}
  4. Paste the full URL into your VideoEngager “Exit URL” setting.
  5. Test: complete a short call → confirm redirect → confirm survey captured the context.

How it works

Your Exit URL is a normal web link. When the call ends, the visitor is redirected to it. If your Exit URL contains placeholders like {{interactionId}}, VideoEngager replaces them with real values at runtime.

Recommended pattern: pass context as query-string parameters:

https://survey.vendor.com/form?interactionId={{interactionId}}&tenantId={{tenantId}}&lang={{lang}}&callIds={{callIds}}

🔒 Privacy tip (important)

URLs can be logged by browsers, proxies, analytics tools, and screenshots. Prefer IDs over personal data. If you must link to a person, pass a reference ID and resolve it on your backend.

Requirements

  • Your provider must support pre-filling fields via URL parameters (or you can use a redirect page that maps parameters).

  • Keep URLs short; avoid sensitive data.

  • Generic pattern
https://your-survey-url
?interactionId={{interactionId}}
&tenantId={{tenantId}}
&lang={{lang}}
&callIds={{callIds}}
  • If your provider uses a different prefill format, use a redirect page to map these keys into the provider-specific parameters.

Example 1: Google Forms (pre-fill fields via URL)

Google Forms supports pre-filling answers by using a “pre-filled link” that contains URL parameters in the format entry.<fieldId>=value. The easiest way to get the correct entry. IDs is to use Google Forms’ Get pre-filled link option. 

Step-by-step

  1. Open your Google Form in edit mode.
  2. Menu (⋮) → Get pre-filled link. 
  3. Fill “dummy” values into the fields you want to capture (e.g., INTERACTION_ID, TENANT_ID).
  4. Click Get Link and copy the generated URL.
  5. In that URL, replace dummy values with your VideoEngager variables.

Copy/paste example

Replace the entry.111111 numbers with your form’s actual ones from the pre-filled link.

https://docs.google.com/forms/d/e/<FORM_ID>/viewform
?entry.111111={{interactionId}}
&entry.222222={{tenantId}}
&entry.333333={{lang}}
&entry.444444={{callIds}}

What you’ll see in Google Forms responses: those fields arrive already filled-in for the user (they can usually edit them unless you design around it).

Example 2: SurveyMonkey (Custom Variables)

SurveyMonkey supports passing “custom variables” through a Web Link collector. SurveyMonkey even provides a URL template like:

https://www.surveymonkey.com/r/your_survey?var1=[var1_value]&var2=[var2_value] 

Step-by-step

  1. In SurveyMonkey, open your survey → Design Survey.
  2. Logic → Custom Variables → add variables (example: interactionId, tenantId, lang, callIds). 
  3. Go to Collect Responses → create a Web Link collector. 
  4. Copy the web link (SurveyMonkey appends a template for your variables).
  5. Replace the bracketed values with your VideoEngager placeholders.

Copy/paste example

https://www.surveymonkey.com/r/<COLLECTOR_OR_SURVEY_CODE>
?interactionId={{interactionId}}
&tenantId={{tenantId}}
&lang={{lang}}
&callIds={{callIds}}

Where the data shows up: in SurveyMonkey results/exports, you can filter and analyze by those custom variables.

Notes & limits (SurveyMonkey)

  • Custom Variables are case sensitive. 
  • Keep URLs under ~2,000 characters to avoid browser issues. 
  • Some characters/names are restricted (SurveyMonkey lists forbidden characters and reserved names). 

Testing checklist

  • Run a short call → end it normally.
  • Confirm the redirect happens immediately.
  • Copy the final landing URL from the browser address bar and confirm values are present (e.g., interactionId=...).
  • Submit the survey → verify the response includes the context (Google field values / SurveyMonkey custom variables).

Troubleshooting

Problem Likely cause Fix
Survey opens but fields are empty (Google Forms) Wrong entry.<id> parameters Generate a new “Get pre-filled link” and copy the correct entry. IDs. 
SurveyMonkey link works but variables don’t appear in results Custom Variables not created, or name mismatch Create variables in Design Survey → Logic → Custom Variables and ensure query keys match exactly. 
Some values look “cut off” or broken URL encoding issue (spaces/special characters) Prefer IDs; avoid special characters; keep values URL-safe.

Best practices

  • Prefer stable IDs: {{interactionId}}, {{tenantId}} are safer than names/emails.
  • Keep it short: fewer parameters, fewer surprises (and fewer URL-length issues). 
  • Use consistent keys across systems: interactionId, tenantId, lang, callIds.
  • Test with “weird” values: agent names with spaces, non-English characters, etc.

🔗 Related

If you use a different survey tool, search their help center for: prefill form via URL, query string parameters, or hidden fields.

Related articles

Comments

0 comments

Please sign in to leave a comment.