Convert.com

Go and split your conversion rate by device. If the gap bothers you, Craig Smith has an explanation. Buy something from your own store on your phone. One hand, standing up. Congratulations, you’ve just met your average customer. Whatever annoyed you in those ninety seconds is what Craig Smith is spending an hour on. He’s been optimizing retail stores for twenty years and puts the gap between mobile and desktop at about half. What’s in it: → Why the gap exists. Thumb reach, load times, form friction, payment options. → A framework for hypotheses that are genuinely mobile-specific, rather than desktop ideas on a smaller screen. → Why blended conversion rate hides the problem instead of showing it. → An OuterBox case study on reworking checkout flow, auto-fills and one-click payments for mobile traffic. → Live Q&A. Craig’s Chief Strategy Officer at OuterBox and teaches web optimization at Harvard and NYU. 21 October, 1:00 PM EDT / 7:00 PM CEST Register today: https://lnkd.in/djt_Z7sS

You can now code an A/B test on Shopify with one prompt to Claude. No designer. No developer. No week in the dev queue. Convert.com's MCP is how. Connect it to Claude once, describe the test in plain English, and Claude reads your live page, writes the variation, and creates the experiment inside Convert. The build that took a designer, a developer, and a week now takes minutes. You stay the one who hits go. What's inside the guide: ↳ The one-prompt loop: idea, Claude builds it, draft in Convert, you QA and start ↳ 10 pre-vetted tests you can build in one prompt each, with the lift we have actually seen (+8.44%, +10.04%, +9.67%) ↳ The fast-path prompt template, copy-paste ready, with the two safety lines ↳ The Figma path for real redesigns, section by section, never a full-page swap ↳ The read-the-result prompt: lift, confidence, significance, in plain English ↳ The guardrails, and exactly what to hand your devs before you give it write access 𝗜𝗳 𝘆𝗼𝘂 𝗿𝘂𝗻 𝗔/𝗕 𝘁𝗲𝘀𝘁𝘀 𝗼𝗻 𝗦𝗵𝗼𝗽𝗶𝗳𝘆 𝗮𝗻𝗱 𝘄𝗮𝗻𝘁 𝘁𝗵𝗲 𝗲𝘅𝗮𝗰𝘁 𝗽𝗹𝗮𝘆𝗯𝗼𝗼𝗸: Like this post Comment "CONVERT" And I'll DM it.

When choosing the right A/B testing tool, the demo call is crucial. Because during that call, your job is not to be impressed. Your job is to decide what is best for your organization, your colleagues, and yourself. Recently, I created a video series on choosing the right A/B testing tool. This video covers one of the most important parts of the process: the demo call. A few things I always recommend: 🔹 Share your requirements and technical information before the call 🔹 Bring a developer to the call (also for internal support) 🔹 Focus on your real workflows, not ideal scenarios 🔹 Pay attention to limitations and trade-offs 🔹 Think about how easy the tool will be for others to use every day The best demo is not the one that impresses you most. It's the one that helps you make the best decision. The other videos in the series can be found here: https://lnkd.in/eZX2VeCc --- 🤩 More experimentation tips or questions? 🤝 I help organizations embed experimentation for better decision-making. ✉️ Or join 2,000+ subscribers to my CRO Tips newsletter.

We just gave Claude the ability to launch A/B tests end to end. No designer. No developer. One prompt. Convert.com's MCP is how. Connect it to Claude once and a test goes from a hypothesis in your head to a live experiment in minutes. Things one prompt now does: ↳ Launch a PDP hero test in 1 prompt ↳ Audit account health ↳ Pull this week's test results ↳ Write the post-mortem on a losing test ↳ Build the 90-day roadmap What's in the playbook: ↳ 6 launch templates (PDP, cart, ATC, pricing, free-shipping bar, sticky mobile CTA) ↳ 6 ops prompts (account health, velocity, experiment status, post-test analysis, guard-metric watch, weekly winner tracker) ↳ The full setup (Locations, Shopify Revenue goal, project context paste) ↳ The Mon/Wed/Fri rhythm that chains the 12 into a system 𝗜𝗳 𝘆𝗼𝘂 𝗿𝘂𝗻 𝗔/𝗕 𝘁𝗲𝘀𝘁𝘀 𝗼𝗻 𝗦𝗵𝗼𝗽𝗶𝗳𝘆 𝗮𝗻𝗱 𝘄𝗮𝗻𝘁 𝘁𝗵𝗲 𝗲𝘅𝗮𝗰𝘁 𝗽𝗹𝗮𝘆𝗯𝗼𝗼𝗸: Like this post Comment "CONVERT" And I'll DM it.

Convert & AI 🤖 my view as founder … interested in alfa and beta releases? At the end of the video I’ll tell you how to join!

Choosing the right A/B testing tool takes more than a demo call. I broke the full process down into a short video series. Because I still see many teams make the same mistakes: 🔹 Relying too much on Google or AI instead of their own needs 🔹 Involving stakeholders far too late 🔹 Not thinking about how teams will actually use the tool 🔹 Ignoring future needs and switching costs 🔹 Going into demo calls unprepared 🔹 Not validating properly during the trial period The result? A tool that looks good, but doesn’t get adopted or used well. In the videos, I cover: - How to define your real needs - How to run demos that actually help you decide - How to validate a tool during a trial You can find them here: https://lnkd.in/eZX2VeCc One important reminder from the series: A tool won’t improve your experimentation maturity or increase conversion rates. The value comes from how teams work, how decisions are made, and how you learn. But do choose your tool carefully; it is a vital part of your organization’s experimentation capability, growth, and success. The page on the Convert.com website brings all three videos together. Let me know your thoughts :-) #conversionrateoptimization #cro #experimentation #abtesting