惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

大猫的无限游戏
大猫的无限游戏
U
Unit 42
T
Tailwind CSS Blog
罗磊的独立博客
WordPress大学
WordPress大学
小众软件
小众软件
Recent Announcements
Recent Announcements
博客园 - 聂微东
Jina AI
Jina AI
云风的 BLOG
云风的 BLOG
博客园 - 【当耐特】
爱范儿
爱范儿
Microsoft Azure Blog
Microsoft Azure Blog
GbyAI
GbyAI
V
V2EX
博客园 - 三生石上(FineUI控件)
I
InfoQ
雷峰网
雷峰网
G
Google Developers Blog
阮一峰的网络日志
阮一峰的网络日志
B
Blog
腾讯CDC
A
About on SuperTechFans
博客园 - 叶小钗

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Naver Brand Search shows 5 –9 LTV:CAC and it's the least ...
강해수 · 2026-06-19 · via DEV Community

강해수

Naver Brand Search returns 5×–9× LTV:CAC on every Korean D2C account I operate. It also tells me almost nothing useful about growth. You're not acquiring customers there — you're recapturing people who already decided to buy. Counting it as an acquisition channel inflates your portfolio average and makes cold prospecting look broken by comparison when it isn't.

The 3× LTV:CAC rule is a VC heuristic built for SaaS — stable subscription contracts, clean sales CAC. Neither condition holds in Korean skincare or apparel D2C, where repurchase cycles are discount-driven, Cafe24 checkout events don't always fire cleanly, and iOS 14.5 attribution still hasn't stabilized. Most brands I've worked with are running 12-month projected LTV with a 30–50% confidence interval baked in and calling it a number. That's a forecast with a nice label.

Here's where the ratio actually lands across my accounts after 90-day cohort pulls: Meta cold prospecting sits at 1.8×–2.4× (iOS signal loss compresses apparent LTV), Meta retargeting looks great at 4×–7× until frequency decay kills it around week 6, Naver Shopping PLA runs a consistent 2.8×–3.5× on repurchase categories like supplements and skincare refills, and Google PMax in Korea routinely lands at 1.5×–2.8× because it over-spends on brand keyword traffic you were going to capture anyway. The 3× threshold holds on Naver Shopping PLA for repurchase-heavy categories — I've run ₩15M–₩30M/month there and it's reliable enough to use as a scale trigger. It breaks on PMax almost every time I've tested it in this market.

The other place it breaks quietly: second purchases driven by a 20% retention coupon. If that discount cost isn't inside your LTV calculation — and most attribution setups I've seen don't include CRM discount spend consistently — the ratio looks fine while the margin doesn't.

I wrote up the full breakdown — including where Google PMax specifically misfires on Korean D2C and how to adjust your LTV:CAC floor by channel instead of using one number across all spend — over on themedilog.

Full post →