- TLC Home Home
- Discussions Discussions
- Documentation Documentation
- Knowledge Base Knowledge Base
- Education Education
- Blog Blog
- Support Desk Support Desk
04-29-2016 07:44 PM - edited 05-05-2016 08:40 AM
A primary use case of Demandware leveraging AudienceStream data is to show 'personalized' offers to on-site visitors. While this could be executed by a pipelet API integration, it is better to use Demandware's "dynamic customer groups" feature and read a session variable populated thru data layer enrichment. This will allow you to group visitors in a way that Demandware can react and personalize data. In fact, this is actually preferred by Demandware because using dynamic customer groups is the only way to personalize content for anonymous visitors.
Here is one article that discusses dynamic customer groups:
And another 3rd-party article:
06-07-2016 02:46 PM - last edited on 06-07-2016 03:56 PM by kathleen_jo
The 3rd-party article by Joseph Greenwood brings up an excellent point about creating a master ID to create an association between a DW ID and a CRM ID for a consolidated view of the customer data. Storefront analytics from DW are pretty lightweight at the moment, but armed with additional feedback from CRM data I can see a nifty future ahead. Thanks for sharing @dan_george!
08-24-2017 09:58 AM - last edited on 08-24-2017 10:03 AM by kathleen_jo
Can you outline (or provide an example of/documention on) a method to link a dynamic customer group within Demandware to a UDO attribute?
08-24-2017 01:49 PM - last edited on 08-24-2017 04:45 PM by kathleen_jo
This would be done by setting Demandware's "Dynamic Customer Groups" to "is rule based" then you make the rule cookie based and use Tealium's Data Layer Enrichment to assign a cookie value. Here is some additional detail on Data Layer Enrichment (DLE): https://community.tealiumiq.com/t5/Universal-Data-Hub/Data-Layer-Enrichment/ta-p/684
Let us know if you have any follow-up questions.
Copyright All Rights Reserved © 2008-2023