DISCLAIMER: It is possible for features documented in these Release Notes to have their release delayed. This happens in situations where we encounter unexpected software behavior prior to release. In such circumstances, a delayed release will be added to a future release.
Table of Contents
TapClicks Platform
Added display banner when a user impersonates another user
We have introduced a new feature that enhances the user experience. Now, when users log in as another user using the "Log in as User" functionality located near the user profile, a visible sticky banner is displayed to remind you that you are using another user's instance. (The old behavior is still visible.)
The banner message prominently showcases the user's role, first name, last name, email ID, and data profile. For example, if you are logged in as a client named John Doe with the email address [john.doe@clientcompany.com|mailto:john.doe@clientcompany.com], the banner will read: "You are logged in as Client - John Doe ([john.doe@clientcompany.com|mailto:john.doe@clientcompany.com]), Default Data Profile".
Data Features
Added alias delivery types to Data Exporter
We have added two new delivery types to Data Exporter:
- Amazon Aurora MySQL
- Amazon Aurora PostgreSQL
Users interested in sending data to these locations can now do so.
Enabled editing of existing Data Exporters
Users can now edit their existing Data Exporters. The following can be edited:
- New fields can be added and existing fields can be removed
- All data destination types can be edited
This gives users the ability to further refine what data they export from their dashboard to their target location.
Updated scheduling option language on Data Exporter
We have updated the scheduling option language for Data Exporter from On Auto (run at sync finish or 8 pm Eastern Time to When the daily data fetch is complete (run at data sync finish or 8 pm Eastern Time).
The previous language was confusing. This change more clearly tells the user what to expect with this setting.
Updated trash can icon behavior
We have updated the behavior of the trash can icon for channels, calculations, and other pages. Now, when users see the list of areas where this item touches, they can open that object in a new tab. This makes it easier to investigate where a given item is in use, make changes appropriately, and not lose the previous step.
TapOrders
Vendor and Vendor Restricted roles updated
This feature applies a slightly stronger restriction to the existing Vendor and Vendor Restricted roles. For customers who have 3rd party users logging into their instance as a Vendor or Vendor Restricted role, those users will no longer have access to viewing comments, viewing uploaded files, or re-assigning tasks from the Task details page.
TapAnalytics
Improved bulk import for Goals
We have made usability improvements to the bulk import for the Goals feature by providing context for fields in the CSV file. This improves the overall usability of the Goals feature.
Instant On Connectors
Facebook Ads - added field
We have added a field labeled Custom Conversion ID to the existing Custom Conversions data view. Users can now report on custom conversion IDs, in addition to conversion names for more granular reporting.
Facebook Ads - added fields
We have renamed events to match Facebook’s UI. This will clear up confusion related to events that are being displayed within TapClicks. The fields that have been modified are listed below and are available using the existing Ads data view:
| Previous Name | New Name |
| Website Adds of Payment Info | Add Payment Info |
| Website Adds to Cart | Adds to Cart |
| Website Adds to Wishlist | Adds to Wishlist |
| Website Registrations | Completed Registrations |
| Website Checkouts Initiated | Initiates Checkouts |
| Website Leads | Leads |
| Website Purchases | Purchases |
| Website Searches | Searches |
| Website Content Views | View Content |
LocaliQ - exposed Data Load Status' assignment status
We have exposed LocaliQ assignment level statuses to the Data Load Status page Assignment Status screen (see image below). Now, users have insights into specific assignments, that may have fetch issues, that are unique to those records. This can help set expectations with internal and external stakeholders.
Google Business Profile - made available in geo widgets for Campaign data view
Users can now view data in geo widgets using the existing Campaigns data view. This functionality was previously only available using the Top Driving Directions Last 30 Days data view, but that view has been deprecated.
Xandr Invest - Updated data based on timezone
We have updated the way in which we pull data for our users to ensure that the data comes through in the connected user’s timezone. Now, when building out reports for clients, users are able to report on the data in a more accurate timezone.
Spotify Ads - upgraded API
We have upgraded the API connection for Spotify Ads to the latest version (v2) to ensure continued data flow. With this update, additional changes have been made as a consequence of changes made by Spotify. The changes are as detailed below:
Assignment structure changed:
- Level 1 - Account
- Level 2 - Campaign
Fields we deprecated across data views:
All levels:
- Fetches
- Errors
- Ads Served
- Render Ratio
- Fetch Reach
CGN level :
- Organization ID
- Ad Account Description
- Advertiser Description
- Advertiser ID
- Advertiser Name
- Advertiser Version
- Campaign Version
Ad set:
- Active Status
- Ad Set Serving Issues
- Ad Set Version
Creative:
- Landing Page Domain
- Ad Version
- Companion Asset ID
- Companion Asset URL
- Asset Width
- Asset Height
Data views we deprecated:
- Geo
- Platform
Fields we added:
Creative:
- Ad Updated Date
- Tagline
- Delivery
- Ad Preview Url
Data views we added:
- Country Lifetime
- Geo Lifetime
On Demand Connectors
Enabled custom filtering logic
We have built out filtering functionality for the various connectors where the source API does not support filtering. This enables users to filter on all of the On Demand widgets, regardless of connector.
Twilio - enabled as an On Demand connector
We have exposed Twilio as an On Demand connector. Twilio users who want to take advantage of On Demand connector features may now do so.
CallRail - enabled as an On Demand connector
We have exposed CallRail as an On Demand connector. CallRail users who want to take advantage of On Demand connector features may now do so.
Salesforce Marketing Cloud - enabled as an On Demand connector
We have exposed an On Demand connector for Salesforce Marketing Cloud.
Added multi-account support
We have added the ability to utilize up to five assignments in a single widget where previously it could only support one. This will enhance users' ability to work at scale.
Implemented search for data grid widgets
We have added the ability for users to use the search bar in data grid widgets of On Demand connectors. This brings the user experience in line with that of stored data widgets.
Smart Connectors
ClickHouse - added as a new delivery type
We have added a new Smart Connector delivery type for ClickHouse. Users who are looking to collect data from ClickHouse can now do so via Smart Connector.
AlloyDB - added as a new delivery type
We have added a new Smart Connector delivery type for AlloyDB (alias to Postgres). Users who are looking to collect data from AlloyDB can now do so via Smart Connector.
Enabled quick assignment by default in database delivery types
Users who are using database delivery types for Smart Connectors will now be able to use quick assignment by default when creating new Smart Connectors. They will also have the ability to test the quick assignment with the click of a button from the Smart Connector configuration page. Another part of this work exposes customers to an automatic prompt for a query to help them get started with their Smart Connector.
This enhancement brings our Smart Connector database delivery types into alignment with other Smart Connector delivery types which offer quick assignment while offering ease of use enhancements. The automatic prompt will also help coach users get started instead of trying to create a query from scratch.