Personify template strings, tags and custom fields are the three things that works only if the current visitor is linked to the crm systems ( ActiveCampaign, Drip ). If you personalize a page for users based on how they are tagged inside the crm or on what custom fields they are related to then personify needs to know about the current visitor.
The only way personify can translate the template strings is by fetching the user details from the local WordPress database or from the crm. To make things fast personify searches the local db for the user existence and if not found then searches / fetches the information from the CRM itself, then it saves a copy of the data that’s fetched from the crm inside the local db for future reference / usage.
After the user data is fetched the personalized template strings are replaced with the linked user data such as tags and custom fields, if for some reason the user data is not found or not set inside the crm the template strings can be appended with a default text which will be replaced by personify instead of displaying nothing.
The same applies to the tag, custom field conditions, if personify can’t find the user data then the condition is completely ignored and returns false. In order for the custom fields and tag conditions to work then the person who is viewing the page should be linked to the crm. This happens during 3 process.
1. If the user logs into WordPress, then personify fetches that user information from the local db or from the crm.
2. If the user who views the page is being redirected after he completes a surveyslam quiz.
3. If the user gets redirected to the personalized page from a smart link.
In this article we will talk about how surveyslam can be utilized to work in tandem with personify so that a desired result can be achieved.
In order for template strings, tags and custom fields to work on a personalized page the users who are viewing the page should be identified, before the user is being shown the personalized page the user can be redirected to a personalized page after the user completes a survey, this way personify will drop a cookie on the users computer which encrypts the user data and stores inside the cookie. This cookie information can be later decrypted by personify and the user information is fetched from the local db or if not present then it’s fetched from the crm.
The fetched user data is later used to personalized the content on the destination page the user got redirected to.