Velocidi enables you to collect real-time events in your customer data platform with first-party tags:
This method provides the most flexible approach for tracking events and it is the preferred method. Its main use case it to capture user interactions with the E-commerce website. The event channels expected to be collected via this method are: Web and E-Commerce.
In order to use the tag in a site, the following snippet is the minimum piece of code that should be
included on the page. It should be added as close to the opening
<head> tag as possible.
This snippet only needs to be included once per page.
Don't forget to change the URL
Since Velocidi provides a first-party system for each client, each client must include the system-tailored script tag from their domain. The URL should be replaced with your system endpoint. This applies to all interactions.
For standard installations, a client whose website is at
example.com would use the following URL:
Once the tag as been included, you can begin collecting user interactions with your site by calling
pcdp function and specifying the required parameters for each event type.
For this example, you can see its required parameters in the Page View details page.
For more information about supported events and their details see the Complete list of events by categories.
For this example, you can see its required parameters in the Ad View details page.
This interface is used to capture clicks before directing browsers to the original destination URL. It can be used for tracking clicks on display banners, search ads, e-mails, and any other type of click-through.
Please note that this interface requires you to URL-encode all parameters, including the
For when it is not feasible to perform a URL encode on the
ourl, you can use the next interface
/events/click0 instead of
/events/click) where you can provide the non-encoded
ourl but it must be
the last query parameter of the URL.
For these examples, you can see its required parameters in the Ad Click details page.
For more technical details see the API Reference.
Once you have tagged your website or during that process you can verify that the events are entering the system correctly using our dashboard.
You can see the latest collected events in the Dashboard under Collect > Events > All Events.
If all of your tags are implemented correctly, there is nothing more for you to do. However, in the case that something goes awry, you'll see an error message in the Events page of your Velocidi user interface, letting you know immediately what needs to be corrected.
Any time you see an yellow exclamation point in the ‘Event type' column, you can click into the event details to see the specific errors flagged for that event. When you see errors in your events stream, contact your designated client support specialist and we will help resolve the issue.
Bots are software applications that have been programmed to automatically do certain (often repetitive) tasks without human user intervention. They can be of several different types, such as chatbots, social bots, web crawlers or malicious bots.
Hence, bot traffic is any non-human traffic happening in a website or application. While some of it is actually interesting and used by helpful services (eg. search engines, digital assistants), depending on the context of your website/app, this traffic may be something that you should not take into consideration as website/app activity.
Usually this type of traffic is detected by analysing the user-agent strings that are sent in the header of the HTTP request. This string provides information on where the request originated from, including the operating system, and browser.
Bots with no harmful intent often identify themselves with their own user-agent. Google, for example, made public the list of their user-agents and strings, with adjoining info on what they are used for.
Velocidi uses a library to maintain the list of user-agents identified as bots and filter the traffic from these.
This traffic is diverted and written in a different database, for short period of time, so that it can be used to debug any related issues, if needed.
If you are integrating with us directly, be aware that most non-browser traffic may be filtered. This applies to development tools (e.g.
wget) and others. Consider sending a whitelisted user-agent to prevent this.