You can give a highly personalized experience for visitors landing from outbound emails, social media campaigns, push notifications, etc.
For example, when you send a marketing/sales mail to your prospect, in most of the cases you know the prospect's first name, last name, company, designation, use-case to highlight, etc. When the prospect lands on your web-page clicking on that link, the page will be totally personalized. In other words, he will be seeing what you want to showcase.
CustomFit.ai SDK auto fetches the query parameters with below prefixes and assigns to the user (visitor) properties.
cfup_{user_property_name}={user_property_value}: The prefix 'cfup_' stands for CustomFit User Property. CustomFit SDK extracts the user_property_name and user_property_value and sets it to the user profile. Example: cfup_first_name=John cfup_company_name=oracle
cfupp_{user_property_name}={user_property_value}: The prefix 'cfupp_' stands for CustomFit User 'Private' Property. CustomFit SDK extracts the user_property_name and user_property_value and sets it to the user as 'private' attribute (meaning, the value won't be stored at the server side for analytics and insights, but will be used only for rule evaluation).
Example: cfupp_gender=male
Use these captured parameters in the Experience/Dynamic-Element rules. For more information about the rules on Elements check here and for Experience level targeting check here
Target: Lucy who is a marketer at company BackBuckle
https://{url_path}?cfup_first_name=Lucy&cfup_company_name=BackBuckle&cfup_team=marketing
​
2. Target: John who is a sales head at company BackBuckle
https://{url_path}?cfup_first_name=John&cfup_company_name=BackBuckle&cfup_team=sales