Identify Signals

Deeploop.js has sophisticated algorithms built-in that match website analytics signals with actual lead or customer profiles.

Approach	Description
Email Links exact	Once a lead clicks on any link in an email a cookie is set that identifies this lead or customer going forward, even when they revisit the page without clicking on the link again. And if desired, deeploop.js identifies the previous website signals that came from the same browser the lead is using at the point of identification.
Identify API exact	You configure explicit calls of the Identify API to inform deeploop.js which lead these signals comes from using an email address or lead-specific ID
IP Matching approximate	deeploop.js uses an elobrate IP Matching alogrithm that provides meta-data for every signal and also helps identifying traffic coming from non-masked IP addresses.

Identify API

While in most cases the Email Link and IP Matching identification is enough (particularly in top-of-funnel sales processes) using the identify API can be helpful when you would like to track the behavior of current customers to drive customer success workflows.

Our recommendation for when and how often you should call identify is as follows:

• After a user registers
• After a user logs in
• When a user updates their info (eg changes or adds a new address)
• Upon loading any pages that are accessible by a logged in user (optional)

An example identify call looks like this in Javascript:

deeploop.identify("55480cfqa0067", {
  name: "Michael Ridley",
  email: "mr@deeploop.com",
  plan: "premium", 
  logins: 5
});

An identify call has the following fields:

Field	Type	Description
userId optional	String	Unique identifier for the user in your database While this is optional, we recommend using your internal user ID to consistenly tie
traits optional	Object	Free-form dictionary of traits of the user, like email or phone which deeploop.js uses to identify the signal against your existing leads or customers. Refer to the next section on which values can be set here.

Note: If the person you are attempting to identify does not yet exist in Deeploop, the lead will be created in your Deeploop account. However it won't be added to any workflow or sequence. To achieve this, refer to the Workflow Source configuration inside a specific workflow in the Deeploop Application.

Note 2: If the userId is unknown you can either pass an empty string '' or set for example a form input such as the email address as the userId.

Traits

The traits that are passed in the identify call are used to create or update leads. However Deeploop only accepts keys that are present in the actual lead model definition in side the Deeploop App. Fields that are not defined in the lead model will be ignored by Deeploop.

Examples of lead model fields:

Display Name	ID (used in identify as keys in traits)
Email	email
First Name	first_name
Last Name	last_name
Phone	phone
Company	company