MaggieBrennan Adding to what jojo_zieff said and just to add more granularity, there are different ways you could go about storing and accessing your recommendations - but all of them will end up using liquid tags to populate the recommendation in the message:
- Build a catalog with recommendations based on different attributes - e.g. other content watched, food preferences, city, country, etc
- Use connected content to fetch your recommendations from an external database/system - e.g. google sheet working as catalog, recommendations engine, internal database/apis etc
- Use conditional logic within the message to run through the different options and logic
