Core definitions in Events

Core definitions in Events

Event Properties


Event properties refer to the characteristics or attributes of an event that can be recorded and analyzed. These properties can provide valuable information about the event, such as the time it occurred, the location, the participants, and any relevant details or context. Event properties can be used to better understand the event, and can be useful in identifying trends, patterns, or relationships within the data.

Event traits

Event traits are characteristics of an event that are used for analysis. Traits differ from event properties in that they are structured in a way that allows them to be searched, analyzed, and aggregated more effectively.

For example, if an event includes a property that describes the type of device that was used to initiate the event, that property could be converted to a trait so that all events involving the same device type could be identified and aggregated.

Event traits can provide valuable insights into the behavior and patterns of users or other entities within a system. By analyzing events with traits, it is possible to identify trends, correlations, and other relationships that may not be immediately apparent from the raw event data.

Profile-less event

A profile-less event is an event that cannot be assigned to any particular profile. This means that it does not contain sufficient information to identify a specific user or entity associated with the event.

Profile-less events can still be useful for understanding the user journey, but they may not provide as much context or insight as events that are tied to specific profiles.

Event context

Event context refers to data that is not directly connected to the properties or traits of an event but may provide additional context or background information that is relevant to understanding the event.

Event routing

Event routing is the process of directing events to specific workflows or processes based on the type and source of the event. This allows businesses to handle different types of events in different ways, and to route events to the most appropriate workflow based on their characteristics.

Events synchronization

In ReBid CDP, event synchronization is the process of managing the order in which events are processed. This includes ensuring that events for a specific profile are processed in a specific order. Essentially, this means that events for one profile are processed sequentially, while events for other profiles are processed sequentially but in parallel to each other.

Event tracking 

By tracking events, businesses can gain insights into how customers interact with their products and services, and use this information to improve the customer experience and drive sales.

Event tracking is the process of collecting and storing data about customer interactions with a product or service. This data can be collected from a variety of sources, such as websites, apps, and customer support systems.

Once the data has been collected, it can be analyzed to identify trends and patterns in customer behavior. This information can then be used to improve the customer experience, such as by personalizing content and recommendations, or by identifying and fixing problems.

To track events with ReBid CDP, you need to:
  1. Create an account and integrate ReBid CDP with your systems.
  2. Identify the events that you want to track.
  3. Collect the data for each event.
  4. Send the data to ReBid CDP.

    • Related Articles

    • Core Definitions

      By understanding these key terms, you can use ReBid CDP more effectively: Traffic ReBid CDP can receive and send data. Therefore, the system defines two types of traffic: Incoming, i.e. systems that are able to send data to ReBid CDP. These will be ...

    • Core Definitions of Workflows

      Flow A flow is the central mechanism of event processing in ReBid CDP. It is a series of actions connected to a graph. The actions are run one after another to fetch, process, and store data. The actions (sometimes called nodes) may do different ...

    • Setup Events

      Events serve as essential tools for monitoring and recording the various activities performed by customers on your website. With this feature, you can effortlessly track their interactions and engagements, helping you gain valuable insights into ...

    • System Architecture

      ReBid CDP is a distributed system that consists of several components working together to track and analyze customer data. The core components of ReBid CDP include: Collectors: Collectors collect events from customer interaction sources, such as ...

    • Key Terms of Actions

      An action is a single task in a workflow. Actions consist of input and output ports. Input ports are used to receive data, while output ports send data via connection to another action. An action is basically a code in the system. Input ports are ...