
This update could have been an email. But since we’re warming up for some bigger things coming soon, we figured it deserved a proper post.
This winter, we focused on making the day-to-day stuff better. From faster product collection edits to smoother templates and stacking rules interface. Here's what new. For more updates, visit the changelog.
You can now update product collections via the API. Until now, changing a single product in a collection usually meant starting over. Delete, recreate, rewire everything. Now you can simply update a collection in place.
We also added a new GET endpoint for product collections, so you can see when a collection was created or last changed. Which means you can finally tell when something broke and who touched it last. This is another small step toward making product collections fully API-first and easier to manage at scale.
Stacking logic shouldn’t feel like guesswork. Our redesigned rules interface helps you clearly see which promotions combine, which exclude each other, and why, so you can quickly reason about offer behavior without trial and error.
.webp)
You can now filter logs by free text in both request and response bodies. Whether you’re drilling into validation behavior or tracking redemption edge cases, this gives you more precision when debugging or analyzing activity.
Plus, recent updates added advanced activity tab filters and richer log navigation, which help you find specific events without endless scrolling.
.webp)
If you’re on a single-tenant setup, you can now stream Voucherify events directly into your Snowflake instance. Redemptions, validations, customer activity, basically anything in your activity logs can land in your Snowflake warehouse in real time.
Once it’s there, you can slice the data however you want. Build attribution dashboards, join promo data with transaction history or inventory, and finally answer questions without stitching things together after the fact.
You can now preview a campaign template before using it, so you don’t have to guess whether it’s the one with the settings you actually want or the one that will surprise you later. More importantly, when launching a campaign from a template, you can choose which resources to reuse. Instead of duplicating six nearly identical validation rules, you can just pick the one you already have.
%20(1).webp)
This one’s small, but powerful. You can now include metadata fields and work with arrays directly in the webhook payload designer.
That means your webhook can carry the context it needs to route, personalize, or trigger whatever comes next, instead of hardcoding logic in five different places. Think sending messages via external providers, tagging orders in your CRM, adapting fulfillment flows, or simply not rebuilding the same filtering logic on the receiving end.
This quarter, our education teams prepared plenty of useful resources, perfect for your morning coffee or tea!
This quarter, we’ve had the pleasure to document several awesome journeys of our clients. Jump in to see what they build and how.