Skip to main content

Looking to get some ideas around using a dynamic content block using lookup AMPscript (or other recommended method). 

 

We have some longer lifespan journeys, and using journey data (which remains static after entry), doesn't work for some of our dynamic content or personalization strings. For example, if we have a cross sell product recommendation, and they purchase that product within the journey, I want to look at the updated cross sell recommendation for the next email, not what was at the start of the journey. 

 

We have done lookup AMPscript for personalization strings but not dynamic content blocks. We would like to get to a point to have re-usable content blocks that a content creator can pull in without editing the code. But for now, just looking to get recommendations around the best method to do this. 

 

#MCDeveloper 

#MCAskAnExpert 

1 Kommentar
  1. 9. März 2020, 14:12
    Assuming your cross sell recommendations are stored in a data extension that is constantly updated and includes a reference to the customer, I would set up a reference data extension set up that would include information about the cross sell products (name/image/URL, etc) to display and a key to reference them, like a SKU number. In the dynamic block, I would create a lookup to the cross sell recommendation DE using lookuprows() based on the subscriber reference between the 2 tables. Then take the SKUs you get from that lookup and populate your dynamic content block using lookups to the product info table based on SKU. Of course build in error handling in your AmpScript to hide the block if no results are found in any of the lookups.
0/9000