Skip to main content
These steps apply to product cards you render yourself. Cards rendered by a legacy Depict UI SDK already carry these attributes.
We need to tell DPC about the product cards that you created using Depict data. Also, you need to enable Depict to understand what product this product card is in our internal representation. In the response from all our API:s there’s an id inside each display. You need to add this id to your product card template as a data attribute. The ID is called different things based on different endpoints
/v3/search/suggestions returns no displays, so there is nothing to tag for it.
This step enables DPC to track clicks on the product cards — including clicks on add-to-cart buttons inside them. Cards added later (for example after client-side navigation or infinite scroll) are picked up automatically.

Examples

One attribute per card, named after the endpoint the display came from (see the table above). The value is the id from that display.
Collection or category page (/v3/listings/*)
Recommendations (/v3/recommend/products)
Search results (/v3/search/*)