Q1 2015 Release Notes
Anonymous User Conversion
You can now covert anonymous user history collected with Horizon and include it in a known-user’s profile. Complete the user’s lifecycle picture from first click with this new “User API” feature. Learn more in our documentation.
Updated final campaign stats processing time to 7 days after send
Campaign Stats now process one final time, 7 days after the send completes. This allows the collection of the long-tail campaign activity that takes place in the 6-7 day range after send. This improves our previous automatic cap at 4 days after send time.
‘First Ten Clicks’ now included in the campaign query export
Campaign (blast) query exports now include a “first_ten_clicks_time” column, which corresponds to the existing “first_ten_clicks” column. This lists the first ten clicks in a campaign message for each user. See a full list of export columns here. You can access this report through our Campaign Detail Page or via the Jobs API.
Audience Builder (formerly known as Query Builder): Target users based on their last page view
You can now query a user based on when they last viewed a page on your site. Use the “last viewed” audience Builder criteria – complete with our full range of time options. Look for the new item in the Query Glossary.
Export from the ‘Purchase Log’ page
Our Purchase Log page now allows for exporting up to 31 days of history via CSV. Look for the “Download CSV” button in my.sailthru.com. Learn more in our documentation.
“Purchase Order” vars now displayed on User Lookup Page
The User Lookup Page now displays “order-level” vars for each user’s purchases, where present. These vars can be applied to orders sent to Sailthru via the Purchase API.
Purchases fully support use of ‘extid’
Purchase API calls now support GET/POST of “extid” values at the purchase order level. You must also use the associated “purchase_key” or “purchase_keys” parameter, respectively. This enables the ability to store a unique purchase string for each order and later locate (GET) that order using the same string. This release maintained the call in backward compatible state. See our updated Purchase API documentation here to understand how to use “purchase_id” and “purchase_key(s)”.
Links from campaign ‘includes’ now appear in clickmap reporting
Links within includes now display in the Campaign Detail Clickmap.
Notable Bug Patches:
- Both members of a Template A/B test will now have the same triggers copied to them if the original template had triggers attached. Previously “B” members would sometimes not receive the copied triggers.
- Revenue overlay for clickmap reporting within our Campaign Detail Report is active again.
- Template renaming and saving issues within my.sailthru.com are resolved.