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:
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:
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:
Using the Webhooks by Zapier Action (Post event) is another great way to bring customer data into Omeda from a third party application. This option is more targeted to those who want to use our Data Loader Webhook (because of the record list tracking and easy data mapping capabilities) but the third party app does not support our Webhook. Zapier formats the data coming from the third party app in a way our Webhook will accept so this is a great way to still take advantage of our Data Loader Webhooks.
Note: Data Loader Webhooks do not support Magazine or Website products at this time so if you’re looking to bring in data that includes these, take a look at our other Zapier Action options.
What you’ll need to get started:
Create a new Data Loader Webhook. Learn more about our Webhooks here. After you’ve created your Webhook in Data Loader, keep the Webhook URL handy.
Create your Trigger in Zapier. The Trigger will be where you want data to be sent from based on a certain event.
To create the Action, select the Webhooks by Zapier app in the app search. Select POST as the Event.
Input the Data Loader Webhook URL into the URL field of the Action setup.
In the Payload Type drop down, select json.
In the following Data fields, in the first column, create static headers for each incoming field from your Trigger Event.
In the second column of the Data fields, map the incoming data from the Trigger Event to the appropriate field headers:
Once the incoming fields are mapped, you should be all set to test your Action! If successful, you should see a record in your Data Loader Webhook, under the Records list. From there, you can map the incoming data to your Omeda database.Learn more about mapping data in Data Loader here.
Once Webhook is mapped, it’s time to publish your Zap!
Table of Contents
| Table of Contents | ||
|---|---|---|
|