Mobile B2B personalization tends to be an afterthought. Personalization rules get designed in a desktop browser, reviewed on a 27-inch monitor and signed off before anyone opens the variant on a phone. Then a buyer taps a link in a LinkedIn message, gets the default hero because the personalized block loaded late, and scrolls past a case study card that was squeezed into a column two words wide.
How much this matters depends on your traffic, and you should check that before reading any further. This post covers how to size the mobile opportunity from your own data, what changes when you personalize for a small screen, the CTA and form patterns that hold up on a phone, how to test variants on real devices, and the situations where mobile visits carry the most intent.
Start With Your Own Device Split
Published figures for "share of B2B traffic on mobile" vary widely and mix very different sites, so they are not much use for planning. Your analytics answers the question for your business in a few minutes:
- In GA4, open Reports → Tech → Tech details and switch the dimension to Device category. Use the last 90 days.
- Add a comparison for the traffic you actually personalize (for example, a segment of identified target accounts, or sessions from paid and email campaigns).
- Note the share of sessions and the share of key events (demo requests, contact forms) for mobile vs desktop.
- Repeat for your three highest-traffic landing pages. Mobile share is often very different on a page that gets email and social clicks than on the homepage.
Two patterns are worth acting on. If mobile is a large share of sessions but a small share of conversions, the mobile experience is probably losing people. If mobile is small overall but large on specific campaign pages, personalize those pages for mobile first and leave the rest.
Be careful with the conversion gap. Some of it is not a problem to fix: plenty of buyers read on a phone and convert later on a laptop. Check the cross-device picture before blaming the mobile page (see the metrics section below).
What Changes on a Small Screen
One personalized element above the fold, not four
A desktop hero can carry a personalized headline, a logo strip from the visitor's industry, a testimonial and a CTA side by side. On a 375-pixel-wide phone, the first screen fits the headline, a line or two of subtext and possibly a button. Decide which single element signals "this is for you" and make sure that one is visible without scrolling. In most B2B setups it is the headline, because it is the cheapest element to vary and the first thing read.
Rendering speed decides whether the variant is seen at all
Client-side personalization usually works like this: the default page renders, a script asks the personalization service who the visitor is, then swaps content. On a slower mobile connection the gap between those steps is longer, so the visitor either sees the default flash before the variant (flicker) or a blank block while it waits. Neither helps.
To check yours, open the personalized page in Chrome DevTools, set network throttling to one of the slower presets (such as Slow 4G) and CPU throttling to 4x, and record a performance profile. Look at when the variant headline appears compared with the default. Then run the same URL through PageSpeed Insights and compare Largest Contentful Paint for the personalized and default versions. If the variant noticeably delays LCP, move the decision earlier: server-side, at the edge, or at least hide only the swapped block (not the whole page) until it is ready.
No hover
Tooltips, hover-to-reveal panels and mouse-over case study previews do nothing on a touch screen. Any personalized component that relies on hover needs a tap equivalent. For tap targets, WCAG 2.2's enhanced criterion asks for at least 44 by 44 CSS pixels; it is an AAA-level criterion, but a sensible floor for primary buttons.
Short sessions, and the same buyer on another device
Mobile visits are often brief and picked up later on a laptop. A cookie set on the phone is not available on the laptop, so cookie-based segments do not follow the person. Company-level identification (reverse IP or enrichment on the network the visitor is on) and CRM-known contacts who click tracked links are the signals that tend to carry across. Plan personalization rules so that they still make sense if the visitor only ever sees one session on each device.
Layout Patterns for Personalized Blocks
Set a mobile priority order for your personalized blocks before the designer stacks them. A common order is: headline, then CTA, then proof (logo or one-line quote from a similar company), then supporting content such as a case study card. When the desktop columns collapse, blocks appear in that order instead of whatever order the grid happens to produce.
Other patterns that hold up:
- Condense, don't hide. A desktop case study card might show a headline, a two-sentence summary and a result. On mobile, show the headline and the result and put the summary behind a tap. The personalized signal (the industry name, the customer logo) stays visible.
- Short horizontal carousels for proof. If you personalize several testimonials, a swipeable row takes less vertical space than stacking them. Keep it to a few items and turn auto-advance off on touch devices, where it fights the user's own swipes.
- Keep variant copy short at the source. A headline that fits on two lines on desktop can wrap to five on a phone. Write each segment's variant with a character limit and preview it at 375 pixels before publishing.
CTAs and Forms on Mobile
If your product has a companion app, mobile visitors may be better served by an install CTA than by a demo form. Our app landing page examples show how teams handle store badges and smart app banners without losing the web conversion.
Sticky CTA, personalized by segment
The main CTA scrolls out of view fast on a phone. A slim sticky bar at the bottom keeps it reachable. Its label is an easy place to personalize, for example:
- Identified enterprise accounts: "Talk to the enterprise team"
- Smaller companies: "See plans and pricing"
- Returning visitors who viewed pricing: "Pick a demo time"
Keep the bar small enough that it does not cover content, and make sure it does not sit on top of the cookie banner or a chat widget. For more on matching CTA wording to segments, see data-driven personalized CTAs.
Shorter forms, and fewer fields to type
Typing on a phone is slow, so every field costs more than on desktop. Our guide to the lead capture form argues for asking only what you cannot look up; on mobile that argument is stronger.
- Use enrichment instead of dropdowns. If the company is identified, pre-fill company name, size and industry, or drop those fields. Show the pre-filled company with an "edit" link rather than asking the visitor to confirm everything.
- Set the right input types.
type="email"andtype="tel"bring up the matching keyboards, and theautocompleteattribute (email,name,organization) lets the phone fill stored details. - Move secondary questions later. Ask for phone number or project details on the thank-you page or in the scheduler, after the main conversion is recorded.
Measure the effect on your own traffic. Compare form start and completion rates for mobile sessions before and after, and check whether lead quality changes; a sample-size check from our A/B test sample size guide tells you how long that will take.
Click-to-call, for the segments that want it
A tel: link is one tap on a phone. For enterprise segments where a call is a normal next step, a "Call our enterprise team" button can work. For self-serve segments it usually does not: a small-company buyer who wants to try the product is unlikely to want a sales call. That is a case where segment rules prevent a bad experience as much as they create a good one.
Testing Variants on Real Devices
Check every personalized variant at three widths before launch:
| Profile | Width to test | What usually breaks |
|---|---|---|
| Small phone | 320-375 px | Long variant headlines wrapping, sticky bar covering the form, buttons pushed below the fold |
| Standard phone | 390-430 px | Flicker on slower connections, carousel swipes conflicting with page scroll |
| Tablet | 768-1024 px | Getting the desktop layout with touch input, so hover-only elements stop working |
DevTools device emulation is fine for layout. It does not reproduce real touch behaviour, real font rendering or the CPU of a mid-range phone, so open each variant on at least one physical phone before it goes live. To see a variant without being in the segment, use your personalization tool's preview mode or a URL parameter that forces it.
What to track for mobile separately
- Scroll depth on personalized pages. If most mobile visitors never reach the personalized proof block, move it up or drop it on mobile.
- Form start and completion by device. A low start rate points to the page; a low completion rate points to the fields.
- Rage taps and dead taps. Session-recording tools flag repeated taps on elements that do nothing, which usually means something looks like a link and is not.
- Cross-device return. For identified companies, how many come back on desktop within a week of a mobile visit, and do they convert there? If many do, judge mobile pages on whether they produce that return visit, not only on mobile conversions.
Where Mobile Visits Carry the Most Intent
Events
Attendees look vendors up between sessions. If you exhibit, schedule a rule for the event dates that shows visitors from the host city (or from the attendee list's companies) a hero referencing the event, with a link to book a meeting at the booth. Remove it the day the event ends. Our guide to lead capture at events covers the follow-up side.
Email and LinkedIn clicks
Check your email platform's device report: for most lists a large share of opens and clicks happen on phones. A click from a campaign email already tells you what the visitor was interested in. Pass it through UTM parameters and use them to choose the variant, so the page continues the email's topic instead of restarting on a generic homepage.
Links sent by sales
When a rep sends a link in a LinkedIn message or a follow-up email, the prospect often taps it on a phone. Give reps tracked links (with the account or campaign in the parameters) that open a page about what the rep was discussing. This is where account-level personalization is easiest to justify, because the context is explicit.
Reading on the move
Someone reading on a train is scanning, not evaluating. A "send me this case study" option that emails the content to them often fits better than a demo form, and it gives you a reason to follow up when they are back at a desk.
A Two-Week Starting Point
- Pull the device split for sessions and conversions, overall and for your personalized segments.
- Pick the one page where mobile share is highest among those segments.
- Check that page's personalized variant on a real phone and on a throttled connection. Fix flicker and layout first.
- Add a segment-aware sticky CTA and cut the mobile form to the fields you cannot enrich.
- Compare mobile form starts, completions and cross-device returns against the previous period, then decide whether to extend the changes.
If you need the company-level signal that survives a switch from phone to laptop, Markettailor's visitor identification resolves the visiting company on either device, and its segmentation lets you build the mobile rules above on top of it.