Identifying journeys, using ID Scores, URL Parameters or APIs

journy.io is a customer intelligence/data platform (CDP) for SMB that gather visitor,- lead-, customer information — depending in what stage of the funnel they're in — NOT just website visit counts or devices. For journy.io, every interaction and touchpoint tells something about a person, about a persona with intensions. As such, identification is at the core of what we do.
This article explains how to use ID scores, URL parameters or API calls to achieve best identification, without having to compromise on security and privacy compliance.

To consistently explain your identification options during the article, let's make some simple assumptions:
website: site.com
www website is supported! www.site.com
https is supported!

We will also assume you're familiar with the concept of URL Query Parameters. If not, please visit Tracking, using URL Query Parameters and the Advanced Tracking URL

Enabling client-side identification through APIs

On every tracked page, you have a general JS funtion available named journy. To identify a journey, simply call:
journy("identify", { email: "john.[email protected].tld", score: 25 });
Here are the parameters being used:
* email: this is the email you want the current journey to be identified with.
* score: this represents a level (percentage) of probability for identifying the journey, ranging from 0 to 100. If you are not sure if the computer us being shared with temporary users, you should set a low probability such as score=10. If you certain about the connection and the device being used by the intended user, you should use a high score. E.g. at login and email confirmation, score=90. When not providing the score, the default value is score=50.

Here are the simple rules for ID-Scoring: If the new score is greater or equal to the existing one, the journey will be identified by provided email. If NOT, the journey will keep its existing identification.
Example:
journy("identify", { email: "john.[email protected].tld", score: 25 }); //journey is now identified by john.[email protected].tld
journy("identify", { email: "jane.[email protected].tld", score: 25 }); //journey is now identified by jane.[email protected].tld
journy("identify", { email: "john.[email protected].tld", score: 25 }); //journey is now identified by john.[email protected].tld
journy("identify", { email: "jane.[email protected].tld", score: 75 }); //journey is now identified by jane.[email protected].tld
journy("identify", { email: "john.[email protected].tld", score: 25 }); //journey is now STILL identified by jane.[email protected].tld


Enabling URL Paramater identification (per tracked domain)

Since we recognize not everyone's able to start coding to identify journeys, we also allow for the use of URL Identification Parameters.

Since security is key to what we do, we highly encourage you to choose a dedicated self-chosen parameter, per tracked domain, which we also will have disappear from the URL, once identified! These identification options only work on domains that support https!

To enable URL Identification Parameters,
Log in as admin and go to your business settings.
Choose the domain you wish to use an identification parameter for and
Press the 'edit domain' button.
A modal window will appear, looking like this:



The part that interest us in the context of identification, starts at:
* Identify users with URL parameter? this lets you chose whether you want URL Parameter to be used to identify the journey. (In some cases, for security reasons, you may choose not to allow it.)
* Email URL parameter name: this is the parameter to be used, for this particular domain! This could be a new dedicated parameter or maybe an existing one already being used by other martech tools. E.g. &email= which is also used by ActiveCampaign.
* Remove email URL parameter when user is identified? this lets you choose whether you want to remove the parameter form the URL, once identified. Imagine this parameter to also be used by other martech tools, you may choose to keep it in the URL...

When would you use URL Parameters? In most cases, your martech ecosystem includes confirmation emails and email platforms such as mailchimp, ActiveCampaign and others. Simply add the parameter to your emails redirection links and you're good to go...

Identification through URL Parameters always takes a score=25!! If you have already identified a journey with a greater score, the journey will NOT(!) be re-identified with the new given URL Parameter!!

Some Examples:
You are using Pipedrive forms on your website, and want to use &email=<[email protected]> to identify visitors clicking on email links. email is used by different other vendors as well!
Identify users with URL parameter? YES
Email URL parameter name: email
Remove email URL parameter when user is identified? NO

The URL link from the submit button in Pipedrive will look pretty much like:
www.site.com/thank-you-page/?email=%email%

You are using MailChimp as mail service, and want to use &tracking_ID=<[email protected]> to identify visitors clicking on email links. tracking_ID is not used anywhere else!
Identify users with URL parameter? YES
Email URL parameter name: tracking_ID
Remove email URL parameter when user is identified? YES

The URL link from the submit button in MailChimp will look pretty much like:
www.site.com/thank-you-page/?tracking_ID=*|EMAIL|*
Was this article helpful?
Cancel
Thank you!