Visitor Identification enables you to associate session data and events with people. "People" can include sign-in users of your website or store, or visitors who submit sign-up forms somewhere on your website.
Using Visitor Identification
Before you can implement Visitor Identification, you first need to add the Data Layer Script to the <head> section of your website. If you've already implemented Custom Events, the script has already been added to your website.
The Attribute Object
The Attribute object is where values related to visitor identity are stored.
By default, an ID is automatically generated for every unique visitor, but using Visitor Identification, you can override this ID with your own value, such as an identifier from your web app.
You can also store a visitor's email address and virtually any other type of data that can be stored as a key-value pair.
Below is an example of a function that when called sets Attribute Object values.
In the above example, id, mail, age, and persona are keys that are paired with values provided by your website or web app.
You can include any number of key-value pairs to suit your use case. Any of the values tracked by Flowpoint are recorded to your project's Session Log and can be exported for use in other apps.
All Keys Are Optional
You don't have to configure Visitor Identification (or include any key-value pairs) to track sessions on your website. As mentioned earlier, all visitors are automatically assigned a unique ID by default. But by using Visitor Identification, you can augment and powerfully enhance the visitor telemetry you capture from your website.
Testing & Troubleshooting
Like the testing steps for Custom Events, once you've configured Visitor Identification, you can trigger it on your website and validate the implementation by checking the Session Log for your project in Flowpoint.
If Visitor Identification doesn't appear to be working, trigger it on your website and check your browser's console for any errors. Most issues are related to syntax errors such as typos or incomplete arguments.