Messaging Channels
Mobile push, web push, in-app, inbox, email, SMS, WhatsApp, RCS, on-site and webhooks, with no margin on delivery.
DeliverExplore Channels
Deliver
Every message resolves at the moment of send.
Versioned templates, tokens with fallbacks, reusable blocks, catalog-driven recommendations and prices resolved live.
Template · liquid
v7 · approvedHi {{ user.first_name | fallback: "there" }},
{{ cart.items[0].name | fallback: "your cart" }} is back in stock at
{{ catalog.price(sku) | inr | fallback: "our best price" }}.
You might also like:
{{ recs.top(3) | fallback: "bestsellers" }}
Opt out: {{ unsubscribe_url }}
tokens 5 · fallbacks declared 4 / 4 · unsubscribe_url is system-provided
Preview · u_5f2a
rendered at sendA
Acme Retail
Business account · WhatsApp
Hi first_name,
cart.items[0].name is back in stock at catalog.price.
You might also like:
- Grip Socks · 3 pack₹699
- Hydration Belt₹1,299
- Trail Cap₹899
Opt out: unsubscribe_url
10:42
QA before every send
running · 0 / 5- all tokens resolved · 5 / 5
- every token has a fallback
- unsubscribe link present
- SMS variant length 142 / 160
- template matches approved v7
Overview
Nobody should receive an email advertising yesterday's price, and nobody should receive "Hi ,". Edverix templates are versioned per channel, every token declares what renders when the value is missing, and a QA pass runs before every send. Connect your product catalog and recommendations, collections and live prices become tokens like any other.
Only on Edverix
- Fallbacks that actually workOnly on Edverix
Every token declares its fallback, and any token without one is flagged before the send.
- Automated QA before every sendOnly on Edverix
Tokens resolve, SMS length and cost are sane, the unsubscribe link is present, the template matches what the regulator approved.
- Recommendations that respect marginOnly on Edverix
Rank by contribution, not just by likelihood to click.
Capabilities
Everything in Personalisation
13 capabilities in 3 groups, organised the way the product is.
Templates
Versioned per channel
Previewable, shareable across campaigns and journeys, with a full change history.
Tokens from anything you know
User attributes, event properties, computed attributes and catalog fields, with Liquid-style filters.
Fallbacks that actually workOnly on Edverix
Every token declares its fallback, and any token without one is flagged before the send.
Reusable blocks and asset library
Change the footer once and every template updates; images and files referenced everywhere, replaced centrally.
Locale-driven content
Every customer in their own language, with a default when a translation is missing.
Dynamic content
Content fetched at send time
Prices, stock and copy pulled live from a URL when the message goes out.
Personalised images and deep links
Visuals and URLs generated from the customer's own data.
Automated QA before every sendOnly on Edverix
Tokens resolve, SMS length and cost are sane, the unsubscribe link is present, the template matches what the regulator approved.
Catalog and recommendations
Catalog sync
CSV, XML or RSS, uploaded directly or synced from your bucket on a schedule.
Events map to products
Product views, cart adds and purchases join to catalog rows by item id automatically.
Dynamic collections
Rule-built slices with multi-level sorting and randomisation, so customers do not see the same five items every day.
Recommendations, five ways
Popular, trending, bought-together, people-like-you and item-to-item, or bring your own model through an API.
Recommendations that respect marginOnly on Edverix
Rank by contribution, not just by likelihood to click.
FAQ
Questions about Personalisation
What template language do you use?
A Liquid-compatible syntax with filters, conditionals and loops, so existing templates port with minimal changes.
How large can a catalog be?
Feeds up to several million items sync incrementally; only changed rows are reprocessed.
Get started
See Personalisation on your own data.
Send your first event in an hour, simulate your first journey against real history, and keep every byte of it in a database you can query.
- No credit card for the Developer plan
- Bring your own providers
- Export everything, any time