Understand the Data Graph — the entity mapping layer that connects your warehouse tables to the entities, relationships, and events used to create Audiences.
Available Plans
growth
enterprise
3 minute read
The Audiences feature is in Private Beta, where we work with early users and customers to test new features and get feedback before making them generally available.
Reach out to Customer Success if you are interested in enabling this feature for your workspace.
The Data Graph is an entity mapping layer that maps your warehouse tables to entities and events and defines the relationships between them. This gives marketers a business-friendly interface to build audiences from. Your data team configures it once, pointing at warehouse tables or your own pipelines, and marketers self-serve from there.
Core concepts
A data graph has three key components: entities, events, and relationships.
Term
Description
Entity
A warehouse table that represents a business object, for example, Customers, Accounts, or Products. Entities are the “nouns” marketers build audiences around.
Event
A warehouse table with a timestamp column that captures something that happened, for example, product_viewed, order_placed, or cart_abandoned. You can filter events with a time window in the Audience Builder.
Relationship
A 1:many, many:1, or 1:1 link between two entities, or between an entity and an event. Relationships let marketers filter one entity using conditions on related records, for example, “customers with 3 or more orders”.
Create a data graph
You can create a data graph in two ways:
Both methods produce the same data graph. Pick whichever best fits your team’s workflow.
1. Visual Builder
Configure the data graph directly in the RudderStack dashboard using an intuitive visual builder. Pick warehouse tables, mark them as entities or events, and draw relationships between them without leaving the app.
This approach is the fastest and easiest way to get started with the data graph.
Define your data graph as a YAML file and sync it to your workspace using the Rudder CLI. This is the right choice for teams that want to version-control the data graph in Git, review changes via pull requests, or manage multiple environments (dev, staging, prod) as code.
This site uses cookies to improve your experience while you navigate through the website. Out of
these
cookies, the cookies that are categorized as necessary are stored on your browser as they are as
essential
for the working of basic functionalities of the website. We also use third-party cookies that
help
us
analyze and understand how you use this website. These cookies will be stored in your browser
only
with
your
consent. You also have the option to opt-out of these cookies. But opting out of some of these
cookies
may
have an effect on your browsing experience.
Necessary
Always Enabled
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.
This site uses cookies to improve your experience. If you want to
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.