Generate Embed Code


On this page we guide you through all necessary steps to generate an HTML embed code for your survey. Once created and copied to your email tool, the embed code will render the first question of your survey inside an email.

As the name suggests, the code we are creating is common HTML. Once you obtained your copy of the embed code, you can further customize it to your liking as described here.

To get started, navigate to the “Embed Code” tab in the survey editor.

Set a color theme

You can choose the color scheme of your embedded survey. When changing colors, you’ll see an updated survey preview on the right side of the screen.

Please note that the color selection only applies to the embed code you are using in your email. You also might want to adjust the colors of the survey page in the “Landing Page” tab.

NPS and CSAT questions allow you to use a multicolor scale. If this option is enabled, the colors of the multicolor scale are used when generating the embed code.

Choose Email Service Provider

As a next step, choose your Email Service Provider (ESP) and copy the HTML code to your clipboard.

Once you select your provider, Refiner fills the “Identify User” field with matching tags. These tags will identify survey respondents with their emails address. You can replace the suggested code with provider specific tags, for example if you want to use a different identifier or add additional data (see below).

If the solution you are using is not listed, don’t worry. You can still select “Other” which generates a generic embed code with a blank “Identify User” field.

The generated HTML code is now ready to use in your email template. If you know your way around in HTML, you might want to check out how to customize the embed code event further.

Finally, paste the HTML code to a template in your email sending solution. The process of using HTML code snippets in an email differs for each provider.

Choose language

If you are using our multilingual surveys feature, you’ll see the option to choose the language for the embed code. Choosing a language will translate labels and also determine the language used on the survey landing page.

Import additional user data

The “Identify User” field allows you to import any kind of user data from your email tool to Refiner. When you select an Email Service Provider, the field already contains a code suggestion to identify survey respondents with their email address. You can further customize the code suggestion to import more data from your email tool to Refiner.

Add user traits

Depending on the capabilities of your email service provider, you might be able to access additional user traits (e.g. company name, subscription plan, …) that you want to import to Refiner. You can use the “Identify User” field (see above) to move data from your email service provider to Refiner.

What data you can import to Refiner depends on your email provider. Usually you’ll have access to data like the recipient name, their email address and custom fields that you created. You can check their documentation to figure out which data fields are available.

You can add additional parameters to the “Identify User”, separated with a “&” symbol. The syntax for Refiner is “&contact_<any field name>”. The syntax for the source data is depending on the email service provider you chose.

Here is an example how this could look like:


Add hidden response data

You can also attach hidden data fields to the survey response. You can either import dynamic data provided by your email service provider, or static text data.

As with user traits, you can data to your responses by simply adding more fields to the “Identify User”, separated with a “&”. However, instead of using “contact_” as a field prefix, you can use “response_” as a field prefix.

Here is an example how this could look like:


Add response tags

Next to adding user traits and hidden response data, you can also add response tags using the “Identify User” field. The syntax for adding a tag is “&tags=Tag1,Tag2,…”.

Here is an example how this could look like:


Was this helpful? Let us know with a quick a vote