The Unify Intent Client can be used to log user activity across multiple subdomains of the
same top-level domain. For example, if a user visits your marketing website at
www.yoursite.com
and then logs into your production web application at app.yoursite.com
, the activity in both
places will be attributed to the same person.Page View Events
Website page views are an indicator of buyer intent. You can log this information to the Unify platform for usage with thepage
method.
There are two ways to collect page data with the Unify intent client:
- Automatic monitoring of the current page
- Manually via the client
page
method
Automatic Page Monitoring
The Unify intent client is capable of automatically monitoring the user’s current page to trigger page events. This will happen by default when the client is installed via the Unify Website tag. If the client is installed via a package manager, you must pass theautoPage
configuration option
when instantiating the client. See Configuration below for more details.
Automatic page monitoring works in Single Page Apps, too!
startAutoPage
and stopAutoPage
methods on the client:
Manual Page Logging
You can also manually trigger a page event with thepage
method on the client. This is useful
when you do not want to trigger page events for every page.
Identify Events
All intent data collected for users by Unify is anonymous by default. When intent events are logged, Unify will attempt to automatically de-anonymize the IP address of a user to associate them with a specific company, but their personal identity will remain anonymous until an identify event is triggered for them. There are two ways to collect identity data with the Unify intent client:- Automatic monitoring of email input elements
- Manually via the client
identify
method
Automatic Input Monitoring
The Unify intent client is capable of automatically monitoring text and email input elements on the page to collect user identity. This will happen by default when the client is installed via the Unify JavaScript tag. If the client is installed via a package manager, you must pass theautoIdentify
configuration option when instantiating the client. See Configuration
below for more details.
In either case, this behavior can be enabled or disabled programmatically via the startAutoIdentify
and stopAutoIdentify
methods on the client:
Manual Identification
You can also manually trigger an identify event with the identify method on the client. This is useful when users log-in with OAuth or SSO, for example, because they do not enter their email into an input on the page.Configuration
The following configuration options can be passed when initializing the client:Tells the client to automatically log page events whenever the current page changes.
Works for static websites and Single Page Apps. Also logs a page event for the initial page.
Tells the client to automatically monitor text and email input elements on the
page for changes. When the current user enters a valid email address into an input, the client
will log an identify event for that email address.