Actions

AGO-11529

For clients that push AgilOne Actions Campaigns to CheetahMail, we have squashed a bug that was resulting in some data not being successfully pushed to a CheetahMail xDB.

Actions

AGO-11502, AGO-11503, AGO-11624

We have significantly overhauled the user interface of the AgilOne Actions choose channel screen to better visualize the options available to the user. Previously if you were trying to push data to a third party (e.g. Monetate), you had to know which data transfer medium they used (e. g. SFTP). Now instead of memorizing ‘Monetate uses SFTP’ and then clicking on ‘SFTP’, you can just click on ‘Monetate’.

Actions

AGO-11604

Some clients experienced Actions campaign failures due to removing content models from a previously executed campaign. Due to the backend data structure, after the first execution of a campaign, output content can only be added, not removed. Therefore we have blocked Actions users from being able to remove content models after the first execution of a campaign. If you would like to remove a content model please clone the campaign and then edit the clone.

Calendar

AGO-11065

We are releasing a new application called the AgilOne “Execution Calendar”. This application displays when campaigns, reports (not including Looks), and data exports are scheduled to be executed in the future. It currently does not display any past execution history. This application will be made available to all users who have access to either Actions, Metrics, or Data Export. The calendar should be extremely helpful for keeping track of which campaigns, reports, and exports are scheduled to execute in the future.

Actions

AGO-11434

Before this release Actions users were limited to inputting a maximum of 50 values into a single filter. With this release we are significantly increasing that limit to 2,500. We hope to slowly increase this limit to 9,999 at which point we reach a new barrier enforced by one of our underlying technologies. If you have a use case where you would like to input more than 2,500 values into a single filter, please reach out to your Customer Success Manager so that we can thoroughly test and validate the functionality before we release it widely. Thank you!

Platform: A1 Mailer

AGO-11376

For clients who send emails through AgilOne’s SendGrid integration, AgilOne now receives details, in real time, about which device type (e. g. computer, tablet, or mobile phone) was used to open or click within the email. This will be especially helpful for reporting on which devices are used to open and click on emails.

Platform

AGO-10549, AGO-10558

We have enhanced the platform so that display names in Actions and 360 re more easily configurable. Please reach out to your Customer Success Manager or Implementation Consultant if you would like to change some of the default language in Actions or 360. For example, you may want to change “transaction” to “order” or “purchase”.

Actions

AGO-11363

While previously AgilOne did not enforce any consistency with regard to the order of columns in Actions output content, we have found that the recent introduction of the ‘Echo’ content model has upset some of our client’s downstream integrations. In this release we have introduced an update that maintains the order of Actions content columns across saves and executions of an Actions campaign. The order of Actions output columns can still change when a campaign is cloned (i.e. copied). If you rely on the order of columns that Actions outputs, we recommend that if you need to add new content to a previously executed campaign, that you clone the campaign first before adding the new content. Thank you!

Actions

AGO-11188

In Actions, you can now filter date/time based attributes by a relative number of weeks. E.g. Find all customers who purchased a product in the last 3 weeks. Previously you could only filter by days, hours, and minutes. As always, the time frame utilized to filter the audience is calculated at time of execution. In the previous example, if the campaign runs at 8am, the audience will be filtered to include anyone who purchased a product since three weeks ago at 8am (i.e. today at 8am minus 3 weeks * 7 days/week * 24 hours/day * 60 minutes/hour * 60 seconds/minutes).

Platform: DW Tracker API

AGO-11353

We have enhanced our DW Tracker API so that it can ingest all email events in real time. This should enable additional real time use cases around email engagement, should your Email Service Provider support informing AgilOne of email sends, opens, and clicks in real time.

Actions

AGO-10881

In 1833 we are releasing two new Actions content models. The first of which is ‘Household Attributes’. This content model allows you to export household-level details for each customer in an Actions audience. This content will be especially useful for clients that mail catalogs or other direct mail marketing pieces. Now you can use Actions to export such details as household total revenue segment or household acquisition offer. Please reach out to your Customer Success Manager or the AgilOne help desk to enable this feature.

Actions

AGO-11215

We are always working to make Actions campaigns perform more efficiently. In this release we have added two features to enhance performance. The first of which is a campaign optimizer that reviews campaign construction before execution and works to minimize the complexity of the campaign logic. This performance improvement occurs behind the scenes to the user, but should significantly improve the performance of campaigns with a large number of filters and/or content.

Actions

AGO-11280

We have squashed a bug that broke the functionality of the following audience filters:

• Purchased a Number of Products

