Skip to content

Identify visitors ​

Tell QuickPipe who the visitor is, for example after a login or a registration. QuickPipe then connects the earlier visits of this browser to the person.

Procedure ​

  1. After the visitor logs on or sends their email address, call identify:

    ts
    lg.identify({ email: '[email protected]', userId: 'u_1842' });
  2. With the script tag, use:

    js
    lg('identify', { email: '[email protected]', userId: 'u_1842' });
  3. When the visitor ends the session, call reset:

    ts
    lg.reset();

Result ​

QuickPipe adds the identifiers to the visitor of this browser. The match mode of each identifier decides the result. When an identifier with the mode merge belongs to a known person, the visits before identify and after it belong to that person. An identifier with the mode suggest, for example phone, gives only a suggestion. QuickPipe examines the suggestion before it joins two people. After reset, the browser gets a new visitor ID, and the next visits do not belong to the person.

Identifiers ​

IdentifierExampleDefault mode
email[email protected]merge
phone+46701234567suggest
linkedinProfilehttps://www.linkedin.com/in/anamerge
xProfilehttps://x.com/anasuggest
instagramProfilehttps://www.instagram.com/anasuggest
githubProfilehttps://github.com/anasuggest
tiktokProfile@anasuggest
youtubeChannelhttps://www.youtube.com/@anasuggest
userIdThe user ID in your productmerge
leadIdThe lead ID in QuickPipemerge
anonymousIdThe visitor ID from the cookie lg_aidmerge

A person can have more than one value of an identifier, for example a work email and a private email. QuickPipe does not use the case of a value to match, so [email protected] and [email protected] are one value. A handle of X, Instagram, GitHub, TikTok or YouTube can belong to a company, so it gives only a suggestion.

The client needs consent to store the visitor ID. Refer to Set consent.