best practice recommendation while creating a connection in CJA

Question

1) Technically its possible to create a connection and include all the dataset. And create dataView for each dataSet. But that may not be standard practice to determine the which dataset to be included in the connection. If we keep aside the privacy related aspect that which data we want to share with which stakeholder, are there any other factor that can influence how to strategically determine which dataset to be included in the connection ?

2) Are there any gotchas to know if we have same dataset included in multiple connections ?

3) Any limitation for the having same dataset covered into multiple dataViews ?

Josh__Stephens · Accepted Answer

There can be a variety of considerations depending upon your use cases. If you combine datasets in a connection, although you can filter out certain events at the data view level, it only filters out those specific rows. For example, let's say you have different brand sites. Persistence from other brands would carry over, even though those brand events may be excluded. Also, session starts and stops could be strange for events that are filtered out.

Having the datasets in separate connections would eliminate this. However, it also eliminates the ability to have visibility into all data together. You can't analyze datasets from different connections within the same data view.

It would be nice if Adobe had a way to solve for this so that filtered data views considered only the desired events.

John_Man · Answer

Hi @pradeep-jaiswal

I think it depends on your design whether to use a single or multiple connections. But one thing to consider is on license usage. As far as I know, CJA license depends on the number of processed records in all the connections. So the multiple connections approach may end up with a higher CJA license usage.

Thanks,

John

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded