12-07-2015 08:47 PM - edited 12-08-2015 09:02 AM
Previously, users were only able to check if a date occurred more/less than a certain time period, or was greater/less than another attribute. This update is the ability to check whether or not the Date exists in the first place.
For example, I have a Date being imported from Omnichannel and want to compare that Date to the visit start Date using Metric enrichment “Set Difference Between Two Dates”. Before I do the enrichment, I want to check that the Date actually exists before I do the comparison. Now I can do so.
This update provides the ability to check if a “UDO variable“ data type or an AudienceStream “Trait” begins or ends with a specific string. This is useful for checking SKU Lists, Email Campaign IDs, and more.
Previously, when adding a lead to a list you could not use an email address as a Target Lead ID. You could only use the Lead ID that is associated with the user that exists in the Marketo list. We have updated to add a lookup that can associate a Lead ID with an email address.
Google continuously updates APIs and sunsets previous versions over time. We completed the required updates to support the latest version.
Facebook continuously updates APIs and sunsets previous versions over time. We completed the required updates to support the latest version.
When passing Date attributes to Salesforce, if the attribute was empty/unassigned Salesforce would reject the addition of the record. We have updated the connector to proceed with sending the record even though the Date attribute does not exist.
The connector was able to insert or update user information in a contact table, however there were only a limited number of fields available in the contact table. This new action allows for use of up to 250 fields of data and can be synced to the contact to allow for advanced use cases such as Cart Abandonment that may require dozens of pieces of data for a visitor.
We have changed the default behavior of the AudienceDirect connector to pass attribute IDs instead of attribute Names. If you still need to pass attribute Names, check the checkbox “Print Attribute Names” in the action as seen below.
Previously we were mapping the SiteCatalyst Visitor ID as “VID” which was not being received by SiteCatalyst. Changing to “vid” resolved the data capture issue.
Previously, Audiences could not make use of OR conditions and had a limited set of conditions and attribute evaluations available. We have updated Audiences to use the same engine as Rules so that all attribute evaluations can be used such as “Trait contains” and “OR” conditions. This only applies to newly created Audiences, existing Audiences will have to be recreated to take advantage of the new functionality.
Previously, Audience Discovery filtering was very limited and not flexible enough for truly drilling into data. This made it difficult to use this feature to its true potential. We have updated Audience Discovery to use the same engine as Rules and Audiences to improve the use of Audience Discovery as a real-time audience viewer. To access the filtering that previously existed in the left panel, click the “+” icon next to the Audiences drop-down.