Web layers & on-site personalisation

Your website is a channel too. Web layers are popups, banners, slide-ins and embedded content blocks that appear for the right visitor — decided by the same CDP profile and segments used for messaging.

How it works

1. Build a layer in Content → Web layers: pick a layout, write the content, style it (it inherits nothing from your site's CSS, so it looks the same everywhere).
2. Target it: which segment sees it, on which URLs, after how many seconds/scroll depth, and how often (e.g. max once per week per visitor).
3. Publish. The site snippet (the same one used for event tracking) asks the decision endpoint what to show.

The decision call

The browser asks, the server decides — targeting logic and segment membership never leak to the client. The snippet sends a GET request with your public tracking key (key, a wz_pk_… key, required) and the visitor's identifiers — email if known, otherwise the anonymous id in anon:

GET /v1/web/decide?key=wz_pk_…&anon=anon_8f3…&email=jane@example.com
→ { "layers": [ { "id": "wl_exit_10", "content_html": "…", "trigger": "exit_intent", "delay_seconds": 0, "position": "…", "frequency": "…" } ] }

An anonymous visitor who later identifies keeps their history — the profile is merged, and segment targeting applies retroactively.

What teams build with it

• Exit-intent offer for visitors with a non-empty cart who are not in the "purchased last 30 days" segment.
• Newsletter bar shown only to visitors not yet subscribed (why nag your subscribers?).
• VIP banner for the high-CLV segment, hidden for everyone else.

Impressions, closes and clicks are recorded as events, so a layer can trigger a journey — e.g. "clicked the offer but didn't buy within 2 hours → send the reminder SMS".