RudderStack’s flexibility in modeling caters to all your data needs seamlessly.
Profiles models your organizational data by analyzing all the data in your warehouse to create unified customer profiles and enrich them with features to help you scale your business efficiently and swiftly.
When you run the Profiles project, it creates an identity graph and user feature tables as outputs. You can augment the graph and create new user features by writing simple definitions in a configuration file or via SQL models.
Flexibility to use event stream, ETL, or any external tools as input sources.
Support to define various entities like user, product, organization, etc.
Intelligent merging of entities with different identifiers, like stitching Salesforce IDs.
Ease of creating features/traits for any entity and using them to deliver personalization.
Deal with advanced use-case scenarios using custom SQL queries.
Use varied input sources
RudderStack Profiles gives you the flexibility of using a variety of input sources. These sources are essentially the tables or views which you can create using:
Existing tables in the warehouse (generated by external tools like DBT).
Entities refer to an object for which you can create a profile. RudderStack allows you to use the desired object as an entity. For example, user, customer, product, or any other object that requires profiling.
You can define the entities in pb_project.yaml file and use them declaratively while describing the columns of your input sources.
Once you define the entities, you can resolve different identities for an entity using the process of identity stitching. It matches the different identifiers across multiple devices, digital touchpoints, and other data (like offline point-of-sale interactions) to build a comprehensive identity graph. The identity graph includes nodes (identifiers) and their relationships (edges), and it is generated as a transparent table in the warehouse.
For example, you can stitch Salesforce IDs or other ID types.
Enrich with features
Once you map all the available identifiers to an individual user or entity, it is easier to collect their traits and compute the user features you want in your customer 360 table.
Using the identity graph as a map, the Profiles feature table model lets you define or perform calculations over the customer data in your warehouse. A user feature table essentially creates a feature using entityVars. Each column in a feature table is a trait or user feature for a user or entity.
You don’t need any other tool or deep technical/SQL expertise to create these features. Trait defintion is in a single unified framework and there is no need to move data across silos.
cookies, the cookies that are categorized as necessary are stored on your browser as they are as
for the working of basic functionalities of the website. We also use third-party cookies that
analyze and understand how you use this website. These cookies will be stored in your browser
consent. You also have the option to opt-out of these cookies. But opting out of some of these
have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. This
category only includes cookies that ensures basic functionalities and security
features of the website. These cookies do not store any personal information.
learn more about cookies and why we use them, visit our cookie
policy. We'll assume you're ok with this, but you can opt-out if you wish Cookie Settings.