We’re excited to introduce the ability for users to pass Amperity campaign metadata (e.g., IDs and names of audience group) as customer attributes to marketing destinations.
Just as each customer profile is unified with an Amperity ID, each campaign membership list built from Amperity is logged with unique IDs for its treatment groups. These metadata attributes can be used downstream to generate unique attribution codes (e.g., URLs) that associate a specific customers' actions (e.g., email click through) to a campaign. This attribution functionality is crucial for marketers as the world shifts towards a cookie-less future.
We’re excited to share that campaigns can now be constructed with audiences containing many segments. When defining the inclusion or exclusion audience set, you can now multi-select up to 10 pre-defined segments from the same database. Additionally, in the segment selection drop down, an easy “Create a segment” button has been added to provide fast access to the Visual Segment Editor.
We currently send email alerts if couriers are missing files as part of an SLA workflow run, but you weren’t able to configure the recipients of those email alerts without reaching out to Amperity Support.
We’ve now added the ability to directly configure which email addresses should receive courier missing files emails. These emails include warnings about courier group workflows pausing, continuing, or failing as a result of missing files detected by the couriers.
You can access this feature via the “Configure Alerts” dialog located in the top right hand corner of the workflows page. More details are located in our documentation: https://docs.amperity.com/reference/workflows.html.
While most of the information you need to build Segments and Campaigns is in the Customer 360 database, there are times when you need another attribute or additional calculations. In the past, in order to do this you would have had to add a new table to the Customer 360 database, which often added time and complexity.
We've now added the ability for you to use Queries to create additional attributes (or outputs) that can be used in the Visual Segment Editor, Segments, and Campaigns. This means that anyone who is able to write Queries can now make the output of a Query (both visual and SQL) available in Segments (as Attributes and Customer Lists) and Campaigns (as Destination Attributes).
Some specific applications of this feature include:
- Creating a complex view of customers based on C360 attributes via SQL to then include or exclude in Segments for downstream Campaigns
- Creating custom join logic on an uploaded list and other C360 datapoints for further segmentation in VSE and Campaigns
Using this is easy - just write a Query, make sure it has an Amperity ID column, and check to make it available in the Segment Editor. Another important note - because Queries can reference uploaded files, you can now use the two features together. For example, you can upload a list of customers or products or other items, then write a query that joins those to an Amperity ID, and then make the result available for segmentation.
We're excited to see what you do with these new capabilities, and as always let us know any feedback on ways we can improve them!
We've heard from a number of you that you'd like to be able to quickly upload a list of customers to Amperity to inform insight, analytics or activation. Today we released a new feature that allows you to do just that - and not only can you upload the list, but you can then use the data in the list in queries or segments or campaigns.
Common use cases include:
- Uploading a list of customers (e.g. promotion recipients) to include or exclude from a customer segment
- Uploading an unattributed list of customers (e.g. event participants) to tie back to known customers with Amperity ID, transactions, and more
- Uploading a reference file (e.g. fiscal calendar, nickname list) for speedy iteration in queries
You can upload a file right from the Customer 360 tab or on the sidebar in the Query Editor. Today uploads are limited to CSV files under 50MB in size. If your list has email addresses, you can select an email field in the upload and we'll automatically use the customer information in your database (Merged Customers) to connect it to existing Amperity ID information if there is a mapping.
Once the file is uploaded, you can access it in the same way you would access any database table and write a query against the file. In addition, if your uploaded file has an Amperity ID (either in the file or through mapping the email address), you can make it available in the Segments experience.
Note that uploads may take up to 10 minutes to be available and only one file may be uploaded per tenant at a time.
We're always open to feedback on the experience so if there are other capabilities you'd like to see included, please let us know!
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.
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.
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.
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: