Data Cloud

Question

Title: Data Cloud - Shopping Cart Product Engagement (SSPC) object not returning records Hi everyone, I'm facing an issue in Salesforce Data Cloud related to Marketing Cloud Next abandoned shopping cart data. Issue: The Shopping Cart Engagement (SSC) object is returning records correctly. However, the Shopping Cart Product Engagement (SSPC) object is not returning any records. What I've verified: The abandoned shopping cart event is configured and triggered successfully. SSC records are being created in Data Cloud. SSPC object exists, but it contains 0 records . The repeater works with SSC, but I need product-level data from SSPC. My questions are: Under what conditions are SSPC records created? Does SSPC require any additional configuration or mapping beyond SSC? Are there any known prerequisites for populating the Shopping Cart Product Engagement object? Has anyone experienced SSC receiving records while SSPC remains empty? Any guidance or troubleshooting suggestions would be greatly appreciated. Thank you!

K Mahesh · Accepted Answer

Hi Hemanth,

This is a common one, and the symptom you're describing — SSC populating while SSPC stays at zero — almost always points to mapping rather than the event itself. Since your SSC records are landing, the event is firing fine.

The key thing: cart and order engagement events don't get their own data streams. They're consolidated into a single Behavioral Events stream, and the DLO that gets auto-created has to be mapped to each target DMO separately. So on the DMO side of the mapping canvas you need Shopping Cart Product Engagement added as its own target, alongside Shopping Cart Engagement. If only SSC was added, SSC fills and SSPC stays empty — exactly what you're seeing.

Four things worth checking, in order:

1. Primary key. eventId has to be mapped to the primary key of every DMO, not just the first one. For SSPC that's ssot__Id__c. If it's unmapped, nothing lands — and as a side effect your Data Transform will run full instead of incremental, which also costs more.

2. The relationship back to the cart. SSPC is Many-to-One to Shopping Cart Engagement via ssot__ShoppingCartEngagementId__c. If that's not mapped, the line items have nothing to attach to.

3. Product-level fields in the payload. SSPC expects ssot__ProductId__c, and usually ssot__ProductSKUnumber__c, ssot__ProductQuantity__c and ssot__ProductPrice__c. Worth confirming your cart event is actually sending a line-item array and not just cart-level totals — if the products array isn't in the payload, there's nothing to map.

4. Validate the mappings. Setup → Marketing Features → Triggers management page checks whether your DMO mappings are configured correctly and surfaces errors. Clear everything there before troubleshooting further, then let the transform re-run.

To your questions directly:

SSPC records are created when the behavioral event carries product line-item data and the DLO is mapped to the SSPC DMO with both the primary key and the cart reference mapped. Yes, it needs configuration beyond SSC — same data stream, separate DMO mapping. And yes, SSC-populated-but-SSPC-empty is a very typical outcome of mapping only the cart-level DMO.

Hope that helps — let me know what the Triggers page shows.

K Mahesh · Answer

Thanks Hemanth — that helps. If the Triggers page is clean and the transform is running, then the mapping side is probably fine and the issue has moved upstream to the payload. Two things to check, in this order.    First, confirm SSPC is actually a target on the mapping canvas. Open the Behavioral Events data stream, go to the mapping view, and look at the DMO side — not the field list, the list of target DMOs. Shopping Cart Engagement and Shopping Cart Product Engagement should both be there as separate entries. A clean Triggers page can still coexist with SSPC simply not being added, because there's no error in a mapping that doesn't exist. If it's missing, add it, map ssot__Id__c from eventId and ssot__ShoppingCartEngagementId__c from the cart identifier, and re-run.    Second — and this is where I'd put my money if SSPC is already on the canvas — look at the raw event, not the mapping. In Data Explorer, query the DLO behind the Behavioral Events stream and inspect an actual abandoned cart record. What you want to know is whether the payload contains a nested array of line items, something like products or items with productId, quantity and price inside each element. If the event is only carrying cart-level fields — cart ID, total value, currency, timestamp — then SSPC has nothing to build rows from, and no amount of mapping will populate it. SSC works precisely because cart-level data is all it needs.    That's the most common version of this once mappings check out. The event gets configured with the cart summary and the line-item array either isn't included in the schema or isn't being sent by whatever fires the event.    If it turns out the array is missing, the fix is on the ingestion side rather than in Data Cloud — the event schema needs the nested product structure, and the source has to populate it. Worth checking with whoever configured the cart event on the commerce side.    If the array is there and SSPC is mapped and the Triggers page is clean, tell me and I'll think again — at that point it's worth a case, because that combination shouldn't produce zero rows.

Data Cloud - Shopping Cart Product Engagement (SSPC) object not returning records

관련 학습

도움 더 받기