- TLC Home Home
- Discussions Discussions
- Documentation Documentation
- Knowledge Base Knowledge Base
- Education Education
- Blog Blog
- Support Desk Support Desk
If a List contains {ABC123, ABC456, XYZ789} you can now check if the List contains ABC instead of explicitly checking ABC123 and ABC456.
Users already have enrichments that give the ability to remove a Badge, set a Flag to “false”, and expire Timeline entries. Users now have enrichments to delete the following attributes: Date, Trait, List, Tally, Tally Entry. They essentially reset the attribute.
Tally's can be stored in a Timeline so they can be aggregated on later visits. This enrichment will aggregate each Tally in the Timeline and return the value of the favorite.
As an example, imagine you have a Tally that stores product categories, and that Tally is captured in a Timeline at the end of every visit. You can already use the Tally enrichment "Set Rolling Sum based on Timeline" which will subsequently output a Trait naming the favorite product category (e.g. shoes). You can now use this Metric enrichment that will allow you to capture that favorite product category count (e.g. 10).
Changing the scope of an attribute has many links within the system from the aspect of enrichments, audiences, and actions. It becomes too subjective for AudienceStream to determine the correct action for handling this change; therefore this functionality has been removed.
If your visitor was stitched in the middle of the Trace, you were not able to force the end of session by clicking “Stop Trace.” This has been resolved.
This request is for an integration with Mailchimp, called “Ecommerce 360”. The API contains some handy Ecommerce related methods for attaching order details to your list members. That data can then be used for segmentation when campaigns are sent. More information can be found here: https://apidocs.mailchimp.com/api/how-to/ecommerce.php
https://apidocs.mailchimp.com/api/2.0/ecomm/order-add.php
When leveraging the "Add to Email List" action, it will fail if the subscriber does not exist. This new action checks if the subscriber exists and if so adds them to the email list, otherwise if the subscriber does not exist they will be inserted as a new subscriber and then add them to the email list.
You now have the ability to send AudienceStream data to your Google Universal Analytics reporting suite. There are several requirements to make this work so please reach out to your Account or Deployment Manager for more details and they will loop in an AudienceStream Engineer for guidance. Please be aware that this may effect demographic reporting heavily.
You now have the ability to send AudienceStream data to your Adobe Analytics reporting suite. There are several requirements to make this work so please reach out to your Account or Deployment Manager for more details and they will loop in an AudienceStream Engineer for guidance.
Previously when Omnichannel data was imported into AudienceStream, if the visitor did not have a profile within AudienceStream (was not active in the last 90 days) then the visitor data would not be imported. Visitor Onboarding improves this by creating a visitor profile for inactive visitors on the fly and saving that data. Therefore, in the future when the visitor comes to the site we will already have information on the visitor that can be stitched to the online visitor profile.
Copyright All Rights Reserved © 2008-2023