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 websites, internal systems and services.
- The second type of traffic is outgoing traffic. These are external systems to which we send data or send data inquiries.
Note: In ReBid CDP, we call incoming traffic - event sources and outgoing traffic - destinations.
Bridge
A bridge is a piece of software that connects two separate systems or applications, allowing them to communicate and exchange data. In ReBid CDP a bridge collects data from a particular source, such as a queue, email, or social media, and transfers it through event source. When a new event source is created, the appropriate bridge must be selected to facilitate the collection and transfer of data.
Event source - inbound traffic
To start with ReBid CDP, you must create a new event source. That source will give you an identifier which when attached to your track calls will start collecting data about your users. Event source needs a bridge that will transfer data to the system.
Note: The data that is received through this type of event source is not saved in the system, but is only processed by the workflow. In ReBid CDP, a Transitional Toggle option is available. Using this option, you can choose if you want to save the data or not.
Warning: Some sources may require user consent to collect data.
Resource
A service resource is a type of resource that refers to a service or application that is accessed over a network or the Internet. Service resources can provide a wide range of functions and capabilities, including data storage, communication, computation, and more.
In ReBid CDP, resources are data sets or services that can be queried for data. They often require authentication, such as passwords or tokens, in order to access their data. When creating a resource in ReBid CDP, you may be asked to provide access to both test and production resources.
ReBid CDP allows you to test your internal processes by running workflows in test mode. In test mode, a workflow must connect with test resources in order to avoid making changes that could potentially cause problems in the production environment.
Session
In the ReBid CDP, a session is a type of data that is often associated with a visit to a website or application. As long as the session remains unchanged, the visit is considered to be ongoing. The session id is set when data is sent to ReBid CDP, and it is typically under the control of the client program.
The session often contains data about the context in which an event was launched, such as the type of device, operating system, or other characteristics of the user's environment. This data can be used to understand the context in which events are occurring and to tailor the response or actions taken in response to those events.
In general, a session is a period of time during which a user is actively interacting with a system or application. Sessions are often used to track the actions and behavior of users over a period of time and to provide personalized experiences or services based on that data.
Note: The data is stored for the duration of the session.
Event
In the ReBid CDP, events are representations of something that is happening at a particular time. Events can be used to track visitor behavior on a website or application, and they can capture a wide range of actions and interactions. Examples of events may include clicks on links, logins, form submissions, page views, or any other action that needs to be tracked, such as a purchase order.
Profile
A profile in ReBid CDP is a detailed record or representation of an individual or entity, typically including information about their characteristics, interests, and activities. A profile can be used to summarize and organize data about a customer in a way that is easy to understand and access.
A profile in ReBid CDP is a set of data that represents information about a customer. Profiles can be updated based on incoming events and data from external systems, and they can contain both public and private data.
Private data in a profile is typically sensitive information, such as a user's name, email address, age, and total purchases. Public data in a profile may include information such as the segment to which a user belongs, the last time they visited a website or the number of visits they have made.
The profile is updated by the workflow, specifically by the actions that are performed within the workflow. The data in a profile can be used for a variety of purposes, such as marketing campaigns and other types of analysis. By updating the profile based on incoming events and data from external systems, it is possible to maintain an up-to-date, comprehensive view of a customer.
Segment
In ReBid CDP, a segment is a group of customer profiles that have been identified and grouped together based on shared characteristics or behavior. A segment can be defined using a simple logical rule or by more complex artificial intelligence (AI) models.
Once a segment has been defined, it becomes a part of the customer's profile. A segment defined in ReBid CDP can be used in the segmentation workflow, which allows for targeted marketing and other types of personalized experiences or services.
Destination - Outbound traffic
In ReBid CDP, a destination is an external system where profile data will be sent if it is changed. A destination requires a specific resource, such as an API endpoint or a queue service, in order to receive and process the data.
In general, a destination is a place or system to which data is sent or forwarded for further processing or storage. It can be used to transfer data from one system or application to another, allowing for the integration and exchange of information between different platforms or services.
Identification point
An identification point is a feature that allows the system to identify customers during their journey. When this point is set, the system will monitor for events that can be used to match the anonymous customer's identified profile.
To give an analogy, think of an identification point like the ones at an airport or during a police check. You stay anonymous until there is a moment when you need to show your ID. This is an identification point. At this point, you are no longer anonymous. The same goes for ReBid CDP, once you identify yourself, all your past events become part of your identified profile.
For example, if a customer's profile in the system has an email address that matches the email delivered in a new event, then the system can match anonymous customer data with the existing profile and merge all previous interactions/events. In simpler terms, an identification point is a way for the system to identify customers and keep their information consistent throughout their journey.
Related Articles
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 ...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 ...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 ...What is Audiences?
An audience refers to a group of individuals who share common characteristics or behaviors based on the existing data collected within the platform. These characteristics could include demographics, interests, online behaviors, purchase history, and ...