Lots of goodies coming in for the May 25 release.
And as always, we stagger all releases to slowly rollout over a week to ensure no major bugs get pushed for too many people.
If you notice any bugs or issues, please reach out to your dedicated support rep.
The features are in no particular order.
1. API - Dashboard Stats Summary for Workspace
We’ve added a new endpoint to let you quickly generate a summary of stats for a workspace between two sending dates. You no longer need to loop through each campaign and call the campaign stats separately.
2. API - Full Normalized Workspace Stats (grouped by event + date)
We heard you loud and clear, and we’ve now exposed an endpoint that will give you complete stats, grouped by date. This way, if you’re building internal dashboards, you no longer need to build this logic yourself.
3. API - Workspace v1 endpoints are now deprecated
You can still use these endpoints, but we recommend migrating over to the v1.1 endpoints instead.
4. API - Full Normalized Campaign Stats (grouped by event + date)
We extended the fully normalized stats functionality over to a campaign as well. This way, if you only want to build a graph or report on a campaign by date, you can fetch all these events.
5. API - Fully Normalized “Campaign Event” Stats for Campaigns + Sender Emails
Sometimes, you want a list of all events for a specific list of campaigns or sender emails.
For example, if you want to see how many emails were sent by a given sender email, how many replies were received, bounces, etc.
You can now use our “campaign events” endpoint and pass in a date range + campaign IDs or sender email IDs.
Extremely useful to see which one of your emails are performing well, in combination with our warmup endpoints.
6. Bug fix when mapping certain column types
Before, if your column contained values that were explicitly 0 when uploading custom variables, they would get mapped to “null”. This has now been fixed
7. Bug fix when launching unfinished campaigns via API
Before, you could launch campaigns via API that may not have been finished (eg contacts missing). This would cause the campaign to fail. This is now fixed and you’ll receive an explicit error when attempting to launch unfinished campaigns.
8. API - Update a contact (lead) status. Single and Bulk
You can now update the status of a lead via the API. This means that if a lead was categorized as bounced due to a sender block, or unsubscribed, you can reset their status via the API.
Especially useful if you’re running contact validations from Clay and want to map the statuses to your Bison instance.
9. API - Warmup limit updates
You can now bulk update warmup limits via the API
10. API - Bulk update sender email limits
Before, you could only update sender email daily limits one at a time. Now, you can bulk update them for a list of sender emails.
11. API - Send test email
You can now trigger a test email for a sequence step via the API. You can even decide to send this via your instance's dedicated IPs to simulate a real campaign email
12. Webhooks - Real time notifications for when accounts are kicked off warmup
You can now subscribe to webhook notifications for when your sending accounts are kicked off warmup due either causing too many bounces, or receiving too many bounces.
13. Webhooks - Raw message ID is now available in all email sent / received webhooks
Sometimes you may need the underlying ESP message ID for tracing purposes. While we had these in the API responses before, we now also send them via webhooks.
14. Bug fix for editing single signatures in the UI
When manually editing signatures one at a time, the editor would sometimes fail to load. You’d have to refresh the page and try again.
This has now been fixed, and a refresh is no longer required.
15. Headless UI mode - embed a headless OAuth connection workflow
Some of our customers are building their own apps on top of our sending infrastructure. We now have a headless UI mode for the email connection flow, so you don’t need to implement your own. Simply embed the Bison email connection flow in your own apps.
