An eCommerce client has Adobe Target correctly installed on their website. They have an auto-created global Target request (mbox) that runs early on in the page load but after the data layer has initialized. Many of the items in the data layer are applied to the auto-created global Target request (mbox). On product pages, the product ID is loaded into the data layer only after the Page Load DOM event has triggered.
The client needs to be able to send the product ID to Adobe Target when it has loaded and receive any experiences the user should see based on that product ID. They do not want duplicate experiences that have already been received by the auto-created global Target request (mbox).
According to best practices, what should the client do?
A. Set up a product feed to ingest the product data each day at midnight.
B. Create a second Target request (mbox) called 'product-data' including the product ID when available.
C. Create a second Target global mbox request including the product ID when available.
D. Delay the auto-created Target global mbox request until after the product ID has loaded into the data layer.
