Solutions · E-commerce & D2C
A store loses most of its revenue between product view and payment, and then again between the first order and the second. Edverix joins storefront, app and order events on one profile, so recovery messages know the exact item, the exact step and the exact price, and retention journeys know when a customer is due to buy again.
What we track
7 eventsAutomation
Each play is a trigger on your own events, an action through your own providers, and a number you can hold it to.
Trigger
checkout_started with no order_completed within 45 minutes
Action
WhatsApp with the cart contents and a live price, then push after four hours, then email the next morning
Proof
Conversion attributed inside a 24-hour window against a 10% control group
Trigger
Three product_viewed in one category, no product_added, session ended
Action
In-app or web push with the two most-viewed items and the top recommendation from the same collection
Proof
Add-to-cart rate for the message cohort against holdout
Trigger
payment_failed with error code
Action
SMS with a retry link within two minutes; branch on the error code to suggest a different method
Proof
Recovered order value by error code
Trigger
Computed attribute days_since_last_order crosses the category's median reorder interval
Action
Email with the last order pre-filled, in the customer's language, sent at their best hour
Proof
Repeat-order rate by cohort
Trigger
order_completed, then delivery_confirmed from your OMS via the server API
Action
Rating primer in-app; review request by email three days later; exit the journey on review_submitted
Proof
Review rate and NPS response rate
Trigger
RFM bucket moves from Loyal to At risk
Action
Win-back offer sized by lifetime value; universal holdout excluded
Proof
Incremental revenue against the permanent holdout
Reports
Every report runs on the raw events, and any report becomes an audience in one click.
Hold order_id constant across steps.
From the attribution partner on the profile.
Cohort grid split by a first-order property.
Because provider costs are yours, this is a real number.
Channels that carry the weight
Platform
The whole platform is available on every plan. These are the parts this vertical leans on first.
FAQ
Anything not answered here is a demo call away.
Request a demoAll three. Hosted platforms use the web SDK plus a server webhook for orders and refunds; custom storefronts use the SDK and the server API directly.
Yes. Catalog fields resolve at send time, so a message never advertises a price that changed or an item that sold out.
More industries
Get started
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.