Application Launcher

Area	AgilOne JIRA	Description of functionality after the fix
Actions	AGO-8561	You can now refine the filters “Email Activity > Performed an event in a time period”, “Web Activity > Browsed a Product”, and “Web Activity > Abandoned their cart” by the following attributes : UserClient : this is “A” for events that happened on your mobile application (if you are sending us such events), and “B” for events that happened on a regular browser. Domain : this lists out the domain on which the specific event have happened, which can be useful for filtering the events if you use a lot of subdomains for marketing purposes or special sales and don’t want to target people that browsed on those websites. OperatingSystem : as its name indicates, this is a high-level summary of the operating system of the visitor. It can help you seleect specific segments of users based on their device/OS. DeviceType: as per its name, this is a very high-level summary of the device used by your visitors. It can help you segment further the people you want to target/avoid targeting for your campaigns, based on the device on which those events happened.
Data Export, Actions	AGO-8550	We now support encryption at rest of the data exported via our S3 connector. This applies to Data Export as well as any campaign using the S3 connector execution channel. Note that this encryption option is provided & executed on the Amazon S3 side (we don’t maintain keys and access on our end, we simply consume what is configured on S3). If you want to leverage this, please sync-up with your AgilOne team.
Data Export	AGO-8327	We found an issue where a recurring Data Export was not exporting the MasterCustomer entity. This was due to a timing issue, as well as an optimization on the modified date of each record in that entity. We fixed this, and all recurring Data Export will behave properly now.
Platform, Metrics, Actions, 360 Profiles	AGO-8258, AGO-8246	Unicode characters are now supported throughout our UIs and APIs. The underlying platform already supported those, so the only thing you need to make sure is that you are sending your feeds with a proper encoding (UTF-8 is strongly recommended) so that unicode characters are recognized and left untouched during our data processing.
Actions, SendGrid integration	AGO-8157	Some email contents & titles were incorrectly categorized as “spam” by our Spam Score functionality. This was due to a small glitch in the UI as well as some arbitrary stringent (provided by Spam Assassin) on the ratio of spaces to letters that made little sense to enforce. We reworked the rule and reviewed our Spam Scoring against the leading Email services (Litmus, Postmark, Spam Assassin, etc…) and confirmed that we are 100% aligned with them. THose issues are therefore fixed and you can use our Spam Score feature with confidence.

1717 Release - 2017-04-28