Connections
3 min
Connection for B2B Data
Event, Person, and B2B datasets can be ingested in to a connection using matching keys or containers to join B2B data together. This can contain multiple rows for a single person identifier. Person-based lookups only match the most recent occurrence of that person identifier, preventing a proper person id based lookup of accounts, opportunities, marketing lists or campaigns.
Connections Demo
- The CJA B2B Connection will provide information on the datasets that are connected and how much data is flowing into th connection.
- A connection map will show how all the datasets are joined for what key is used to join the dataset.
- For each dataset you will select values for Key and Matching key. Below is the an event dataset that will have multiple keys and matching keys that can be configured for joining account, opportunity, buying groups, and/or person datasets.
- The Key is based on the Person ID data type.
- The Matching Key is defined as the primary identity field for the event dataset.
- For example you will see in the CJA B2B Account ID Lookup Dataset is matching to Account ID that is the same in the previous event dataset shown that will use Account ID in the event dataset.
- Another example you will see in the CJA B2B SKU Lookup Dataset is matching to SKU that is the same in the event dataset.
