Website personalisation works by collecting data about individual visitors and using it to dynamically adjust the content, messaging, or layout they see in real time. Rather than showing every visitor the same page, a personalised website experience for visitors responds to signals like behaviour, location, referral source, or known profile data to deliver a more relevant experience. The sections below unpack the key questions marketers ask when getting started with personalisation.

What types of data does website personalisation use?

Website personalisation draws on three broad categories of data: behavioural data (what a visitor does on your site), contextual data (how and where they arrived), and profile data (what you already know about them). Each category adds a different layer of relevance, and the combination of all three produces the most accurate personalisation.

Behavioural data includes pages visited, time on site, links clicked, forms submitted, and products viewed. Contextual data covers the referring channel (such as an email campaign, a paid ad, or organic search), device type, geographic location, and the time of visit. Profile data typically comes from a CRM, a customer data platform, or a previous form submission and may include job title, company size, industry, or purchase history.

The richest personalisation happens when these data types are connected. A visitor arriving from a B2B email campaign who works in financial services and has previously downloaded a whitepaper is a very different prospect from a first-time visitor arriving via a Google search, and the website experience should reflect that difference.

How does a website recognise a returning visitor?

A website recognises a returning visitor primarily through browser cookies, which store a unique identifier on the visitor’s device after their first visit. When they return, the site reads that identifier and retrieves the associated behavioural history. For known contacts, recognition can also happen through email link tracking, login sessions, or form pre-fill data.

Anonymous visitors are tracked at the session level using cookies or local storage. Once a visitor identifies themselves by clicking a tracked email link or completing a form, their anonymous history can be merged with their known profile, creating a continuous picture of their journey. This process is sometimes called identity resolution.

It is worth noting that cookie-based recognition has limitations. Users who clear their cookies, switch browsers, or use private browsing mode will not be recognised. This is one reason why encouraging visitors to identify themselves early through gated content or newsletter sign-ups remains a valuable strategy.

What is the difference between rules-based and AI-driven personalisation?

Rules-based personalisation shows specific content when predefined conditions are met, such as “if the visitor is from the Netherlands, show the Dutch-language banner.” AI-driven personalisation uses machine learning to identify patterns across large datasets and predict what content is most likely to engage or convert a given visitor, without requiring manually configured rules for every scenario.

Rules-based personalisation

Rules-based systems are straightforward to set up and easy to audit. You define the logic yourself: segment A sees version X, segment B sees version Y. This approach works well when your segments are clearly defined and stable, and when the personalisation logic is relatively simple. The limitation is that rules do not scale easily. As your audience grows and your content library expands, maintaining hundreds of rules becomes time-consuming.

AI-driven personalisation

AI-driven systems analyse visitor behaviour across the entire audience and surface content recommendations or layout variations based on predicted relevance. They adapt automatically as patterns change, which means less manual maintenance. The trade-off is that the decision logic is less transparent, and you need sufficient data volume for the models to produce reliable predictions. Many platforms combine both approaches, using rules to set guardrails and AI to optimise within them.

What website elements can actually be personalised?

Almost any visible element of a webpage can be personalised, including headlines, hero images, calls to action, navigation items, product recommendations, testimonials, banners, and entire content blocks. Personalisation can also extend to overlays, pop-ups, and chat prompts that appear based on visitor behaviour or profile.

In practice, the highest-impact elements to personalise are those that carry the most persuasive weight. Headlines and hero sections are seen by virtually every visitor and set the tone for the rest of the page. Calls to action are directly tied to conversion, so matching the CTA copy to the visitor’s stage in the buying journey can meaningfully lift click-through rates. Product or content recommendations personalise the discovery experience, helping visitors find what is relevant to them faster.

Structural personalisation, such as reordering navigation items or showing different page templates to different segments, is also possible but typically requires more technical investment. Most teams start with content-level personalisation and expand from there as they build confidence and data.

How does website personalisation connect to email and CRM data?

Website personalisation connects to email and CRM data through a shared contact identifier, usually an email address or a CRM contact ID. When a visitor clicks a tracked link in an email, the personalisation platform recognises them and can immediately apply content rules based on their CRM profile or email engagement history, without requiring them to log in.

This connection enables campaign continuity. A visitor who received an email about a specific product category can land on a page that reflects that same message, rather than a generic homepage. Equally, the behavioural data collected during that website visit can feed back into the CRM or customer data platform, enriching the contact record and informing future email segmentation.

The tighter the integration between your website personalisation tool, your email platform, and your CRM, the more coherent the customer experience becomes across touchpoints. Fragmented tools that do not share data break this continuity and force marketers to manage disconnected journeys.

Does website personalisation affect GDPR compliance?

Yes, website personalisation involves processing personal data and therefore falls within the scope of the GDPR. Collecting behavioural data, building visitor profiles, and using that data to serve tailored content all require a lawful basis for processing, appropriate transparency in your privacy notice, and in most cases, valid cookie consent before tracking begins.

The key compliance considerations are:

  • Cookie consent: Personalisation cookies are typically classified as functional or targeting cookies and require explicit opt-in consent under GDPR and the ePrivacy Directive.
  • Transparency: Your privacy policy must clearly explain what data is collected, how it is used for personalisation, and how visitors can object or withdraw consent.
  • Data minimisation: Only collect and retain the data that is genuinely necessary for the personalisation you are delivering.
  • Data storage: Storing visitor and profile data within the EU avoids the additional compliance complexity of international data transfers.

