Over the last few weeks, we've been iteratively improving the link survey experience with the goals of improving usability and functionality.

Recent improvements include:

  • Ability to set an expiration logic for link surveys
  • Ability to preview a survey prior to launch. For surveys in a preview mode, responses are not recorded
  • Improved UI with white background and centered logo
  • Improved UI around sharing the survey link to make it easier to discover and share
1636

New response options provide flexibility for collecting responses

2238

Responses taken within the preview experience are not recorded

1792

Starting today, Essentials and Enterprise customers have the ability to customize their web surveys with CSS, enabling them to create surveys that are more branded and native to their product.

Key parts of the feature include:

  • Ability to set a custom style at the product level
  • Ability to preview styles across all question types
  • Default stylesheet to provide guidance on customizations
  • Deep flexibility and power for customizations
  • Ability to revert to the default stylesheet that Sprig provides
  • Robust error handling

Try it out here or check out our docs to learn more!

2198

The CSV upload experience (accessed through the Connect or People pages) has been improved to make it much easier and error-free for customers to upload their data into the product!

Key improvements include:

  • New data validations on file size, type, duplicate rows, and more
  • Table preview so that customers can preview the data before the file is processed
  • Automatic user_id and email mapping, ensuring we have the right attribution of user and attribute data
  • Upload status so that customers can track their import's progress

Want to learn more? Check out our documentation on this feature.

2208 2210

As of yesterday afternoon, you might have come across our newest question type in our Recruit Interview Participants and Optimize Product Pricing template collections. Text/ URL prompt was built to support two key use cases: 1) introducing a survey (especially useful for longer form surveys), and 2) redirecting survey takers to another page (i.e. a calendly link, a longer form survey, and reviews sites like G2 or App Store).

With this new question type, customers have the ability to customize the header, body, and button text, and to set whether the button leads to further questions in the survey, or links out to another page.

740

Customers can now trigger surveys with multiple trigger events! Survey triggers were previously limited to a single event, meaning that customers wanting to survey users with multiple qualifying events had to create separate surveys or special trigger events.

With this new release, customers can select up to 5 triggers for each survey, providing greater flexibility and control for survey delivery. Learn more.

1368

Following our Zapier and mParticle integration launches, it was time to revamp our Connect Page to improve discoverability while also reflecting the breadth of available integrations. Major changes to this page include the addition of a search bar, filterable tags, and new cards for the updated integrations.

2730

As surveys get longer in length, keeping track of questions can become challenging. Numbers next to survey questions help users keep track of the questions in their survey, allowing them to iterate on surveys more quickly and with fewer errors.

1494

Previously, survey responses could only be filtered by preset time filters (i.e. last 7 days, last 30 days). With the new date/time picker, users can customize a date range to filter responses by, adding greater flexibility to their survey analysis.

2722

Access custom date filters by selecting "Custom Date Range"

2728

We know mobile and web development is often a heavy lift for teams; that’s why we are excited to now provide a React Native option for iOS and Android. Share this doc with your engineering team to save development time by bridging Web UI components and their Java or Swift components to create a single codebase.

299