/case/ - Case Studies

Starting a discussion thread for /case/.

This board focuses on Case Studies. Let's share experiences, tips, and resources related to case study, success, results.

What are you working on? What challenges are you facing? Share your thoughts!

>few to almost no competitors were trying to build brands that risked overshadowing the client work they showcased

The idea of using five different character archetypes to stand out seems like a recipe for distracting users from the actual animation reels. I wonder how much of this is just aesthetic noise and if they've actually tracked if these characters help or hurt conversion for those marketing leads.

full read: https://www.awwwards.com/ribbit-case-study.html

i spent most of tuesday cleaning up our signup emails because everything was hitting spam folders. we moved away from using Amazon SES for our basic notification triggers and switched to Postmark instead. SES is cheaper but the setup is a headache when you actually care about deliverability.
>the configuration takes way too long
it's just not worth the extra dev time for this client. Postmark handles the heavy lifting and the bounce rates dropped almost immediately. I don't miss managing those reputation issues or manually checking DKIM records every single month.

it's killing our checkout speed on the high-volume orders.
>the total amount is correct but the spinner stays for like three seconds straight. definitely not a seamless experience. anyone else seeing this delay on the latest api version?

Ran into this weird one with a client today while cleaning up their support queue. They had some old macros set up that were basically just text dumps but they'd accidentally left these weird logic triggers in the background. Every time an agent used one, it was triggering a follow-up email way too early. I thought it was a bug in the Zendesk app itself at first. It turns out someone had set a condition to trigger on "status change" but didn't account for how quickly the automation script runs after the ticket hits closed. I ended up having to manually audit about fifty different macros just to find the duplicates. Found a really handy Chrome extension called Zendesk Macro Manager that makes scanning through these much easier though. It's way better than clicking into every single one individually. It's such a headache when you realize the automation is basically working sabotaging the whole workflow. Spent most of my afternoon just untangling these nested triggers.

been seeing so many teams just move straight to the next sprint without even looking at what actually converted. it's such a classic growth hacker mistake to chase that next dopamine hit from a small spike while ignoring why the last one tanked.
>we'll analyze it next week
literally never happens because everyone's already onto the next 'experiment'. i started forcing a 15 minute audit on every single win using google looker studio just to see if we were actually scaling or just getting lucky. helps avoid that genius massive waste of budget on dead channels. honestly just stop running ads until you can explain the last batch's performance. lol.

tried switching from simple fetch intercepts to using workbox-precaching for our main dashboard client last week. it's way more stable but i hate how much the build time bloats when you have a lot of small icons. before, we were just letting the browser handle it and it was a total mess whenever the connection dropped mid-load.
>the app just shows a blank white screen
now at least the shell loads every time, even if the data is stale. still struggling with purging the old cache when we push a new version of the assets though. anyone else dealing with massive cache sizes on mobile?

been looking at some recent campaign data and noticed the revenue numbers for our main flows are totally off.
>revenue looks massive compared to last month
it's clearly just a tracking glitch with how it's counting last-click conversions instead of actual unique orders. anyone else seeing weirdly inflated numbers in their dashboard lately?

separating the attempt from the actual business effect is just common sense but someone's writing long posts about it like it's some grand discovery. if we don't track the original intent and just keep spawning new workers with fresh IDs, we're gonna end up with duplicate way too many production items in the database.

more here: https://dev.to/rkrisa/a-retry-needs-an-identity-not-just-another-attempt-17a0

was looking at the recent checkout data for that retail client and the numbers are totally out of sync with stripe. it's not even a small gap anymore because GA4 is totally lagging by like forty-eight hours on some events. i'm starting to think we can't trust any single dashboard for real-time decision making until they fix their processing latency. has anyone actually seen a consistent delay like this on a different property?