---
title: "1914 Release - 2019-04-17"
date: "2025-09-12T05:57:24+00:00"
summary: "Discover new features in AgilOne's 1914 release: Facebook & Google Ads integrations, bug fixes, and enhanced data management capabilities."
image:
type: "announcement"
url: "/customer-data-platform/release/2019-04-17/79816-1914-release-2019-04-17"
id: "df3c0213-27e4-479c-aa92-ddeb1fa133a6"
---

**Area**

**AgilOne JIRA**

**Description of functionality after the fix**

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

AGO-11771

We patched a bug in Actions that was causing numeric data entered into an ‘IN’ clause to disappear after saving.

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-11159

We have added the ability for clients to add descriptions to the AgilOne data model. We will surface these descriptions throughout the application to make AgilOne more self-describing.

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.

360

AGO-11948

We have added the ability to filter what data enters AgilOne’s 360 Search datastore. If there are certain customers (e.g. Prospects) that should not be searchable in 360 Profiles Search we can now configure a filter that prevents them from being loaded into 360 Search.