Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

Connecting visitors in different browsers

Apps2015
Level 2
Level 2

We are tracking a forgot password workflow action using adobe site catalyst. The flow happens something like below

  1. User requests for forgot password
  2. He provides the email address and clicks on create new password
  3. New password generation like is send to his email address
  4. User clicks on this link and generates a new password

First 3 actions occurs in the same browser. The 4th activity can occur in the same browser or a different browser. Because of this, site catalyst considers that user as a different one (different visitor ID) and considers that as a totally different visit. Ideally the number of users who completes activity 4 should be less than that completes 1,2,3. But for us, we are seeing more users who completes activity 4 which could be because of this different visitor issue.

Can someone please suggest a better approach to solve this?

1 Accepted Solution
Abhijeet_Mishra
Correct answer by
Employee
Employee

Hi,


Cross browser visitor identification requires Custom Visitor ID to be implemented. There are different ways you can set your own Visitor ID.

Please read about it more here: Custom Visitor ID.

View solution in original post

3 Replies
Abhijeet_Mishra
Correct answer by
Employee
Employee

Hi,


Cross browser visitor identification requires Custom Visitor ID to be implemented. There are different ways you can set your own Visitor ID.

Please read about it more here: Custom Visitor ID.

View solution in original post

Apps2015
Level 2
Level 2

Thanks Abhijeet.

If we are using custom visitor ID, we should make sure that every where in the organization which uses Adobe analytics, the same approach is used, otherwise the visitor is considered as a different one.

Abhijeet_Mishra
Employee
Employee

That's correct. Whichever Visitor Identification method you choose to use, it must be consistent across all your sites/orgs.