CDP - Testing Your Olytics Implementation

Owned by Bettina Lippisch
Last updated: May 30, 2024
4 min read

Knowledge Base Home

Search the Omeda Knowledge Base

To verify that your olytics setup is working correctly, someone on your technical team (ideally the person who put the scripts on your site) should follow the steps below after clearing their browser cache:

  • Verify that there are no console errors related to any of the olytics scripts you have added. To check,

    • In Chrome Dev Tools (Inspector) click on the Console tab.

    • Clear the console.

    • Reload your page

    • If you see errors, investigate and verify whether they are tied to any of the olytics scripts you have added.

olytics call console errors: “No behaviorId passed” “Invalid behaviorId passed ” “olytics global import had no write key set” “olytics global import had an invalid write key: ”  

p call console errors: “The oid used in the olytics import is invalid”  

  • Verify the global import is working.

    • Load your site in Google Chrome.

    • Right click the page and select “inspect”.

    • In the Chrome console select the “Network Tab” and clear the traffic listed by clicking the clear icon below the network tab.

    • Refresh the page

    • You should see olytics.min.js with a 200 status. To easier find this particular call – you can type in “olytics.min.js” in the search box. It should look like the screen shot below:

image-20240424-222107.png

  • Verify your olytics.css is working:

    • Follow similar instructions as above, except this time you are going to check for olytics.css and verify it’s a 200 status.

  • Verify Personalization calls are working. This will also verify that you are using the correct olytics key.

    • Load your site in Google Chrome.

    • Right click the page and select “inspect”.

    • In the Chrome console select the “Network Tab” and clear the traffic listed by clicking the clear icon below the network tab.

    • Refresh the page

    • You should see a call designated as p with a 200 status. To easier find this particular call – you can type in “segments/p” in the search box. It should look like the screenshot below:

image-20240424-222117.png

  • Click on the call to expand details then on the right select the “response” tab. You should see something similar to what you see in the screenshot below, if this is the first time you are setting up your script. Make sure you do not see any errors being returned in that response body.

Note: If your team has Personalizations set up already you may see a JSON payload returned with some html content and values, which would be expected. The important thing is that you don’t see an error message when you check the response.

  • If you are using olytics.fire() calls – verify they are working.

    • Load your site in Google Chrome.

    • Right click the page and select “inspect”.

    • In the Chrome console select the “Network Tab” and clear the traffic listed by clicking the clear icon below the network tab.

    • Refresh the page

    • You should see a call designated as just olytics with a 200 status. To easier find this particular call – you can type in “olytics” or “oqs” in the search box. It should look like the screenshot below

  • If you see 2 olytics calls (The first will be an OPTIONS call the second will be the POST call that is sending data) – make sure to select the second call –

  • Click on the call to expand details and then click on the Headers tab, then scroll down to see the raw call going out. Verify the fields you are passing under trackingData are what you expect. It will look similar to the screenshot below:

  • Verify the response to the olytics.fire() call in the response tab. It should look like the screenshot below:

 

Table of Contents