• Made a Number of Transactions in a Timeframe

These filters should now work as expected. Please work with Support to recreate any campaigns that were created over the last two weeks with these audience filters.

Platform: CheetahMail

AGO-11116

For our clients that use CheetahMail, AgilOne can now send audience lists from Actions campaigns to CheetahMail external databases (xDBs). xDBs are campaign ready audience lists and metadata that exist outside of CheetahMail’s main subscriber table and can be used within 14 days as a reference for sending a campaign from CheetahMail. If you are interested, please speak with your Customer Success Manager about how to set up such functionality.

Platform: Silverpop

AGO-11150

For our clients that use IBM Silverpop, we have updated our data ingestion process to map and store the Silverpop event types. Previously AgilOne just standardized the Silverpop event types by translating them into AgilOne’s event types (e.g. ‘hard bounce’ -> ‘emailBounce’). In addition to the previous behavior, Silverpop event types are now available in AgilOne as event ‘subtype’. This will help AgilOne report on hard vs. soft bounce counts and make interaction with AgilOne more familiar for users migrating from Silverpop’s segmentation & reporting user interface to AgilOne’s.

Actions

AGO-11119

We have created two new Actions audience filters:

• Performed an event with a campaign - allows an Actions user to segment an audience by any behavior linked to a marketing campaign. Previously only message-level metadata was available for refinement, now campaign and dispatch level metadata is available for refinement.

• Performed an event with a product category - allows an Actions user to segment an audience by any behavior linked to a product category, such as product category browse or like events.

Actions

AGO-11107

When we added the ability to analyze and segment by Propensity to Buy 3 months ago and 2 months ago, we mistakenly removed Propensity to Buy 1 month ago. Therefore, we have now made available ‘Propensity to Buy 1 Month Ago’ in Actions as both a filter, refinement, and content.

Platform

AGO-11088

To support AGO-11120 we have added two new customer summary attributes:

• Closest Store ID

• Primary Store ID

While Primary Store ID is available out of the box for existing clients, Closest Store ID requires that AgilOne reset an incremental cache within our data processing pipeline. Resetting this cache could cause the subsequent nightly refresh to run longer than normal and thereby impact morning campaigns. Therefore, this effort will be performed on an ‘as needed’ basis. If you would like to utilitze Closest Store ID, please reach out to the AgilOne help desk or your Customer Success Manager to schedule an appropriate time to reset this cache, causing a slightly delayed refresh, but resulting in a Closest Store ID being properly calculated and exposed. Thank you!

Actions

AGO-10824

For clients whose customers have favorite products that they buy multiple times (e.g. single-use items, food, etc.), we have built a new content model that exports each customer’s favorite products from Actions. This “favorite products” content model calculates and exports product details for each individual’s favorite 6 products. A ‘favorite product’ is a product that the customer has purchased more than five times and in greater quantity than any other product (we rank by highest quantity purchased). If an individual has purchased two products in the same quantity, the content model breaks ties by then ranking by sale revenue. This insures that higher value products will win over lower value products when purchased in similar quantities.

Actions

AGO-10999

As part of our continued efforts to make refining by product categories within Actions easier, we updated several Actions audience filters to include refinements on products, product categories, and the product category hierarchy. The product category hierarchy means that you no longer have to explicitly list every product category you would like to refine by. Where previously an Actions user who wanted to refine by Men’s products needed to include in the refinement: ‘Men’s tops knit’, ‘Men’s bottoms jeans’, ‘Men’s socks’, etc., now you need only to enter ‘Men’s’ and Actions will automatically traverse the product category hierarchy to grab and include every descendant category. The audience filters affected are:

• Placed first transaction

• Placed last transaction

• Customers who spent certain amount in a timeframe

• Made a Number of Transactions in a Timeframe

• Purchased a Number of Products

While this effort makes including descendent categories significantly easier than before (you now only need to select one parent instead of all descendants), it does slightly complicate excluding descendent categories. To exclude a product category, please exclude the category on “product category hierarchy” instead of “product category”. If you exclude product categories on product category, then Actions will still traverse down the product category tree from a different parent (or grand parent) to grab the descendant category. Today’s behavior is now reversed from before, where excluding a single category does not exclude its descendant categories. You have to explicitly list every descendant category that you want to exclude. In summary, include categories using “”product category”” and exclude categories using “”product category hierarchy””. We hope to visualize the product category tree in the future so that including and excluding product categories is less confusing and easier to accomplish.

Actions

AGO-10584

