Noteworthy Feature Releases – AudienceStream – March 2016

Tealium Employee

EventStream (New)

EventStream is new functionality that builds on top of Live Events (Filtered Streams) that provides the ability to trigger connector actions to send event-level data to vendors. Web events is to EventStream as visitor segments are to AudienceStream. Customer facing post coming soon, but talk to your Account Manager for immediate details.

Connector Marketplace (Update)

Tied to EvenStream, we're proud to announce a new way to explore connectors and actions. Our new marketplace gives you more insight into the power of AudienceStream's integrations with leading technologies across display, email, social and more. You can now filter available connectors by category, device type, and enrichment capability.

Connector – ExactTarget (Update)

With our Upsert Subscriber action, we did not have an option to update status due to a different API requiring this action. We have added a new section in the action just for the Subscriber Status to be updated.

Connector – ExactTarget (Update)

When selecting a business unit, often times the sub-configurations were not updated to reflect the configurations only specific to the Business Unit. Now, selecting a Business Unit pre-filters the other selections in the action to only show options specific to the Business Unit.

Connector – ExactTarget (Update)

If the same action within ExactTarget was replicated across Business Units with the same name, it became difficult to tell which action matched to which Business Unit within AudienceStream since it simply listed the action name. Therefore, we have updated the UI to list each action by name and include the Business Unit identifier in parenthesis.

Connector – ExactTarget (Update)

There was no logic within Audience to check if a user is opted in/out prior to AudienceStream passing over the user info. Tealium can now check subscriber status via API.

Connector – ExactTarget (Update)

When updating a record, AudienceStream did not know whether or not the record already existed so we did not know whether to "Add" or "Update" the record. We have added an "Upsert Record" that checks if the record exists using the ExactTarget native upsert for data-extensions API.

Connector – ExactTarget (Update)

We have added the ability to remove a user from a Data Extension Table via API.

Connector – ExactTarget (Update)

The ExactTarget data extension table default date/time column did not accept our Date attribute format of epoch. We have updated our connector to be able to support the native ExactTarget date requirement. We are actually checking the type of the field in ExactTarget and if it is a string we will stringify our date, and if it is a date we will convert and send it as a date.

Connector – ExactTarget (Update)

We have removed need for data columns to contain tealium_as in order to pull in the ExactTarget configurations into AudienceStream. We now simply pull all fields so that AudienceStream works will all previously created configurations.

Connector – SendGrid (New)

The purpose of SendGrid is "Delivering your transactional and marketing email through one reliable platform." Available API actions are: Add Recipient to List, Remove Recipient to List, Upsert Recipient, Remove Recipient, Send Transactional Template Email.

Connector – New Relic Browse (New)

Leverage the Tealium and New Relic integration in order to send event data from Tealium's Collect Library to New Relic Insights. New Relic combines business metrics, performance data, and customer behaviors in one lightning-fast event-store database. Available API Action: Send Browser Application Metrics. Used in conjunction with EventStream.

Connector – New Relic Mobile (New)

Leverage the Tealium and New Relic integration in order to send event data from Tealium's Collect Library to New Relic Insights. New Relic combines business metrics, performance data, and customer behaviors in one lightning-fast event-store database. Available API Action: Send Mobile Application Metrics. Used in conjunction with EventStream.

Connector – Kissmetrics (New)

Leverage the Tealium and Kissmetrics integration to track enriched Visitor Profiles and enriched Audience behavior from their first anonymous visit, through each conversion, to their lifetime value. Kissmetrics reports give you metrics to fully analyze and drastically improve your business. They give you the tools to fix your blind spots, maintain a 360-degree view, and strengthen your marketing impact through these 7 key reports. Available API actions are: Record Kissmetrics Event, Record Kissmetrics Event (Mobile Optimized). Used in conjunction with EventStream.

Connector – Google (Update)

The existing “Google Analytics for Web” connector has been deprecated and no longer works. It has been replaced with a new connector that allows EventStream Filtered Streams to trigger actions. Available API Actions: Send Analytics Event Data, Send Analytics Event Data (Mobile Optimized), Send Analytics Transaction Data, Send Analytics Transaction Data (Mobile Optimized), Send Analytics Social Data, Send Analytics Social Data (Mobile Optimized) Send Analytics Page View Data, Send Analytics Screen View Data (Mobile Optimized), Send Analytics Timing Data, Send Analytics Timing Data (Mobile Optimized). Used in conjunction with EventStream.

Connector – Adobe Analytics (Update)

The existing “SiteCatalyst for Web” connector has been deprecated and no longer works. It has been replaced with a new connector that allows EventStream Filtered Streams to trigger actions. Available API Actions: Post Data to Adobe Analytics, Post Data to Adobe Analytics (Mobile Optimized). Used in conjunction with EventStream.

Audiences (Update)

Can now be duplicated

Tealium Collect Tag (Update)

New feature to allow for separate enrichment polling setting values for multiple utag.view or utag.link calls.

Tealium Collect Tag (Update)

New configuration settings allow for defining Tealium Profile, Data Collection Region, and Sampling Percent.

Tealium Collect Tag (Update)

Additional "Performance Timing" metrics are being collected in regard to RUM (Real User Monitoring) data. This data can be used to understand a user's experience (i.e. the Browser's time to DOM Interactive state) for your site's pages. This data can be sent to EventStore or EventDB for analysis. The following data points are captured and added to the data layer:

  • "timing.domain" = The domain where the timing data was collected
  • "timing.pathname" = The path name (web page) where the timing data was collected
  • "timing.query_string" = The query string value in URL where the timing data was collected
  • "timing.timestamp" = The date/time when the timing data was collected (epoch time of client's web browser)
  • "timing.dns" = t.domainLookupEnd - t.domainLookupStart
  • "timing.connect" = t.connectEnd - t.connectStart
  • "timing.response" = t.responseEnd - t.responseStart
  • "timing.dom_loading_to_interactive" = t.domInteractive - t.domLoading
  • "timing.dom_interactive_to_complete" = t.domComplete - t.domInteractive
  • "timing.load" = t.loadEventEnd - t.loadEventStart
  • "timing.time_to_first_byte" = t.responseStart - t.connectEnd
  • "timing.front_end" = t.loadEventStart - t.responseEnd
  • "timing.fetch_to_response" = t.responseStart - t.fetchStart
  • "timing.fetch_to_complete" = t.domComplete - t.fetchStart
  • "timing.fetch_to_interactive" = t.domInteractive - t.fetchStart

References in regard to this kind of navigation timing:
A Practical Guide to the Navigation Timing API
HTML5 Navigation Timing