How to Use a Calculated Insight from the Profile DG in Rule-Based Recommender

1. It must belong to a DMO that lives within the Profile Data Graph.
2. It must be a foreign key (FK) that points to the root primary key of the Item Data Graph.

Example Calculated Insight :

SELECT count(ssot__ProductBrowseEngagement__dlm.ssot__Id__c) as engagement_count__c, UnifiedIndividual__dlm.ssot__Id__c AS unified_individual__c, ssot__GoodsProduct__dlm.ssot__PrimaryProductCategory__c AS category__c , ssot__GoodsProduct__dlm.ssot__Id__c AS productId__c FROM ssot__ProductBrowseEngagement__dlm JOIN ssot__Individual__dlm ON ssot__ProductBrowseEngagement__dlm.ssot__IndividualId__c = ssot__Individual__dlm.ssot__Id__c JOIN IndividualIdentityLink__dlm ON ssot__Individual__dlm.ssot__Id__c = IndividualIdentityLink__dlm.SourceRecordId__c JOIN UnifiedIndividual__dlm ON IndividualIdentityLink__dlm.UnifiedRecordId__c = UnifiedIndividual__dlm.ssot__Id__c LEFT OUTER JOIN ssot__GoodsProduct__dlm ON ssot__ProductBrowseEngagement__dlm.ssot__ProductId__c = ssot__GoodsProduct__dlm.ssot__Id__c GROUP BY unified_individual__c, category__c, productId__c

Here, the dimension used in the CI is pulled directly from the Goods Product DMO i.e,  ssot__GoodsProduct__dlm.ssot__Id__c. 

It is not visible under the Profile Data Graph while configuring the rule-based recommender because:

1. ssot__GoodsProduct__dlm (GoodsProduct) is the root DMO of the Item Data Graph, not lives on the Profile Data Graph.
2. ssot__Id__c on GoodsProduct is the target of the relationship (the primary key), not a field that references it.

So, in order for this CI to appear under the Profile Data Graph while configuring the rule-based recommender, please update the CI by replacing:

ssot__GoodsProduct__dlm.ssot__Id__c AS productId__c with ssot__ProductBrowseEngagement__dlm.ssot__ProductId__c AS productId__c

ssot__ProductBrowseEngagement__dlm.ssot__ProductId__c is the correct field because:

1. It is a foreign key (ManyToOne) that references ssot__GoodsProduct__dlm.ssot__Id__c — making it a profile-side pointer to the product.

2. ssot__ProductBrowseEngagement__dlm is part of your Profile Data Graph, so it satisfies the Profile DG membership requirement.