As a default our link anonymises in-coming comments, but it is easy to add an identity or properties to the link if you want to track, respond to or segment responses. We refer to this data as a recipient.

Some scenarios in which we have found this useful:

  • Adding a survey link to your personal or marketing emails to collect feedback
  • Using the link in your app or website

In each scenario, you would add the identity and any properties as dynamic content to be added to the end of the link

Having added a recipient and/or properties, you will see these on the responses page and in any data exports!

Adding a recipient identity

When you receive a link, it comes in the following format: 

https://responses.zenloop.com/web/surveys/<survey_hash_id>

In order to add a recipient email to this string, at the end of the string of digits and characters, you should add the following: 

?identity=example@exampledomain.com&identity_type=email

As a result, the link should now look like: 

https://responses.zenloop.com/web/surveys/<survey_hash_id>?identity=example@exampledomain.com&identity_type=email 

identity_type  is a field that specifies the type of recipient identity, it can be either email  or  custom.  Custom identity opens a possibility to pass any type of identity you find meaningful, for example a phone number:  identity: '+4900300300'   identity_type: 'custom'
You can also add a first_name  and last_name to your recipient (optional). Now the link could look like:

https://responses.zenloop.com/web/surveys/<survey_hash_id>?identity=example@exampledomain.com&identity_type=email&first_name=john&last_name=brown 

Note:
The “@” may be replaced with “%40”: this is fine!

Note:
you can only have one identity per link, and the identity has to be in a valid format (i.e. it should be a real email).

Adding recipient properties

While a recipient is not required to add properties, it is highly recommended, since this will let you identify and respond to recipients directly within our application. If however, this isn't possible, you can still add as many properties as you want in the following format:

&properties[Key]=Value

As a result, the link could now look like:

https://responses.zenloop.com/web/surveys/<survey_hash_id>?identity=example@exampledomain.com&identity_type=email&properties[Country]=Germany&properties[Colour]=red

Each property can only have one key and one value, and properties must be separated by an “&”


 __________________________________________________________________

Solutions to common questions:

Q – Do I have to add recipients and/or properties?

A – No, these are not required, but will help you to respond to visitors later by storing their information. It is even possible to attach anonymous properties (just leave out any identifying information!)

 __________________________________________________________________


Q – Can I automate this process? Do I have to do it manually?

A – Automation is definitely possible! It depends on the use case and the tools you have available, but some common examples include: 

  • For email or marketing automation tools (e.g. Mailchimp or Hubspot) you’ll likely need to import a unique link for each recipient. This could be done with a spreadsheet, or an API call that maps email and properties onto each link. You would then incorporate that link into your campaigns 
  • On your website, you can dynamically pass through an email and properties to the link (similar to having a personalised review or coupon link

__________________________________________________________________


Q – My properties aren’t coming through properly, any ideas why?

A – There are two common causes for this:

  • First, check to make sure you have only a single unique key and value per property (i.e. you shouldn’t have the following format: &properties[country,colour]=Germany,red
  • Second, it is best to avoid using symbols that already have a meaning. For instance, avoid using “&” or “[]”within the text of your keys or values
War diese Antwort hilfreich für dich?