Noteworthy Feature Releases – AudienceStream – October 2015

[dan_george]

AudienceDB (EPIC RELEASE)

This release alone requires exclusive documentation. Please see this post for more information. AudienceDB supplements EventDB, whereas EventDB stores event level information from your website, AudienceDB stores visitor level information about your visitors.

Attribute (UPDATE) - Details

Attribute details have been updated to show Dependent Rules in addition to Linked Enrichments. This transparency allows you to see which rules are using the currently viewed attribute. Note, while the Linked Enrichments subsection is always displayed, the Dependent Rules section is only shown when necessary.

These two sections (Dependent Rules and Linked Enrichments) help you see the domino effect of your change to help ensure that if an attribute is updated that you see everything else that will be affected.

Connector (Update) - Cooldown Grouping

Cooldown used to be a profile level setting, which meant that all actions had to adhere to the cooldown period instead of only selected actions.

For example, let's say there is a 30-day Cooldown period in affect and 2 actions in the profile. The first action is a marketing campaign for cart abandonment that should only be triggered once every 30 days, and was triggered 2 days ago. The second action is transactional and is triggered each time visitors request information about a product.

Previously, the transactional action would not be triggered for 28 days until the 30-day cooldown period for the profile expired.

Now with Cooldown Grouping you can create groups of actions with different cooldown periods. This allows marketing campaigns such as cart abandonment to comply with a 30-day cooldown, but transactional actions can continue to operate as normal without a cooldown.

Default (no cooldown)

Abandonment (30-day cooldown a.k.a 720 hours)

Connector (NEW) - Adform

Adform is a digital media advertising. You now have the ability to send visitor data to Adform.

This integration requires a cookie sync with Adform, Tealium can provide documentation. The integration also requires knowing the Tracking Setup ID and Tracking Point ID and are provided by Adform.

Connector (UPDATE ACTION) - Check Subscription Status in Bronto

The Bronto connector now has the ability to check whether or not a visitor is subscribed before sending the visitor update request to Bronto.

Connector (UPDATE ACTION) - Add to List in Bronto

We have also added the ability to add visitors to a list without impacting the membership of the visitor to other lists.

Connector (UPDATE ACTION) - Custom Endpoints in CheetahMail

In addition to the standard ebm.cheetahmail.com endpoint, the connector now supports custom endpoints for on-premise setups such as trig.t.client.com.

Connector (UPDATE ACTION) - List Support in ExactTarget

List attributes can now be mapped to the following actions: Data-extension - Add Record, Data-extension - Update Record, Send Email to User, Update Subscriber and Add to Email Lists(s). This makes campaigns easier to manage, such as product abandonment that send aggregate product information.

ExactTarget has an AMPScript method, BuildRowSetFromString({string},{delimiter}]), that can be used to turn a stringified List from AudienceStream into an object in ExactTarget. Here is ExactTarget's documentation on how this can be done.

Omnichannel (UPDATE) - 10 minute polling

Omnichannel was previously configured to import files only once an hour. The polling interval has been decreased to 10 minutes.

Omnichannel (UPDATE) - List Support

Omnichannel now supports uploading data to a List attribute. While Omnichannel normally "overwrites" an attribute value, with a List attribute Omnichannel will "append" each value. Each entry for the List needs to be in a new row. Here is an example CSV:

"customer_email", "upload_flag", "upload_trait_state", "upload_metric_year", "upload_list_city"

"user@tealium.com","true","CA","2015","San Diego"

"user@tealium.com","","","","Torrey Pines"

Rules (UPDATE) - Trait Contains Evaluator

Previously rules could only check to see if a Trait equaled a specific value. Rules have been updated so that when creating a rule that evaluates against a Trait, the Trait can be checked to see if it “contains” a value.