Omesta blog
The math behind every dollar your stack is leaking.
Long-form on payment recovery, attribution, ad optimization, and the operating decisions that move true ROAS. Written by the team that built Omesta.
Payment recovery
Stripe Smart Retries: how they work and why timing-optimized recovery beats them by 3.2x
Stripe's built-in Smart Retries recover about 22% of failed charges. Timing-optimized recovery — retrying the day a customer's bank refills — recovers 72%. Here's exactly why, with the math.
Attribution
iOS 14.5 attribution: what ATT broke, and how to recover tracking without violating it
Apple's App Tracking Transparency cut Facebook conversion data by 30-40% for most e-commerce stores. Here's how to recover the missing signal using CAPI, server-side events, and modeled conversions — without violating ATT or asking customers for tracking consent.
Payment recovery
Card decline codes explained: every reason a Stripe payment fails, and what to do about each
A complete reference to Stripe decline codes. Which are recoverable with a retry, which need a dunning email, which need a card update, and which mean the customer is gone. Plus the underlying issuer codes most Stripe merchants never see.
Playbooks
The dunning email sequence that recovers 72% of failed subscription payments
A 5-touch dunning sequence with the exact timing, copy direction, and decline-code-specific routing that gets a 72% median recovery rate. Plus the three mistakes that drop most dunning sequences below 30%.
Ad optimization
True ROAS vs reported ROAS: why your Meta Ads look profitable when they're not
Meta-reported ROAS includes click-through purchases, view-through purchases, modeled iOS conversions, and 28-day attribution windows. True ROAS is what your bank actually sees. The gap is usually 30-60%. Here's how to measure both.