User segmentation
By Timothy Kioko Mulwa on Saturday, 05 July 2014
Posted in Groups
Replies 2
Likes 0
Views 1.1K
Votes 0
Greetings

I would like to implement the scenario below, but all my efforts have failed, I want to segment my users during registration, could you please advise?

You have both Teachers as well as Students that signs up on your site. However, you don't actually want to ask the Students group their field of teaching and vice versa when you want to request more information from students.
This is where profiles would come in handy because it allows you to request for information dependent on the profile type the user is signed up to.

Grts

Tim
Hello Timothy,

Hm, based on your scenario, this is actually pretty easy to be implemented in EasySocial. This is just what you need to do,

1. Create 2 profile types in EasySocial
2. Configure each respective profile types to ask for different questions based on the "Custom Fields" tab when you edit the profile type.
3. When a user registers on your site, they will be able to choose if they want to register using which profile type. Upon selecting the profile type, EasySocial will be intelligent enough to display the respective custom fields that are associated with the profile type which they have selected.
Mark
·
Saturday, 05 July 2014 15:10
·
0 Likes
·
0 Votes
·
0 Comments
·
If your teachers use an @gov.edu.com style address, you can automatically assign thrm to a usergroup in joomla, and related assigned profile in Easysocial.

I use http://extensions.joomla.org/extensions/access-a-security/site-access/login-restriction/16287 to automatically sort users according to address ( if you use, just ensure you tell the system to ignore manager, admin, super user roles etc).

This could perhaps help you, or you could also use RS Forms pro, as that has registration I tegration. You could create conditional fields to display fields according to usergroups you want toassign them to.

Hope this helps.
Ryan Scott
·
Saturday, 05 July 2014 08:20
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post