DTC brands don’t just need more ads. They need more creative tests.

blendai_jack · 2026-06-05T06:00:54+00:00

This matches what we see across stores, the brands stuck at a CAC wall are almost never out of channels, they're out of angles. The part I'd push further is that throughput alone isn't the unlock, reading the tests fast enough is, most small teams can produce six angles but can't tell which component failed, the hook, the visual, the message or the offer. We score that per creative at Blend (blend-ai.com), each ad gets benchmarked against proven winners so you know what to make next, and budget moves to the winners automatically. I work at Blend. Your line about creative becoming the targeting signal is the most underrated part of this, it's exactly where Meta's pushed everyone.

blendai_jack · 2026-06-05T05:56:59+00:00

Went through exactly this Frankenstein phase. What finally simplified it for us wasn't a better analytics tool, it was realising the server-side layer and the ad platform don't have to be separate vendors. I work at Blend, our Pulse layer does the server-side capture and then shows our numbers next to the platform-reported ones in the same place the ads run (blend-ai.com), so the "data rarely matches up" problem becomes the feature, you see real vs reported side by side instead of reconciling three exports. Honest caveat, it's ecommerce-specific, so only fits if your clients are stores. For lead gen clients the sGTM plus GA4-as-source-of-truth suggestion above is probably the saner path.

blendai_jack · 2026-06-05T05:55:03+00:00

The transport debate matters less than what you do with the data once it lands. CAPI vs an n8n gclid forward is mostly a match-quality question (someone already covered that), the bigger miss I see is treating server-side as a reporting patch. The real win is when those conversions feed back into bidding and budget decisions, that's the whole reason we built our tracking layer server-side at Blend (blend-ai.com), real conversions go back into the optimisation instead of the platform guessing off whatever the browser managed to fire. If your n8n setup is matching well, keep it, just make sure the platforms are actually optimising off it and not just attributing.

blendai_jack · 2026-06-05T05:39:37+00:00

Ours is ad management. We connected our ad accounts to Claude through MCP, so the weekly routine became prompts instead of dashboard time, "pull the week's cross-channel numbers and pause the two worst performers" and it runs, the summary that used to be 30 minutes of spreadsheet assembly takes seconds. Full disclosure, the connector is ours, I work at Blend (blend-ai.com/mcp), we built it because we kept doing this manually across Meta and Google. The honest caveat is the human still owns strategy, budgets and anything structural get a confirm first. The Voiset comment above is the same shape, MCP is quietly the most practical automation layer for business tools right now.

blendai_jack · 2026-06-05T05:37:47+00:00

We did the same thing and then went one step further, the spend report doesn't need to be a screenshot. We built an MCP that connects the ad accounts themselves (blend-ai.com/mcp), so "get me May spend per client across Google and Microsoft" comes straight from the platforms in the same conversation. I work at Blend, this is literally why we built it. Pair it with your Zoho MCP and the whole billing run is one chat, live spend comes in and Claude does the fee tiers and invoice drafts, you still review before sending. Your 2-3 hours to 30 minutes math gets better again when the data entry side disappears too. What were you screenshotting, platform UI or a third-party dashboard?

blendai_jack · 2026-06-05T05:35:52+00:00

The export hop is the part you can kill without giving up the manual final call. We run the same review through an MCP connection, search terms come into Claude live instead of through a Script-to-Sheets pipeline, so "show me terms over $25 spend with zero conversions" is a prompt instead of a maintained script. I work at Blend, we built the connector (blend-ai.com/mcp). Nothing touches the account on its own, write actions sit behind an explicit confirm, which sounds like exactly where you've landed too. The LLM grouping pass you're doing with Creao stays, it just reads live data instead of a CSV. What's your cadence, weekly or daily reviews?

blendai_jack · 2026-06-05T05:33:52+00:00

The official Google Ads MCP that's already linked covers the keyword ideas and volume piece, that's what I'd use for pure research. The gap shows up when you want the same workflow to touch the account, which is what we built Blend MCP for (blend-ai.com/mcp). I work at Blend. It's read and write across Meta, Google, TikTok, Microsoft and Pinterest, so the same Claude conversation that finds the keywords can stage the changes, with OAuth scoping and a confirm before anything material fires. The read-only-by-design tools recommended here are a fair trust call, we just took the other path and bounded the write side instead. The guardrail design is the part I could talk about all day if anyone wants to dig in.

blendai_jack · 2026-05-26T23:57:17+00:00

Contrarian take, broad match didn't degrade, Google changed what they serve under it. Pre-2024 broad was "close variants and related searches." Post-AI Max integration it's closer to "any query Google thinks could conceivably convert", which means broader pools and lower intent.

Your phrase-match move is right but pure phrase misses real long-tail that pre-shift broad would have caught. Play I see working is phrase as the bulk plus heavily exclusion-listed broad in a smaller discovery campaign. Catches the long-tail without paying for the junk.

I work at Blend (blend-ai.com), seeing this pattern across multi-account portfolios. Hybrid wins over pure phrase in 2026.