We squashed a bug that prevented users from exporting correctly formatted dates before January 1st, 1970, the start of Unix time. Dates before January 1st, 1970 were incorrectly exported as Unix epoch time stamps instead of human readable dates.

Platform

AGO-10839

Recently some clients who have householding logic enabled have noticed that some transactions are improperly marked as anonymous transactions instead of being properly assigned a master customer. This has been rectified so that all transaction records are properly assigned the correct master customer. If you do not have houeholding logic enabled, then you were not susceptible to this issue.

Actions

AGO-10927

Continuing our effort to make the AgilOne application more self documenting and user friendly, we have added many new information buttons (i) throughout the Actions campaign workflow. In the future we hope to add more documentation within Metrics and 360 as well! Please email product@agilone.com if you ever spot any out of date documentation.

360

AGO-10857

We are continuously making 360 Profiles more configurable. If you prefer, you can now hide all timezones displayed within 360.

Platform

AGO-10884

Recently our Bronto output connector has been failing when the source dataset has empty (i.e. null) fields. We have fixed our output connector so that it no longer fails when attempting to export null data.

Actions

AGO-1054

To more easily enable recurring birthday campaigns AgilOne has developed a new Actions audience filter: ‘Days Until Next Birthday’. You can utilize the ‘Days Until Next Birthday’ filter to segment an audience based on whether their birthday is approaching or recently occurred.

Actions

AGO-10710

Removing content from an Actions campaign after it has already been executed once can cause future executions to fail. Therefore we are now disabiling the ability to remove content after a campaign has already been executed. You can still add new content for future executions. If you would like to delete existing content, please clone the campaign, and edit the new copy of the campaign.

Actions

AGO-10828

In order to make the AgilOne application more self-documenting we have added many more information buttons within Actions. These buttons (designated by an ‘(i)’ icon) will either provide more details right in the application or link out to our thorough documentation portal in Zendesk. We hope to improve the quality of this documentation and add more documentation within the application going forward.

GDPR

AGO-10924

We have greatly improved the performance of our GDPR purge process to handle significantly larger customer lists (>250,000 customers at once). After testing our privacy API with some early adopters we found that many of our EU clients are more eager to purge ‘no longer relevant’ customers than we expeted. To accomodate these requests we have iterated upon and improved our GDPR purge workflow to handle very large customer lists.

Metrics: Cube Reports, Template Reports

AGO-10686

Empty/null values in the result grid of a report were being defaulted to “0” when charted. This was giving rise to some unexpected charting behavior. We’ve fixed it so that empty/null values are not charted in a data series instead of defaulting them to “0”.

Metrics: Cube Reports, Template Reports

AGO-9792

Fixed various bugs related to “Stacked Column” charts. This chart type should now work as expected in various scenarios in Reports.

Platform

AGO-1052

AgilOne’s default data promotion policy is ‘latest is greatest’, in other words the most recent data received is the most up to date. However, in some instances this paradigm breaks down: for example, the latest data can contain conflicting information, or higher quality and more thorough data may exist from an earlier source. Therefore, AgilOne has highly complex and advanced logic to decide which email address, mailling address, phone number, and some key customer attributes (e.g. first name, last name, gender, age, etc.) are promoted from the source data to the master customer in AgilOne. We have now made it easier for our clients to customize this logic based on their specific needs. Please speak with your Customer Succcess Manager if you would like to adjust how AgilOne chooses the winning name & gender, address, email, and phone number for each master customer. Sometimes the default promotion logic can be enhanced just by discussing which sources are highly reliable, and which sources are not.

Actions

AGO-9078

In Actions we are now exposing the recently created phone validity flags for primary, secondary, and mobile phones within the United States and Canada. For clients that exclusively do business in the US and Canada you can utilize these flags to understand whether a customer’s phone number is valid or invalid and perform text marketing phone calls appropriately.

Metrics: Cube Reports

AGO-10863

We experienced a bug where the “Connect from Excel” button was not downloading an Excel file as expected. We’ve fixed it as part of the release.

Platform

AGO-10576

AgilOne has made it easier to configure changes to the many default buckets, or ranges, that are grouped in AgilOne’s nightly refresh process. For example, the default buckets for days since last transaction are: ‘Less than 1 month’, ‘1 to 3 months’, ‘4 to 6 months’, ‘7 to 12 months’, ‘13 to 24 months’, and ‘More than 24 months’. Configuring this bucket to be unique for a client’s specific needs was achieveable before, but is now much easier to accomplish. Any attribute that ends with ‘group’ is performing bucketing that should be configurable.

360 Profiles

AGO-10593

