Actions

AGO-12617

The campaign history filter had a UI bug where instead of showing names, it was showing IDs after the campaign is saved and reopened. This is fixed now.

Platform: Google Customer Match

AGO-12646

Google Customer Match connector is enhanced to tackle the case where multiple lists with same name exist on the Google side (for ex, if a list with same name as an AgilOne campaign is uploaded directly to Google outside of AgilOne processes)

Actions

AGO-12493

A bug in the logic of how isEmpty operator is combined with other operators is fixed now.

Actions

AGO-12550

The editor used in “”design”” tab of SendGrid campaigns in Actions is now upgraded.

Actions

AGO-12552

An additional attribute is in the output to distinguish multiple events output from the Latest Events content model.

Actions

AGO-12576

For connectors that support aliasing, the corresponding destination lists show the original names and aliases in the hub actions UI.

Actions: Campaigns+

AGO-11968

Segmentation operators in Campaign+ have been extensively enhanced. We now support all operators that are supported in audience criteria. Relative date comparators and String contains are notable additions.

Platform

AGO-12574

We added new entities and attributes for Payment Method integrations. We can now accept data for payment methods on each transaction. In the future, we will expose these attributes as dimensions in Metrics and as filters in Actions. Please reach out to your AgilOne CSM if you would like to take advantage of this integration.

360 Profiles

AGO-12531

Following up on work done in 1938, we have improved several display names that are surfaced in 360 Profiles so that they match Metrics and Actions. These include attributes on:

• Household

• Master Customer Group

• Address

• Product

This improvement project to Actions and 360 Profiles display names is now complete.

Actions: Campaigns+

AGO-12551

On occasion Campaigns+ could fail due to a user-input character that interrupted a downstream process. Therefore, we have added guardrails around what characters can be used in Campaigns+. You can no longer use a single-quote (’) in Campaigns+. We hope to improve this behavior in the future.

Actions: Campaigns+

AGO-12327, AGO-12335

Additionally in the Campaigns+ Content page, you can now mark variants as ‘Do not send’ so that they are withheld from delivery to the downstream system. Variants that are marked as ‘Do not send’ are still delivered to Metrics for Cohort Analysis, so please make sure to name them appropriately.

Metrics

AGO-12527

We added tooltips on hover for long Look, Dashboard and Folder names in the Metrics listing page that were being clipped earlier.

Actions

AGO-11606

We have fixed a very rare bug that could cause content within a recurring Actions campaign to mix.

Actions

AGO-12482

For Campaigns+ users, you can now use the new ‘Were included in an AgilOne audience’ filter to include or exclude specific audiences, segments, and/or variants from your campaign.

Actions: Campaigns+

AGO-12071

Campaigns+ has gotten much faster. Executing campaigns and segment counts should be quicker than before.

AIF: Silverpop Output Connector

AGO-9507

If you use Actions to push audiences to Silverpop, we have patched a bug that was preventing empty/null date times from being pushed as dates. Clients were working around this by pushing dates to Silverpop as the string/text data type. Now you can push AgilOne date times to Silverpop and keep them as date times.

360 Profiles

AGO-12462, AGO-12424, AGO-12422, AGO-12452

We have made several improvements to the 360 Profiles user experience and consistency of the user interface.

Campaigns+

AGO-12448

In Campaigns+, A/B Test and Limit By Quantity now function closer to expectations. Before, A/B Test variants may have been slightly smaller or larger than requested. For example, if you created variant A as 50% and B as 50%, then the result may have been something closer to 49% A and 51% B. For Limit By Quantity, before 1936 the variants created were not perfectly random. Two campaign executions could have resulted in the same distribution of audience members to variants. Now, Limit By Quantity is close to perfect in how it randomly assigns individuals to variants.

Campaigns+

AGO-12071

Campaigns+ now performs much faster when you have complicated audience criteria.

360 Profiles

AGO-12419, AGO-12281

For clients that use master customer groups, in 360 Profiles, AgilOne can now surface the multiple master customer identities that were de-duplicated into a single master customer group.

360 Profiles

AGO-12451

In 360 Profiles, the headers at the top of each page are now configurable. If you would like to adjust the label of a particular section (e.g. Transactions), you now can.

Campaigns+

AGO-12442

In Campaigns+ we have rolled out the greatly improved documentation, and provided links to the documentation from the application. Also, A/B Tests and Limit By Quantity are no longer in a beta program, they are available for general consumption.

Interactive Queries

AGO-12399

We made some enhancements to the welcome email and login screen of Interactive Queries to clarify the login options for the user.

Platform

AGO-12182

We fixed a bug in our genderization engine that was causing individuals with a first name of ‘and’ to get a gender of ‘ ‘. Now ‘and’ is properly matched to the ‘U’ (i.e. Unknown) gender.

