When you join two or more objects in Insight Builder, the join nodes and join keys are
autopopulated based on their relationships in Data 360. A key join is a simple
way to join link tables. Autopopulated join nodes make it easy to connect engagement data with a
unified profile and override autosuggested joins.
When auto populating join keys in Data 360, keep these guidelines in
mind.
You get join up to three objects between the selected join data model objects (DMO).
If the relationship exists in Data 360, a one-to-one DMO relationship can
autopopulate join keys.
DMOs, such as a Unified Profile and engagement data, can auto-populate join keys.
A join between two unified profiles can’t be autopopulated.
If a join isn’t autopopulated, the original node is returned.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.