The 360 household tab now displays more than three family members when necessary. Householding logic can be quite complex and therefore is not exposed by default. If you do not see a household tab in your 360 profiles, and would like to explore the benefits of householding, please speak with your Customer Success Manager for more information.

GDPR

AGO-10475

To further enhance our GDPR purge process, we have updated the process to also delete or anonymize personal data in our purge tracking tables after the purge process succeeds. This is because the primary identifier of a customer, that we write to these purge tracking tables, often contains personal data that must be purged or anonymized under GDPR rules.

360 Profiles, Real-Time Events

AGO-10483

The SourceProductNumber field in the Journey tab of 360 Profiles was not being populated for real-time events such as productBrowsed. We’ve fixed that to display the SourceProductNumbers.

Actions

AGO-10381

In Actions we have found that it can get confusing which refinement filters are being used when the same attribute applies to multiple entities, most commonly ‘transaction type’, ‘product type’, and ‘organization type’. Therefore, we have added the name of the entity to all refinement filters, so that if you see the filter ‘type’ you will know if it refers to a transaction, a product, or an organization.

Actions

AGO-10444, AGO-10476

We have added the ability to select multiple calculated content models in a single Actions campaign. In Actions content there exists a distinction between content that is 1:1 customer to content, vs. content that is 1:many customer to content. Only one content model that explodes the result set, that is 1:many, can be added per campaign. Since calculated content models are only 1:1, and do not explode the result set, we are now allowing the user to add multiple calculated content models to a single campaign.

Metrics: Cube Reports

AGO-10378

The “Chart Settings” button in Cube Reports was incorrectly showing a ” +” icon. We have now fixed it to correctly show a “gear” icon.

Metrics: Cube Reports, Template Reports

AGO-10357

Reworked the UI for the “Chart Settings” dialog in Cube and Template Reports. The dialog should now be more intuitive, and minimizes the amount of user input needed for creating a chart. The dialog also collects all customizable options for the chart under the “Customize” tab.

Metrics: Cube Reports, Template Reports

AGO-10457

Chart axes and value labels will now have number formatting that can be set by the user. We’ve also introduced a setting for min/max axes bounds.

Metrics, Cube Reports

AGO-9955

When removing a measure from a report that had run, a bug caused that measure to still be displayed in the next run of the report. This has been fixed and is working as expected now.

Metrics, Cube Reports

AGO-10356

A bug in the filtering functionality was causing the hierarchical dimensions(e.g. Organization Type) to have no filter applied. This has been fixed and everything is back to the expected behavior.

Actions

AGO-9864

We removed the filter “Was sent and email with name” because it was confusing, and duplicated uselessly the filter “Performed an event [emailSend] where message name is”.

Actions

AGO-10470, AGO-10236

We received a lot of requests to enable filtering on the content you are sending via our Actions campaigns, and we have heard you. We are releasing the ability to filter the content (in the “Content” step of Actions) sent in your campaigns : for instance, if you only want to send the last browsed products that were in the category “Red Shoes”, simply select the “last browsed products” content model, the product attributes you want to send, then click on the “+” to refine the content and build the criteria “where product categories equals to [Red Shoes]”. All recipients will then receive their last browsed products, as long as those products are in the “Red Shoes” category.

Actions

AGO-10363

Similar to the above, we also released a new calculated Content Model to be able to export a static value (that you can configure) for all contacts in the campaign. This is especially helpful for cases where you want to send the same content to all recipients of your campaign(e.g. discount code, gift card, etc…). Please reach out to your AgilOne team to get this Content Model for your tenant.

Actions

AGO-8481

We added the ability to select dates in the future for all your Actions Audience criteria. This is a new “operator”, similar to “in the last [number of days]” or “before [a certain date]” : we added 2 operators called “in the next [number of days]” and “in the future range [defined y 2 dates]”. You can use it for any date/time data element currently existing in Actions, as well as any data element configured for your tenant (as long as it is a date/time element). This now allows you to send reminder campaigns for all customers who have a subscription about to end, an appointment or event coming up that they should remember, loyalty points about to expire, etc…

360 Profiles

AGO-10322

In 360 Profiles, certain product URLs displayed were not redirecting correctly to your product pages. This has been fixed, so you can now click on those links when reviewing a customer profile’s transactions to be directed to the product he bought.

360 Profiles

AGO-10264

360 Profiles stopped displaying the “donut” charts on the Overivew page of any profiles, supposed to show the transaction organization distribution and the event type distribution. This was due to a bug in the 3rd party component we were using to render those, so we downgraded it to a working version for now, and everything is back to normal.

Metrics, Dashboards

