CRM Targeting

Custom data attribute targeting enables targeting surveys based values previously passed to Pulse Insights so you can ask questions only to a hyper-targeted segment of users.

For example, if you pass loyalty points balance, you can target a question to users who have over, say, 50,000 points.

Numerous options are available:

• ‘Equals’ is an exact match. E.g., ‘customerType equals member’ only matches users with that exact value, ‘member’, defined for ‘customerType’ attribute.

• ‘Does Not Equal’ matches users that do not match the value. E.g., the targeting ‘customerType does not equal member’ will match users with the values defined that do not exactly match ‘member’, such as ‘trial user’ or ‘nonmember’

• ‘Contains’ is a partial match. e.g., ‘locale contains en’ matches users with locale of ‘us-en’ and ‘uk-en’.

• ‘Does Not Contain’ will match any user whose defined value does not include the targeted value. E.g., ‘customerType does not contain member’ will match users with the values defined that does not contain ‘member’, such as ‘trial user’, but would not match ‘non_member’, since that value contains ‘member’.

• ‘Exists’ means that some value is defined. E.g., ‘loyaltyStatus exists’ would match users that have any value defined – say silver, gold, or platinum.

• ‘Does Not Exist’ means that the value is not defined. E.g., ‘loyaltyStatus does not exist’ would match users that do not have any value defined for that attribute.

• ‘Is Greater/Less Than’ evaluates the value defined and will match users with a value bigger/smaller than the targeted value. E.g., if ‘pointsBalance is greater than than 50000’ is the target, then a user with a pointsBalance of 50001 will be eligible to see the survey, but a user with a points value of 50000 will not be shown the survey. If the value is stored as a string, Pulse Insights will still attempt to evaluate it as a number.

• ‘Is Greater/Less Than or Equal to’ evaluates the value defined and will match users with a value bigger/smaller OR matching exactly than the targeted value. E.g., if ‘pointsBalance is greater than than 50000’ is the target, then a user with pointsBalance of 50000, or a user with a pointsValue of 50001 will both be eligible to see the survey.

You can add multiple user attribute targeting rules by clicking on the “Add Another” button. To remove a rule, click on the X to the right of the row.

• All of: If you have multiple rules and you’d like your target audience to match each rule, then use the “All of”, which builds a block of condition statements joined by AND. E.g. a user must have a pointsBalance equal to 50000 AND have a defined customer Segment (customerSegment exists). The user must match every set of conditions you add to “All of” in order to be eligible for the survey. ‍

• Any one of: If you have multiple rules and you’d like your target audience to match any one of the conditions, then use the “Any one of”, which builds a block of condition statements joined by OR. E.g. a user must have a loyaltyStatus of gold OR have a pointsValue less than 1000000 OR an undefined customerSegment (customerSegment does not exist). The user must match at least one, but not ALL of the set of conditions you add to “Any one of” in order to be eligible for the survey.

Client Key Required: A Client Key is your anonymous userID that you pass to Pulse Insights to uniquely identify the user, E.g. customer ID, order ID, custom ID. Enable “Client Key Required” if you’d only like to show the survey if the user has a defined client key.