Choosing a personalisation platform that is built in Europe and certified to ISO 27001 significantly reduces compliance risk, as the infrastructure and default settings are designed with European data protection law in mind.

How do you measure whether website personalisation is working?

Website personalisation is working when personalised experiences outperform default experiences on metrics that matter to your business, such as conversion rate, time on page, bounce rate, or form completions. The most reliable way to measure this is through A/B testing, where a segment of visitors sees the personalised version and a control group sees the standard version, and results are compared over a statistically meaningful period.

Beyond A/B tests, useful metrics include:

  • Conversion rate by segment: Are the segments you are personalising for converting at a higher rate than comparable visitors who received generic content?
  • Engagement depth: Do personalised visitors view more pages, spend more time on site, or engage with more content?
  • Return visit rate: Does personalisation increase the likelihood that a visitor comes back?
  • Campaign alignment: For visitors arriving from email campaigns, does matching the landing page to the email message improve the conversion rate compared to sending them to a generic page?

It is also worth tracking the performance of individual personalisation rules or AI recommendations over time. A rule that was effective six months ago may become less relevant as your audience or product offering changes. Regular review and iteration are as important as the initial setup.

How Spotler helps with website personalisation

We built Spotler Website Personalisation to give every visitor an experience that genuinely matches who they are and what they are looking for, without requiring a team of developers to maintain it. As part of Spotler Activate, it connects directly to our CDP, email marketing automation, and the broader Spotler Marketing Cloud for B2B, so the data flowing through your campaigns and CRM immediately informs what visitors see on your website.

Here is what you can do with Spotler Website Personalisation:

  • Dynamically adjust content blocks, overlays, and calls to action based on company data (industry, company size), click behaviour, and stage in the customer journey.
  • Automatically show campaign-aligned content to visitors arriving from a specific email, so the message they clicked on continues seamlessly on your site.
  • Build enriched visitor profiles in the background that feed back into your email segmentation and other channels.
  • Run A/B tests to measure exactly which personalisation approach works best for each audience segment.
  • Work within a fully GDPR-compliant, ISO 27001-certified European platform, so compliance is built in rather than bolted on.

If you are ready to move beyond one-size-fits-all web experiences, speak to our team to see how Spotler Website Personalisation can work for your organisation.

Frequently Asked Questions

How much data do I need before website personalisation is worth implementing?

There is no universal threshold, but rules-based personalisation can deliver value from day one, even with modest traffic, as long as your audience segments are clearly defined. AI-driven personalisation typically requires a higher data volume — most platforms need thousands of sessions per segment before machine learning models produce reliable predictions. A practical starting point is to focus on your highest-traffic pages and your most distinct audience segments, then expand as your data grows.

What are the most common mistakes teams make when starting with website personalisation?

The most frequent mistake is trying to personalise everything at once, which spreads effort thinly and makes it difficult to measure what is actually working. Another common pitfall is building personalisation rules based on assumptions rather than data, resulting in content that feels generic or even off-putting to visitors. Starting with one or two high-impact use cases — such as tailoring the homepage hero for visitors arriving from a specific email campaign — and measuring rigorously before scaling is a far more effective approach.

Can I personalise my website for anonymous visitors, or does it only work for known contacts?

Personalisation works for anonymous visitors too, using contextual signals such as referring channel, geographic location, device type, and in-session behaviour. For example, a first-time visitor arriving via a paid LinkedIn campaign can be shown industry-specific messaging based on that referral context, even before they have identified themselves. The experience naturally becomes richer once a visitor converts to a known contact, but contextual personalisation alone can meaningfully improve relevance from the very first visit.

How do I make sure my personalisation does not feel intrusive or "creepy" to visitors?

The key is to use data to improve relevance rather than to demonstrate how much you know about someone. Personalising a headline to reflect the industry a visitor works in feels helpful; referencing specific personal details they did not knowingly share tends to feel unsettling. Keeping personalisation contextually relevant, obtaining proper cookie consent, and being transparent in your privacy policy about how data is used all contribute to an experience that feels tailored rather than surveilled.

How long does it typically take to set up and see results from website personalisation?

A basic personalisation setup — such as showing campaign-aligned content to visitors from a specific email or adjusting a CTA based on industry — can be live within a few days on a modern platform, assuming your data integrations are already in place. Seeing statistically meaningful results from A/B tests typically takes two to four weeks, depending on your traffic volumes. More complex use cases involving AI-driven recommendations or structural page changes will naturally require more time to configure, test, and optimise.

Does website personalisation require developer resource to maintain on an ongoing basis?

Not necessarily. Most modern personalisation platforms are designed for marketers to manage independently, with visual editors and no-code rule builders that do not require developer involvement for day-to-day changes. Developer resource is more likely to be needed during the initial integration phase — connecting your CRM, CDP, or email platform — and for any structural personalisation that involves changing page templates or layouts. Once the foundation is in place, marketing teams can typically create, adjust, and test personalisation rules without engineering support.

How does website personalisation interact with SEO — could it negatively affect my search rankings?

When implemented correctly, website personalisation does not harm SEO. Search engine crawlers see a consistent, default version of your pages, while personalised content is served dynamically to human visitors based on their session data. The important principle is to avoid cloaking — that is, serving fundamentally different content to crawlers than to users — which violates search engine guidelines. Sticking to content-level personalisation (swapping headlines, CTAs, or content blocks) rather than serving entirely different pages to different audiences keeps you well within SEO best practice.