Sessions & People are containers which can contain more than one event. The difference represents those Sessions & People who also engaged with pages other than the LP. 998 sessions & 850 people engaged with the LP plus other pages on the site that aren't excluded.

Using data prep, you can nullify fields.

As far as I know, that isn't possible automatically.  You can use rolling dates for the reference period, but I can't think of a way that you could make that date range larger as more days roll by.

Hi @MartaSk1  Exit rate is typically used with the page dimension to determine how many visits exited from a particular page. Exit Rate = exits / visits. Exits are the count of times a dimension is captured as the last value in a visit. Assuming that the eVars I am considering are expiring after 1 h...

As I understand it, the cost of CJA is related to the total budgeted row count in Connections for CJA.  This includes event datasets and also lookups, profile, and summary datasets. Using the retention setting, you can determine how much historical data is retained. If there are events that aren't n...

In CJA, with graph based stitching, you can use multiple IDs to stitch together a single person, so it seems that should work.  There are some caveats, however.  Chief among them is it doesn't have full support for shared devices.  You can review more details in Adobe's stitching documentation - htt...

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 othe...

The two schemas will not work together.  Unless you map the data into the same fields, you'll have two sets of dimensions/metrics - one for each dataset.

If the data type is a string, you can't do math with it in CJA.  You can cast as an integer using data prep, but that's only for new data after you add that mapping. Alternatively, you can use Report Builder to get the numeric "string" into Excel.  There you can use it as a number.  Hope this helps!

Description - For all datasets, allow the ability to force lowercase all or certain fields. Why is this feature important to you - Currently, if the casing in matching keys doesn't match exactly, enhancement data from lookup and profile datasets isn't available in CJA. How would you like the featur...