Using the API to set Custom Property matching

The ability to target based on custom properties is part of our Growth and up plans
Qualaroo survey targeting tab supports many conditions that can apply to any website. Yet sometimes you might want to add a targeting condition that are specific to your website and visitors. 
For instance, you might decide to display a survey only to users who made a purchase in the past 30 days and only when the shopping cart contains exactly 2 items. In this case, the “number of items” and "has made a purchase in the past 30 days" are custom targeting properties, where “2” and "yes" are their respective required targeting values. 

You can notify Qualaroo of the value of any number of custom properties with the JavaScript API. Think of this as tagging a visitor with a name/value pair. This step requires your developers to update your page's code, so you might want to tag visitors with all the possible name/value pairs that you are likely to use for targeting surveys in future. This way you will not have to ask your developers every time you want to use a new property for targeting.

If we were to use the first example of targeting those who made a purchase in the past 30 days when their cart contained 2 items, the additional JavaScript you would want to add to your site would look something like this:
<script type="text/javascript" charset="utf-8">
    _kiq.push(['set', { 'num_items': <code for # items purchased>, 'purch30': <code for whether purchase has been made in last 30 days> }]);

This code is added directly beneath the main Qualaroo JavaScript. 
Continuing with the above example, now you can specify your custom targeting requirements in the Targeting tab of your survey:
It's important to note that with custom property matching, all values will be rendered as strings, and will not be interpreted by our API as integers or booleans. Whatever is passed is used, and names do not need to be single-word, camel-cased, or have any other specific formatting or syntax. Generally, it's best if they do not contain spaces ("customer_attribute" vs "customer attribute"), and the name cannot contain hyphens.

You can set the values any number of times during the visit, on page load or after the page loads. Every time you set a new value, Qualaroo will check again if a survey should be displayed.
Now that your developers have tagged visitors with the actual value of the properties, and you have specified the required values in the configuration UI, Qualaroo will compare the actual values with the required values. The survey will show up only if the values of all targeting parameters match their respective actual values.

Custom requirements are applied in addition to the standard ones. This allows you to target to surveys based on the combination of standard requirements and custom properties specific to your business. 
Any properties that are passed in a survey show up in the Individual Responses tab, and in the CSV export of your survey responses.
Have more questions? Submit a request
Powered by Zendesk