2

Our site is set up so certain content is protected to logged-in users only. We're using WFFM to do the login form with the login save action, and the user pool is in a custom domain instead of the standard "extranet" domain that ships with Sitecore. The client is reporting that they aren't seeing any data from logged in users, but it seems to continue tracking people as anonymous users.

Since we're using a custom domain, is there something extra that needs to be done for analytics to track those users? Is there another possible reason why analytics wouldn't switch from tracking a user as anonymous to tracking them as logged in?

Improve this question
1
  • Does these secured pages have separate layout? if so, check if it has Visitor Identification element
    – Ahmed Okour
    Commented Feb 10, 2017 at 17:15

1 Answer 1

Reset to default
8

Just because you are logged in does not mean it will treat the user as a contact in xDB. You should check out how to identify contacts.

The key being to call Sitecore.Analytics.Tracker.Current.Session.Identify(identifier), where identfier is the username or email.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.