If you have a website property, you can use our JavaScript integration option to collect data from customers who visit your website. You can easily deploy a JavaScript code snippet on your website and we will automatically capture your customer data based on the configurations you have set.

Click on Website JavaScript Source

Setup Source

  1. Enter a name for your source

  2. You will see a code snippet with some specific macros for first party attributes.

  3. Copy the JS code and paste it into your website page header.

  4. Click on "Test Connection" to check if the code has been successfully implemented.

Click “Next” to proceed to save the Web Pixel Source.

How does the Web Pixel work and what does Lifesight capture?

The website operator needs to add the tracking pixel using a code in the website’s HTML code or email. This code contains an external link to the pixel server. If a user visits the destination website, the HTML code is processed by the client – usually the user’s browser. The browser follows the link and opens the (invisible) graphic. This is registered and noted in the server’s log files.

In addition, various information about the user is also transmitted using this method.

The following data can be acquired and analysed with a tracking pixel :

  • IP address (gives information on the Internet Service Provider and location)

  • Additional information like the EXTERNAL COOKIE ID in this case which is left to the website owner for them to agree to send and unify their 1st party ID reference. This is not mandatory. Below more details on how this can be passed.

  • Additional information like the Event Name can be passed as part of the event tracker. This is again not mandatory.

  • Timestamp of website visit

Tag Deployment via GTM for a 3rd Party Tracker like Lifesight's Web Pixel:

3rd party Tag Deployment Process via Google Tag Manager

Step 1: Click on New Tag

Step 2: Enter a tag name and click on the edit button next to tag configuration.

Step 3: Select Custom HTML Tag - This is to deploy the tag as a 3rd Party function loader

Step 4: Deploy the tag here.

Note: Lifesight’s API needs to be wrapped inside <script></script> tag and deployed.

Step 5: Selecting All Pages as the triggering option

Step 6: Select Custom HTML Tag - This is to Call the Function to send the 1st Party cookie id.

Step 7: Deploy the tag here.

Note: Lifesight’s API needs to be wrapped inside <script></script> tag and deployed.

Tag Script -

Lifesight can collect 1st party cookie values, which returns a String containing the value stored in the cookie, or undefined, if no such cookie exists.

1st party cookie variable is defined in GTM and must be created as a variable type and deployed on the site. E..g variableAnonymousId

This unique variable then should be added to the script.


DLV- Data Layer Variable

<script>window.Personica('PageView',{'ExternalCookieID':{{DLV -segmentAnonymousId}}})</script>

The ExternalCookieID is a variable that expects a unique identifier to be passed
from the client website.
In the above tag script example, the "DLV-segmentAnonymousID" is your reference of the 1st party cookie id reference on your website.

If the client is unable to send any 1st party cookie id information, we require the use of another unique identity to allow us to create a user profile

Google Tag Manager Options -

In Google Tag Manager, there is a built-in variable called Random number – this will return a randomised number between 0 and 2147483647 - this variable can be included to creating a session cookie with a random number.

Example Script:

<script>window.Personica('PageView',{'ExternalCookieID':{{Random Number}}})</script>

Google Tag Manager Random Number Details here :

Implementation Examples :-

Step 8: Selecting All Pages as the triggering option

Examples of Tag after being deployed via GTM or directly on website:

Request URL: https://developer.lifesight.io/personica/api/data/v1/9d6e08a1-015c-4092-9c9d-ad8846c9b614?

'ExternalCookieID'=<1st Party ID>

Did this answer your question?