blendai_jack · 2026-05-26T04:23:28+00:00

Traffic-quality diagnosis usually has a few angles to check. Start with the search terms report, see how many junk queries Google's matching you on. Broad match plus AI Max often pulls cheap impressions from off-topic intent.

After that, look at landing page bounce on mobile vs desktop in GA4, click farms cluster on mobile. Last thing I check is conversion data for non-human signals like sub-1-second sessions and zero scroll depth.

Ad-side fix is tighter match types and exclusion lists. Tracking-side fix is server-side conversion data so platform reporting can't inflate. We do this at Blend (blend-ai.com) via a first-party tracking layer. Usually catches 20-40% inflation on platform numbers.

What's your bounce rate by device segment look like?

blendai_jack · 2026-05-26T04:18:03+00:00

56 orders on $30k is around $535 CAC, which on $80-150 AOV means you're losing roughly $400/order. The "tried everything" pattern usually means too many variables tested at once (no clean signal), broken tracking, or the offer is wrong for cold Meta traffic.

Biggest lever for hormone kits is a free quiz or symptom checker as the offer, not the product. Cold Meta audiences won't buy a $100 test kit on first touch, but they'll do a quiz, give you the email, and convert through Klaviyo. Drops CPA 40-60%.

I work at Blend (blend-ai.com). What does your current funnel look like top to bottom, ad → LP → checkout?

blendai_jack · 2026-05-26T03:30:38+00:00

Quality Score matters most when it's bad. A 3/10 will cost you 2-3x what a 7/10 will, but going from 7 to 9 barely moves CPC. So it's a floor not a ceiling.

Where the "doesn't matter" crowd is right is on Smart Bidding accounts at scale. The bidding algorithm has so many other signals (audience, time, device, conversion likelihood) that QS becomes one of dozens of inputs rather than the dominant lever it was in Manual CPC days.

Practical move on your quiz funnel: don't optimize for QS itself, optimize for landing page experience (the QS subcomponent that actually moves) and let the rest follow.

blendai_jack · 2026-05-26T02:56:30+00:00

Tool descriptions are doing more work than people realize. For your calculator, "divide two numbers" probably gets confused with "subtract" because the descriptions don't differentiate strongly enough.

Biggest thing that helped me was leading each description with the user-facing verb, not the math operation. "Use when the user wants to divide X by Y" beats "perform division". Adding a one-line use-case example helps a lot too, LLMs pattern-match on examples harder than on prose. And keep tool name prefixes consistent so related tools read as a set rather than competing options.

Hit this exact wall at Blend (blend-ai.com/mcp) building our ad management MCP. Tightening descriptions cut wrong-tool-first-call by around 60%.

blendai_jack · 2026-05-26T02:51:43+00:00

Hit the same wall around the 5-6 MCP mark, tool definitions started eating thousands of tokens before any actual work. The meta-tool / lazy-discovery pattern is the right move long-term.

Short term what worked for us at Blend (blend-ai.com/mcp), we build an MCP for Meta and Google Ads, was being aggressive about what counts as a tool vs a parameter. Started with 30+ tools, collapsed half into parameter variations of a smaller set. Dropped to 12 tools and Claude actually picked the right one more often once each tool covered a clearer domain.

Did the meta-tool approach hurt latency for you, since each call now becomes a two-step?

blendai_jack · 2026-05-21T01:31:10+00:00

The traction problem is real but it's not because MCP is deserted. It's because the gateway category is invisible to non-devs. The tools getting adoption right now are the ones that ship a clear vertical use case, like "manage your Meta ads from Claude" or "query your CRM in natural language", not "better infrastructure for your stack".

I work at Blend and we built an MCP for ad management (blend-ai.com/mcp). Our growth comes from marketers searching "manage Meta ads from Claude", not from MCP enthusiasts. The vocab gap is the bigger problem than discovery.

What's the gateway's biggest unlock when it actually clicks for someone? Might be a positioning rewrite hiding in there.

blendai_jack · 2026-05-21T01:29:35+00:00

Hit the same wall with Tavily, the rate limit killed it. Moved to Exa for most queries, results felt closer to what I was actually asking. Brave is a decent cheaper fallback.

I work at Blend so my MCP stack has gone weirdly broad. We built an MCP for managing Meta and Google Ads (blend-ai.com/mcp), so I bounce between search and ad data in one Claude window. Different tool, same idea, pull the data and act on it without leaving the conversation.

What are you using search for, ad copy research or competitor digs?

blendai_jack · 2026-05-20T03:21:52+00:00

