Understanding Lytics / Product Documentation / Lytics Javascript Tag

Testing & Verification

Once the Lytics JavaScript tag has been installed it is important to verify that data is being collected as expected. The following are recommended ways for verification depending on what type of confirmation you are looking for.

Verify Lytics JavaScript Tag is Loaded

The core JavaScript tag has a helper method that will return true if all Lytics resources have been loaded properly.


Verify Data is Being Sent to Lytics

The easiest way to verify that a request was sent with your data is to use Chrome Developer Tools and look at the Network tab. This will list every request your site is making. Among those will be, if working correctly, requests to Lytics. Simply filter all results by lytics.io/c/ using the search box. Clicking on any of those docs will also reveal details of the request such as the query params.

Verify Lytics has Received Data

An overview of all data received on any given Lytics stream is surfaced inside the data stream section. When attempting to confirm that Lytics has received data for a particular stream, select the stream name from the drop-down menu. Unless you have configured the tag to use a custom stream, the Lytics JavaScript tag will send data to the default stream.

Check the raw keys table in the data stream section below the data ingress chart for the raw field in question.

If you are not seeing your event in the data stream, this may be because it is being filtered out or, if the data was sent recently this could be a tag configuration issue. To ensure that data is being sent to Lytics you can view the "Network" requests tab in Google Chrome developer tools. For assistance with debugging these types of issues, feel free to contact our support team for assistance.

Testing Audiences

In order to create a proper testing environment and not run into merge conflicts and false positives, please follow these guidelines and steps:

  • Always use incognito mode. An incognito window removes all cookies, caches, etc. ensuring you have no history with the site and that no email addresses share a cookie. The entirety of a test session must take place in the same incognito window so that all actions tie to the same profiles. All incognito windows must be closed between testing sessions to clear all cookies. Google provides instructions for opening an incognito window.

  • Use a test email only once, and then expire it after that.
    • Recommendation - keep an excel/googlesheet log of which email address was used for each test
    • Google allows you to use punctuation in email addresses, while still sending to the same account. For example: [email protected] and [email protected] will both be delivered to the same inbox, however Lytics will create separate profiles for each. This will cut down on how many emails you have to create.

If you are testing audiences that are not tied to an email:

  • Use Google Chrome developer tools to find the cookie id for your anonymous web session. This will allow you to search for it in the Find a User feature of the Lytics dashboard.
    • On the tagged website, right click and select Inspect
    • Select the Console tab
    • Enter jstag.getid() to get your cookie/seerid

If you are testing audiences that tie email and cookie actions together:

  • You need to ensure a merge event occurs that will tie the incognito session cookie with your test email.
    • Fill out a form that is sending an email address over to Lytics via jstag.send()
    • Open a link from an email with the email pixel embedded in to in an incognito window by right-clicking the link and clicking Open link in incognito window
    • Make an API call that will force-append an email to your cookie

As a best practice, keep a testing doc that reflects the date and time of when you tested, the link of the Lytics audience you are testing, along with results and screenshots. This will assist Lytics support in tracking and debugging any issues.