Personalise pages by traffic source

Open Google Analytics and list your top five sources for the page, by sessions. Next to each, write what the visitor was doing before the click:

• Paid search: typed a specific problem and wants a direct answer.
• LinkedIn or other paid social: was scrolling, saw a promise, wants proof that it is real.
• Email newsletter: already knows you and wants the next step.
• Organic search: researching and wants depth.
• Referral from a partner: trusts the partner and wants to see the fit.

This table is your brief. Without it, personalisation turns into guessing.

Change one or two elements, not the whole page. In order of impact:

1. Headline: repeat the promise of the ad or link that brought them.
2. Proof: show the logo, quote or number that fits that audience.
3. Call to action: a demo for paid search, a guide for social, a booking link for email.
4. Image: swap only if it improves clarity.

Keep the price, the offer and the facts the same for everyone. The aim is relevance, not different promises.

Add UTM parameters to every link you control: source, medium and campaign. For example, ?utm_source=linkedin&utm_medium=paid-social&utm_campaign=audit-offer. Keep the names consistent and lower case, and write them in a shared sheet. Without clean tags, you cannot tell sources apart.

There are three routes, from simple to advanced:

• Separate pages. Duplicate the page and change the headline and proof for each major source. Best when a source has real volume, as covered in Build segment-specific pages only where volume justifies it.
• Parameter-driven text. A small script reads a URL parameter and swaps the headline. Landing page tools such as Unbounce and Instapage offer dynamic text features, and a site on Webflow can do it with a short script added through Google Tag Manager.
• Rules in your CMS or CRM. Some website platforms, HubSpot among them, can show content by rule. Check what your plan includes.

Start with separate pages for your top source. Move to the others only when the first one pays off.

Visitors without a tag, such as those who type your address, must see a strong generic page. Write the default first, then the variants. Make sure the swapped text appears quickly, because a headline that flashes and changes after load looks broken.

Show visitors a version that is still true to the page that search engines index. Do not hide content from one group and show it to another. Keep the main promise, the URL and the facts the same, and personalise the emphasis.

Source parameters do not identify a person. Do not combine them with personal data to show someone their company name or role unless your consent set-up allows it. When in doubt, personalise by audience, not by individual.

Compare conversion rate by source before and after the change. Change one source at a time, so you know what caused the change. Use the routine from Test systematically and apply learnings. If a variant does not beat the default after a fair run, drop it and keep the page simple.

• Personalising every element and making the page hard to maintain.
• Promising different things on different versions.
• Skipping UTM parameters and relying on guessed sources.
• Forgetting a default.
• Judging a variant on a few visits.
• Making the page flicker as text swaps.

Conversion rate for the source you changed rises while the others stay flat. Bounce rate falls for that source. Your team can say in one sentence what each version is for, and keeping the variants up to date takes minutes, not days.