Date: Fri, 29 Mar 2024 08:33:45 +0000 (UTC) Message-ID: <281764977.289.1711701225751@ac9b4408749a> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_288_1070991988.1711701225751" ------=_Part_288_1070991988.1711701225751 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Each visitor, whether known (has an email) or anonymous, has an ID assoc= iated with them. We call this ID the Prospect ID, or PID. The PID can be us= ed in various ways, such as accessing Lead Liaison's API to look up a Prosp= ect by the PID value, logging a Custom Activity, and = more. Lead Liaison stores an encrypted version of the PID in a browser cook= ie, named ll_prospect_id_encoded.
To begin collecting the PID from your website, make sure to do the follo= wing:
var ll_is= _append_prospect_identifier_cookie =3D true;
Note on Location
This value must be before this line, LazyLoad.js('https://t1.llanalytics.com/tracking_engine/colle= ctor.php');
=
The PID is stored as a browser cookie and encrypted using base64. To read the PID via JavaScript and decryp= t it use the following code:
In the example below, we're using the Console tab in Google Chrome to re= ad and decrypt the PID.
=