Lua Scripting Resources

Important Update to Custom Scripting

SurveyGizmo's CustomScript Action now supports the LUA programming language.


Legacy Custom Scripting Language Deprecation Plans 

  1. New accounts (created after October 29, 2018) will only have the option to use Lua in scripts.
  2. As of October 29, 2018 Custom Scripting Actions will default to Lua as the scripting type in the Custom Scripting Action for accounts created before this date. You will be able to switch to the Legacy Custom Scripting; though we highly encourage using Lua.
  3. In the long term, Legacy Custom Scripting Actions will be switched to read-only. Read-only scripts will continue to function; you will just be prevented from editing. The exact date on this is to be determined; we will send notifications well ahead of time.


 Go to our Legacy Scripting Documentation.

While SurveyGizmo is one of the most flexible survey tools around, we get requests for customizations that are not available out of the box. This is where JavaScript and Custom Scripting can save the day. If you have scripting chops you can use the JavaScript action or the Custom Scripting action to achieve the survey of your dreams.


[article("bodfy")]

This function returns the URL of the webpage that linked to the survey for the given respondent.

Example

In the below example survey we output the Referrer to the page which is this tutorial!

print(referrer())

Note: The referrer is not always available. Below are some common scenarios where the referrer will be blank.

It will/may be empty when the survey respondent:

  1. Entered the survey by clicking on a TXT Message
  2. Entered the survey from an email (like an email invitation)
  3. Keyed the survey URL in browser address bar itself.
  4. Entered the survey by a browser-maintained bookmark.
  5. Entered the survey as the first page in the window/tab.
  6. Switched from an https URL to an http URL.
  7. Switched from an https URL to a different https URL.
  8. Has security software installed (antivirus/firewall/etc) which strips the referrer from all requests.
  9. Is behind a proxy which strips the referrer from all requests.
  10. Visited the site programmatically (like, curl) without setting the referrer header.