Interested if anyone has insight into this.....If a lookup table was ingested into CJA, would it still be able to feed the identity graph that is leveraged for graph-based stitching in CJA? Let's say I want to do a lookup on an appointment event, with the customer ID available on the appointment lookup record....can the ID available on that lookup record still be leveraged for g-b stitching? As in, that customer ID (given it's marked as a primary ID, dataset is marked for profile) can be stitched to the events with matching appointment keys?
Thanks for the information. Can lookup datasets be "marked for profile"? Is that a thing?
You may be able to mark the dataset as enabled for profile. That is set within AEP. Lookup and Profile dataset types refer to how those datasets are handled within CJA specifically.