AGO-10087

A minor UI issue was causing the titles of certain charts to have a “dropped shadow” effect, making them unreadable. This is now fixed.

Actions

AGO-10221, AGO-10222, AGO-10089, AGO-9903

Small UI improvements : small typo fixes, removing the “customersummary” refinements (no need to refine customers since the audience rules are already filtering customers) and removing the “refinement” button when not applicable.

Actions

AGO-10102, AGO-10103, AGO-10291

We released a general overhaul of the Actions UI (functionalities are the same), to make it simpler to find what you are looking for. This update changed both the campaign listing page (you can now toggle between the list view and the card view based on your preferences), and the rules and refinements selection pop-up (the categories are now on the left, while the list of rules/refinements under each category is represented as a list of cards on the right).

Platform, 360 Profiles, Actions, SendGrid integration, SFTP integration

AGO-9599, AGO-9743, AGO-9835, AGO-9839, AGO-9841, AGO-9843, AGO-9850, AGO-9851, AGO-9889, AGO-9935, AGO-9873, AGO-9762, AGO-9732, AGO-9628, AGO-9918, AGO-9596, AGO-9600, AGO-9731, AGO-9602, AGO-9870, AGO-9603, AGO-9745, AGO-9598, AGO-9601, AGO-9888, AGO-10196, AGO-10169, AGO-9994, AGO-9957, AGO-9947, AGO-9745, AGO-9731

AgilOne now supports for real-time data flows. As you already know, the webtag data (and any data sent to the underlying Tracker API) gets to our system in real-time. We now added the following functionality (requires a setup for each tenant, please check with your CSM) :

• 360 Profiles and 360 API : any event or transaction that happens for a known customer will now be displayed/served in real-time by 360 Profiles/360 API. The application will automatically update itself to show those events/transactions as they come under that customer’s profile in 360 Profile.

• Actions campaigns with SendGrid or SFTP integration : with a small additional setup, certain campaigns in Actions (based on events or transactions) can now be executed as frequently as every 15 minutes. This is interesting in particular for near-real-time campaigns like Abandoned Cart or Follow-up after purchase, etc… Note that this is available only with SendGrid or SFTP execution channels because other channels do not guarantee the immediate loading of the data we would send to them (SLAs are usually around the hour), defeating the purpose of this new capability.

• Important note : this capability only supports “pass-through” data with very minimal processing (to be as fast as possible). Processing like DQE (deduping, validation, etc..) and computations like “lifetime value” (and any other KPI/metric, including ML models) will not happen as part of this “real-time” flow. They will be executed as usual, during the next regular data flow. In particular, this means that any customer, product, address and message not already processed (e.g. new customers) by AgilOne in the previous batch cannot be displayed/served in real-time.

Platform, Reports

AGO-9744, AGO-9786, AGO-9855, AGO-9780, AGO-10071, AGO-10057, AGO-10056, AGO-9973, AGO-9959, AGO-9944

Launched a new feature for running Interactive SQL Queries that provide direct SQL access to AgilOne’s processed data. The feature is currently in EAP (Early Adopter Program) and slated for a wider release during Q1 2018. Please reach out to your AgilOne CSM to provision the feature for your tenant.

Platform, Data Export

AGO-10051

In certain corner cases, certain events were missing from the Data Export. This was due to a mismatch between the timestamp used for the incremental Data Export and the timestamp populated by the events (again, only in very specific cases where the standard feeds were being processed while some new events were added and the Data Export had not fully run yet). We changed the incremental data export logic to export all records updated since (last successful data export - 24 hours). It will therefore likely contain an overlap in data, but ensure no records are missed during the export.

Metrics, Reports

AGO-9992, AGO-9763

Various fixes on the report email delivery

Metrics, Dashboards

AGO-9790

Dashboards now resize properly when you resize the window (or change the screen resolution).

Actions

AGO-10122, AGO-10068, AGO-10030

We updated our Audience rules and refinements UI to be more visual, easier to read, and easier to find what you are looking for.

Platform, EuroMessage integration

AGO-10063

EuroMessage changed their API endpoint from “ws.euromsg.com” to “api. relateddigital.com”, which broke our integration. We updated our connector and everything is back to its expected state.

360 Profiles

AGO-10018

360 Profiles now makes the search field “Source Customer Number” more obvious.

Actions

AGO-9894

Actions now has lookups enabled for the refinements “Message Name” and “Message Subject” (under the “Performed an event with message” audience rule). This will allow you to easily select the right message to refine your audience rules, by seeing directly a list of messages that match your criterion.