How is it possible to display different SCENARIOS for customer segments in one website area with einstein web recommendations?

Question

How can I set up a web recommendation that has different SCENARIOS for different customer segments?

Specification (simplified): When I visit a website with one web recommendations area i would like to achieve that males get a different SCENARIO than females. For example males should receive "Top Sellers" while females should receive "Last View Merge".

When i would outline a solution (XY-Problem) i would like to have one recommendation page and a rule engine for the SCENARIO ORDER (not the rule engine to exclude or include products / content). Meaning the web recommendation has an own logic.

What i do not want: Create a logic in the onlineshop that decides which recommendation link it takes depending on the customer attribute like "sex".

Why? This would result in a strong bond between salesforce recommendations and the logic of the webshop. Switching the recommendation engine to other providers would be increasingly difficult when you make that strong hard coded connection.

I created an idea for that some month / years ago. Any clue how this is possible without logic in the webshop?

Ideas i created in that matter:

• Recommendation Scenario Order logic
• purely rule based scenario

Other Ideas that were added by me or that were posted on my demand:

• UniqueID not used everywhere
• Secure user details
• Rule priorization
• Permissions for personalization builder
• Disable Recommendation
• Idiotic implementation of salesforce - why displaying old column values?

Answer 1

Conceptually, you could do following:

1. come up with a hashed contact identifier, you can use in context of e.g. browser cookies
2. create a JSON code resource (In SFMC Cloud Pages), which takes this identifier as parameter (it should be passed via e.g. queryparameter), and returns appropriate pageid (mapped in an SFMC data extension), referring to recommendations configured (e.g. Home vs Home2 in example below):
3. code resource will be called in a java script, which first should check if we already have this pageid and contact identifier stored in a custom cookie, otherwise we pass the contact identifier to code resource, and store the response in a cookie (while setting an expiry date, ensuring we refresh the page id after X days)
4. you take the pageid provided, and merge it into the URL used to fetch recommendations, selecting dynamically which recommendation you want to use for this specific page visitor:

$('head').append('<script src="https://[MID].recs.igodigital.com/a/v2/[MID]/' + pageid + '/recommend.js" type="text/javascript"></script>');

In case Home2 is the right match for the visitor, you end up calling: https://[MID].recs.igodigital.com/a/v2/[MID]/home2/recommend.js