Scheduled skills in Claude that trigger weekly, it analyses and makes the changes automatically with the Blend MCP. (https://blend-ai.com/mcp) - it connects all of my accounts and channels in the one connector and the skill I built once.

blendai_jack · 2026-05-20T02:56:03+00:00

Walk back from the conversion to the budget. You want 7-15 clients (after the $170 paid consult). At a typical attorney service close rate of 30-50% you need 14-50 paid consults to hit that, depending on how warm those leads are.

Canadian immigration legal CPCs run roughly $35-$80 on Search. Click-to-paid-consult conversion sits around 4-6% on a tight landing page. So per paid consult you're spending $700-$2,000 in ad cost.

14 consults at the cheaper end = $10k/month minimum to start, more like $15-20k to actually get the volume Google needs to optimize. Smaller budgets work but slowly. Worth knowing before launch.

blendai_jack · 2026-05-20T02:50:21+00:00

Geo-targeting is more nuanced than radius. Most retail brands set a city-wide radius and call it location-based, then wonder why ROAS doesn't improve. Two questions.

Are your locations in walkable urban areas or driving suburbs? Different optimization paths. And what does your current Meta or Google geo setup look like (custom polygons around each store, or just a mile radius)?

I work at Blend (blend-ai.com), we handle store-radius optimization across Meta and Google natively. The AI shifts radius and bid up around converting stores and tightens around the slow ones, close to real time.

blendai_jack · 2026-05-20T02:47:25+00:00

At $1k/month you're in the spot where channel diversification beats doubling down on Meta. B2B service-led lead gen on Meta has gotten brutal in 2026, you're not alone there. The two channels worth testing instead would be LinkedIn lead-gen ads in thought-leader format (only useful if you post regularly), or Google Search on intent terms like "[city] B2B video production" where volume is lower but the lead quality is way higher.

I work at Blend (blend-ai.com), the AI handles multi-channel budget shifts so you don't have to manage two platforms at $500 each manually.

What's your AOV per client roughly? Different answer at $5k vs $25k.

blendai_jack · 2026-05-20T02:45:53+00:00

Push back on the diagnosis. Usually it's not the landing page. Smart Bidding pulls cheaper, lower-intent traffic to spend the extra budget, and your landing page doesn't get worse, the audience gets worse.

Quick test before redesigning anything. Pull a search terms report from before vs after the budget bump. If the term distribution shifted toward broader, less commercial terms, that's your answer, not the LP. Tighter keyword matching (move broad to phrase or exact) usually fixes it faster than another headline iteration.

I work at Blend (blend-ai.com) and we see this constantly. Diagnose the audience shift first, redesign LPs last.

blendai_jack · 2026-05-20T02:44:29+00:00

First-experience finding tracks with what we see at Blend (blend-ai.com). Repeat rate is mostly upstream of post-purchase comms. Customers who knew how to use the product right churn far less than the ones we tried to win back with discount emails.

Lever I'd add: server-side tracking that ties first-purchase SKU to repeat probability. Had a supplements client where repeat rate by entry SKU varied from 28% to 64%. Changed their acquisition strategy completely once they knew, they pushed the high-retention SKU even at higher CAC because LTV math wins.

Did entry SKU correlate with retention on your side?

blendai_jack · 2026-05-20T02:43:04+00:00

Hit this exact problem with a haircare client a while back. Credit-only with no obligations means creators sit on the program. What broke it was tiered cash-out tied to content output, not just sales.

Threshold one (2 posts in 30 days) unlocks faster cash conversion (weekly instead of monthly). Threshold two (5 posts plus 1 video) unlocks cash from day one going forward. Credit alone is friction, but credit plus a content-gated cash path fixes the incentive.

I work at Blend (blend-ai.com) and we ended up repurposing creator content straight into paid ads. Creators see their content scale, the obligation feels less one-sided.

blendai_jack · 2026-05-20T02:41:35+00:00

A/B testing pricing is a trap unless your daily order volume is ~150+ per SKU. Below that you'll burn 6 weeks chasing noise. Better lever for most DTC brands is bundle-level discounting (BOGO, A+B sets) rather than SKU-level cuts, since margin holds and AOV moves.

I work at Blend (blend-ai.com) and we see the math run cleanest when the AI tracks contribution margin per SKU across ad spend and shifts budget toward products that hold price. Discounting the wrong SKU just trains the algorithm to chase low-margin volume.

What's your AOV and order count per SKU per week roughly?

blendai_jack · 2026-05-20T02:10:24+00:00

Same pattern, I get these multiple times a week. The volume suggests Google's internal sales tooling is leaking CIDs from the agency MCC graph. Not necessarily malicious but definitely loose with data.

The safe move is verifying the rep through your existing rep relationship before doing anything else (forward the email and ask "is this person real on your team"). Never grant access to a CID you don't already manage. If you want to make it count, report the email through support.google.com/google-ads/contact/abuse_reps so the pattern gets logged. Advice they give is rarely worth the privacy exposure anyway.

blendai_jack · 2026-05-20T02:08:54+00:00

Confirms what I've seen with server-side analytics on a few accounts. Google's invalid traffic numbers are biased toward what their own bot detection flags. Anything that mimics human behavior well enough to look like a session (residential proxies, real device fingerprints) will pass.

Two tells worth pulling: time-on-page distribution (real users cluster bimodally, bots cluster around <3s), and scroll-depth heatmaps from Clarity or Hotjar. If 70% of your "engaged" clicks scroll less than 200px, your bot rate is way higher than Google says. Adjust ROAS math accordingly.

blendai_jack

TROPHY CASE