360 Profiles

AGO-6659, AGO-11835

When searching 360 Profiles we now return and surface the city for each mailing address.

Actions

AGO-12338

We have fixed the ability to use product-based content models with the A1 Mailer (i.e. SendGrid) destination.

Actions

AGO-11432

If you have custom event’s that are store (i.e. organization) dependent (e.g. store visit, phone call, etc.) you can now refine by the store details in Actions event filters: ‘Performed an event’, ‘Performed a number of events’, and ‘Performed an event with product category’. For example, you can now filter out an audience who visited a specific store, or sign-up on a specific website.

Actions: Campaigns+

AGO-12273

In Campaigns+, you can now leave variant and/or segment-specific echo content empty. You no longer have to populate echo content for every segment/variant.

Platform: Salesforce Marketing Cloud output connector

AGO-12308

We fixed a bug with our Salesforce Marketing Cloud output connector that was causing data extension records to be dropped due to an empty (i.e. NULL) integer or other numerical value.

Campaigns+

AGO-12223

For Campaigns+ users, we patched a bug in the execution calendar that was preventing you from accessing the campaigns shown there.

Platform

AGO-12260

In Actions, we have added a guardrail to prevent users from being able to assign the same campaign two different execution schedules. Now when you schedule a campaign the application will check if a schedule already exists before allowing you to schedule.

Platform: Euromessage Input Connector

AGO-12271

If your environment pulls data using AgilOne’s Euromessage Input Connector, we have implemented a performance improvement that reduces the number of API calls AgilOne fires when a campaign has zero events (e. g. send, open, click, etc.) to return. Previously we were attempting to pull all events for all campaigns, irregardless if the campaign had events to return or not.

360 Profiles

AGO-12199

We fixed a bug in 360 profiles that was causing product recommendations to only show up for one of the identities rather than for every identity.

Cohort Analysis

AGO-12257, AGO-12259

With Campaigns+ you can now send variants to Cohort Analysis for performance reporting on different treatment or communication creatives.

360 Profiles

AGO-9895

In the 360 Profiles application you can now adjust how many transactions and/or events are returned for you to view. The previous limit was 40, but now you can adjust this to be 25, 50, 75, or 100.

Actions

AGO-12261

Actions users will be happy to hear that (nearly) all filters now have improved descriptions and names. Additionally, we have hidden several duplicate filters that were confusing users.

Platform: Google Ads Offline Conversions Output Connector

AGO-12249

We are no longer failing the Google Ads Offline Conversions Output Connector when a partial data failure is returned by the Google Ads API. We are now logging any records that result in a partial data failure, and allowing the rest of the process to succeed.

Actions

AGO-11318, AGO-12203

In Actions campaigns you can now add multiple content models to a single campaign. Previously you were limited to just one content model per campaign. For example, you can now add both ‘Last Products Purchased’ and ‘Primary Store Details’ to the same campaign. However, there is a limitation, you are only allowed 1:n content model per campaign. For example, you cannot add both ‘Last Products Purchased’ and ‘Last Products Browsed’ to the same campaign because the result would be exponentially large and unintuitive.

Actions: Campaigns+

AGO-11951, AGO-12237

In this release we are adding a significant new addition to Campaigns+, the ability to selectively withhold certain segments from being included in the campaign output. Now you can mark segments as ‘Do not send’. This will cause the segment to be suppressed from the execution and not be sent to the destination. In the future we will expand the ‘do not send’ functionality to variants.

Platform: Bronto Output Connector

AGO-12172, AGO-12189

For clients that use Bronto, we have introduced the ability to rename the AgilOne Actions output columns. This will enable you to push content from AgilOne Actions to existing columns so that you can reuse them and reduce the number of columns you need to purchase from Bronto.

360

AGO-10095

We have patched a bug in the 360 Profiles Overview tab that was incorrectly allowing each sub-section (recent events, recent transactions, etc.) to be scrollable.

Actions Campaigns+

AGO-12170

The Campaigns+ listing page has been updated to properly show if a Campaign+ is scheduled.

Actions Campaigns+

AGO-12037, AGO-12038, AGO-12054, AGO-12055, AGO-12084, AGO-12173

The second significant Campaigns+ enhancement we are releasing with this sprint is the ability to on-demand refresh the count of members per segment. If you have a segmented Campaign+ you can now go to the Content screen and request that the count of members per segment be refreshed. Then you can click another button to see the most recent refresh of counts per segment. This allows you to review how your segments are populated, and then adjust them as needed, before you execute the campaign.

Platform: Machine Learning

AGO-12001, AGO-12003

In this release we are simplifying how we integrate the result of our machine learning models into each AgilOne application. Now each 1:1 machine learning model (1 customer belongs to only 1 segment, such as LTC, but not U2P) will be summarized on a new Machine Learning Summary table that is easier to integrate into Actions, Metrics, and 360. Previously, each new model required an additional integration effort before they became useful to the user.

