An eCommerce website uses Adobe Target Recommendations. The modules on the website consistently recommend popular products that are out of stock despite having a filter set correctly that excludes…

Question

Options

• AChange the product feed to use Analytics Classifications instead of the CSV product feed.
• BChange the product feed to use their Google Product feed data instead of the CSV product feed
• CCreate a Collection of items that regularly sell out quickly and apply this collection to the criteria of
• DSet the entity.inventory Target request (mbox) parameter value to the current live inventory value

• A
  5% (2)
• B
  3% (1)
• C
  10% (4)
• D
  83% (33)

Explanation

Option D is correct because passing the live inventory value directly as an entity.inventory mbox parameter on each page request updates Adobe Target in near real-time - bypassing the 24-hour lag of the CSV feed - so the exclusion filter immediately reflects the current stock level and can suppress zero-inventory products on the next recommendation call.

Why the distractors fail:

• A - Analytics Classifications are used to enrich reporting dimensions, not to feed real-time entity attributes into Target Recommendations; they don't solve the latency problem.
• B - Switching to a Google Product feed is still a batch/scheduled import; it improves nothing about real-time inventory accuracy.
• C - Creating a collection of fast-selling items only segments the catalog; it doesn't dynamically track inventory levels or prevent recommending out-of-stock products.

Memory tip: Think of entity parameters as "live data injected at the point of truth." The product page already knows the current inventory (it's in the data layer), so pushing that value into the mbox at page load makes Target Recommendations as current as the page itself - no feed schedule needed.

No community discussion yet for this question.