Roadmap
Changelog
Workflow Page Filtering
improved
We've added searching and filtering to the workflow page to help you find the workflows that matter. This is especially helpful if you have a long list of workflows and need to find a specific one to look into a task failure or find something you were working on before. You can filter by type, status and who started the workflow.
image (9)
Databricks Egress Connector
new
We’re excited to announce that the Databricks egress connector is available. This connector builds on our existing integration with Databricks to include native support for Delta Lake. The docsite has been updated to outline all of our current capabilities.
Attentive API Connector
improved
AmpIQ
DataGrid
We’re excited to announce that the Attentive API connector is available. This extends our support for Attentive from SFTP to direct connection via API. The Attentive API uses two endpoints - the subscribe user endpoint and the custom attributes endpoint. The subscribe user endpoint enables us to send first name and phone number to opt-in a new user to a subscription. The custom attributes endpoint enables us to update a subscriber with custom attributes. The docsite has been updated to outline all of our current capabilities.
More Powerful Visual Segmentation of Transactional Activity
new
We’re pleased to announce new behavior segmentation tools in the Visual Segment Editor. Going forward, you can easily segment based on the Transactional Activity of their customers and filter these activities further by brand, item category, item sub-category, and item description. Mixing and matching these criteria and using relative dates opens up new journey-based campaign opportunities.
For example, you can now find customers who have purchased a particular product twice in the last 30 days; or customers who have made a repeat purchase of a particular product. This has always been possible in the SQL editor but we recognized that was not as accessible to users who prefer point and click segmentation.
Available clauses include:
  • First Order
  • Repeat Order
  • Most Common Order
  • Total Value of Orders
  • Has Purchased
  • Has Not Purchased
The following animation is an example of this capability at work:
2022-09-22 17
Select All Option in Visual Segment Editor
improved
AmpIQ
Within the Visual Segment Editor, it’s now possible to “Select all” options from within a dropdown. This option is sensitive to the search context, so if you search for a term, you can easily select all attributes that match that term.
vse-select-all
Direct Query Support for Snowflake
new
Major Improvement
DataGrid
We are very excited to release an update to our in-product Snowflake capabilities: query support! Previously, you could only reference entire tables from Snowflake, which required you to create a specific view in Snowflake order to provide Amperity with just the right data.
Those days are now over! Custom queries can now be written directly into the Snowflake plugin configuration removing the need to create specific views within Snowflake to pull specific data into Amperity. This builds on our deep integration with Snowflake and makes it easier than every for you to share data between Snowflake and Amperity.
More Details on Workflow Errors
improved
DataGrid
Previously you weren’t able to see failure details aside from the latest failure in the workflow page if you had a number of errors. This left you guessing as to what error messages were shown for previous workflow failures.
We've added in more error details for previous workflow failures to fill in that gap. They’re accessible via the (…) dropdown in the workflow page so you can now get the details on every error, not just the most recent one.
Database Table Version History
new
Today, we’re making a long-requested update to Databases, allowing database authors to view the SQL edit history of a database table. This lets users understand how a table changed over time and who was working on it. Given that some database tables will have 50–100 edits over their lifetime, this can make it a lot easier to know what’s going on.
There are two ways users can access the feature:
  • Via the Database Editor
    – Users can click the “History” link within the action menu on individual SQL tables.
  • Via URL Navigation
    – We’ve recently made it possible to direct-link to certain modals within the app. While not all modals support this capability yet, most newly added modals should be directly linkable.
Currently, version history shows ONLY differences in the table’s SQL. It does not display any differences in table metadata (descriptions, pick-list config, etc.).
Screen Shot 2022-08-25 at 11
New Amperity Navigation and Global Search
new
New Capability
Major Improvement
Today, we're rolling out a change to Amperity's navigation model. This post will provide details on what will be changing and why.
What will change?
  • Tabs you are used to seeing at the top of the product are now on the left side
  • A global search box now fills that space along the top, allowing you to search the whole app (feeds, queries, segments, orchestrations, etc.)
  • Labels on the navigation can be collapsed to just icons
Why change?
We’re making this change based on research and feedback from users. There are three main benefits:
  • More space for content.
    Most of the experiences in Amperity involve creating or managing lists that go from top to bottom. By moving the navigation from the top to the side, we are creating more space for that content, making the application easier to use. And, we’ve added the ability to collapse the navigation to just icons, giving you even more room when working in Amperity.
  • New search.
    As we’ve expanded the application, we’ve heard from users about a desire to move around more quickly. The new navigation model created space for a global search box, so getting to things is easier than ever.
  • Room to expand.
    As we added more capability to Amperity, we started running out of space in the top navigation, which meant that we did not have room to include top-level links to Workflows, Users, and other areas of the application. The new navigation model gives us room to make those top-level elements and more room to grow.
Questions?
If you have any questions or feedback, please reach out to support@amperity.com.
amp-nav
Standard Email Engagement Data Tables and Semantics
new
New Capability
DataGrid
We're pleased to announce our first suite of email engagement data assets. While you've always been able to ingest and organize email engagement in Amperity, until now we have not had a standard set of out of the box semantics and tables available for use. We've spent the last several weeks working with customers to define this new standard and are introducing it today.
Specifically, we are releasing:
  • A new set of email engagement semantics (email-event/ and email-summary/ ) available to be tagged on the Sources tab
  • A new set of core tables available to be added in the Customer 360 tab (Unified Email Events and Email Engagement Summary)
  • A new database template available to be added in the Customer 360 tab (Email Engagement Attributes)
With these new data assets in place, you can now consistently organize email data in a way that is connected to use cases that have the most value for your brand. This makes it easier for you to build campaigns and analytics based on email engagement and more consistently present a picture of your customer's interaction with your brand.
To build the email engagement data, you can either ingest the raw event data (e.g., opens, clicks, etc.) or summarized email engagements (e.g., opens_in_last_7days, most_recent_email_click_datetime, etc.). If you use email event data, Amperity will generate the summary table, and if you use summary data we can use that directly. One these tables are built, they are then available in the Customer 360 database as well as in the Visual Segment Editor for analysis, insight and actions.
Use cases include:
  • Finding the best email for a customer, based on engagement (Email Engagement Summary) - a future iteration will include out of the box compatibility with Unified Merged, but the data is available to be used today
  • Segmenting customers based on email engagement, for example, creating a campaign of customers who have opened/clicked an email in the last 30 days (Email Engagement Attributes)
  • Analyzing the relationship between email engagement and customer purchases (Unified Email Events)
To learn more about how to add email engagement tables, head to our docs [site.](url)
Load More