360

AGO-11844

We have greatly improved the performance of the 360 Search API. You should experience a ~10x performance improvement when searching for customers in 360.

Actions

AGO-12044

The Campaigns+ Segment Builder UI now shows you the segmentation criteria for each segment when hovering over a segment’s name. You no longer have to click into each segment to see how they are defined.

Actions

AGO-12113

The Campaigns+ Destination UI now surfaces detailed descriptions about each destination channel. Please reach out to your Client Success Manager, Support, or Implementation Consultant if you would like to improve any of the descriptions.

Connectors: Facebook Offline Conversions

AGO-12060

Facebook updated their Offline Conversions API, so we have updated our integration to accommodate their changes. Previously, transaction count related metrics may have been inflated.

Actions

AGO-12023

We have improved the Campaigns+ destination selection user interface.

Actions

AGO-12059, AGO-12014

We are making the filter and content descriptions in Actions more useful. In addition to providing more verbose and detailed standard descriptions, Implementation Consultants can now override standard descriptions in order to provide their own.

Platform

AGO-11755

With this release AgilOne is introducing a new Actions destination option: Google Customer Match. We have built a tight API integration with Google Ads to enable our clients to upload a list of individuals to target within the Google ecosystem or to build a lookalike audience of similar individuals. This integration is just entering an Early Adoption Program (EAP). Please reach out to your Client Success Manager if you are interested in joining the EAP.

Actions

AGO-11768

In this release we have improved Actions Advanced Segmentation to enable the use of the ‘In’ and ‘Contains’ (i.e. Like) operators when segmenting an audience.

Actions

AGO-12006

We have patched a bug in Actions that was causing the ‘Were included in an AgilOne campaign’ filters to incorrectly display the campaign ID instead of the campaign name after saving. These filters now properly surface the campaign name.

Actions

AGO-12016

In addition, we fixed a separate bug with our Actions audience count refresh cache that was causing the cache to not be read properly on certain occasions. For scalability reasons there are two separate cache services maintained behind the scenes. Before 1916, the two services could have gotten out of sync, but now they will remain in sync and return the same values.

ML

AGO-11828

For some ML models (Likelihood to Buy, Behavior Clusters, and Product Clusters) we were not properly storing the cluster names of historical values: ‘as of this month’, ‘1 month ago’, and ‘2 months ago’, instead we were storing the raw data. For example, instead of storing the human readable name of ‘High LTB - Decile 1’, we were storing and surfacing the raw data of ‘1’. This has been fixed, so over the next 2 months the values for LTB, BC, and PC ‘as of this month’, ‘1 month ago’, and ‘2 months ago’ will be more human readable and usable.

Platform

AGO-12034

In this release we patched a bug with our customersummary.emailStatus logic that was causing both ‘Unverified domains’ and ‘Unknown’ emails to get assigned an email status of ‘U’. Now, only unverified domains will receive an email status of ‘U’ and unknown emails will be assigned a status ‘Unknown’.

Metrics

AGO-11614, AGO-11632

We are happy to announce two new native destinations where our clients can send their data:

• Facebook Offline Conversions

• Google Ads Offline Conversions

Through these API integrations you can upload physical (i.e. offline) transactions and/or events to these marketing platforms so that they can calculate your return on ad spend for retail transactions.

Actions: Bronto

AGO-11923

In this release we have fixed a bug with our Bronto Output Connector that could have caused product data pushed to Bronto to leak across campaigns within Bronto.

Platform

AGO-11790

You can now promote source data with the same name from two different source tables to the same reporting summary table. Previously, you could not add both the campaign and message name to the promotion table for reporting.

Actions

AGO-10904

We have patched a bug in the Actions Campaigns ‘contains’ operator that was causing it to not be case insensitive for foreign characters. The default behavior for the ‘contains’ operator is that it is case insensitive.

Actions

AGO-9824

After significant demand, we are introducing a new output connector: Azure Blob Storage. If you use the Microsoft Azure cloud, you will now be able to push data from AgilOne Actions or Reports to Azure. This feature is now entering an Early Adopter Program.

Platform

AGO-11199

Before 1912, Actions Campaigns were more likely to fail during the nightly batch data refresh process called the Business Intelligence (BI) Workflow. We have improved the BI workflow to reduce the likelihood that an Actions Campaign will fail during the BI refresh process.

Platform

AGO-11481

We have fixed a bug in the 360 Refresh process that allowed data to be missed from being sent to 360 if the refresh process failed (or was killed) and was restarted.

Platform

AGO-11912

In 1912 we have improved the Actions Campaigns, Metrics Reports, and Data Exports listing pages to allow the user to easily review IDs, created by email, and last edited by email.

360

AGO-11535

We have patched a bug in the 360 search API where previously any 360 search by email address would return many more email addresses than requested. This has been shown to improve 360 search performance by 15%.

ML

AGO-11533, AGO-11545, AGO-11838

Several new machine learning features that are in an Early Adopter Program (EAP) are now available in the 360 Profiles user interface.

Platform

AGO-11792

We have squashed a bug that prevented customers from being segmented into the ‘Upward’ or ‘Downward’ buckets for ‘Revenue Trend Segment’. These customers were instead falling into the ‘Stable’ bucket. This bug was introduced by a recent upgrade to our Hadoop environment.

360 Profiles

AGO-11546

As part of the early availability of the product recommendations machine learning model, we have enhanced our 360 Profiles API to support surfacing production recommendations in the 360 API. We hope to add these recommendations to the 360 profile user interface soon.

Actions

AGO-11895, AGO-11670, AGO-11752, AGO-11751

With this release we have finished the first version of the front end for Actions’ new Advanced Segmentation features. Advanced Segmentation is a new addition of Actions features that should enable our clients to better personalize their campaigns to their customers. Now that the front end is available, we would love to demo the new features to you. Advanced Segmentation will be available in an Early Adopter Program starting mid-April.

Platform

AGO-1169

We squashed a bug that sometimes resulted in duplicate master customer records being generated by the Likelihood to Buy machine learning model.

Actions

AGO-11817

We squashed a bug in the ‘Purchased a Number of Products’ Actions filter that was deflating the number of products purchased. Previously, this filter could incorrectly de-duplicate transaction items that were in fact unique and should not be de-duplicated. This led to fewer customers being included in the audience since some purchased quantity was not included in the sum of purchased products.

Actions

AGO-11734

We have introduced a new feature that eases the development of custom Actions audience filters and content models. There is still significant work to do here, but we are making incremental progress.

Actions: Bronto Connector

AGO-10849

We have fixed a bug that was preventing AgilOne from exporting some Actions output attributes as a Bronto List Field. Since Bronto Field names have a limited maximum length, AgilOne has to hash our output columns to a reasonable length. Sometimes this hash was generating a result that included a character that was unacceptable to Bronto, a ‘-’ character. We are no longer allowing AgilOne-generated Bronto Field names to include a ‘-’ character.

Platform

AGO-11517

We have added to our data model the ability to associate events to organizations (i.e. stores or websites). Now events you send to AgilOne can be linked to stores. For example, if you have an in-store loyalty program sign-up custom event you may want to keep track of which store the customer signed up in.

Actions: Coupon Management

AGO-11508, AGO-11641, AGO-11644, AGO-11661, AGO-11662, AGO-11687, AGO-11695, AGO-11701, AGO-11707, AGO-11753, AGO-11774, AGO-11791

With the first major feature release of 2019 we are deploying several new coupon management features. With these enhancements AgilOne will be empowered to create individualized, omni-channel coupons for promotions, enable Actions users to link those coupons to a (master) customer, and then distribute the coupons to the customer across engagement channels. We are excited about the new coupon related use cases that these features will enable. Coupon management is just entering an early adoption program (EAP). Please speak with your Customer Success Manager if you are interested!

Platform

AGO-10750

Master customers with over 10,000 transactions are no longer labeled as ‘Non Buyer’, they are now labeled more appropriately as ‘NA - High Volume Buyer - 10k+ transactions’. AgilOne sets aside master customers that have over 10,000 transactions during our business intelligence calculations because they can delay (or prevent) the completion of our overnight refresh process, without adding any real value for our clients. Previously when we set them aside we did not label them properly.

Actions: Facebook Output Connector

AGO-11594

Due to a recent update to Facebook’s Custom Audience API, an AgilOne Actions Facebook campaign would fail during the 2nd+ execution of a campaign, when the audience being exported differed from the previous audience exported by <= 200 individuals. We have implemented a fix to prevent Facebook campaigns from failing during these specific circumstances.

Platform

AGO-11262

Some web events were not being counted properly during our customer summary calculations for FirstVisitDate, LastVisitDate, TotalVisitCountLast30Days, TotalVisitCount31_60Days. We are now properly counting all web events when performing these calculations.

360

AGO-11514

A bug was causing transactions for customers with really short customer IDs to either be missing from 360 or surface transactions from other customers. This bug has been fixed. Within 360, transactions should no longer be missing for individuals with short customer IDs.

Actions: Euromessage Output Connector

AGO-11630

In order to support sending SMS campaigns via EuroMessage, we have added the ability to specify any customer-level attribute as the primary key (e.g. primary phone number) when pushing data from AgilOne to EuroMessage. Previously, AgilOne’s EuroMessage output connector only allowed email address as the primary key.