B2B AI DirectoryB2B AI Directory
Website Managementpro

Website management

Website personalization rules by source, segment, account, and lifecycle stage

Design a safe personalization framework with eligibility, message variants, proof, exclusions, fallback, measurement, and governance.

Output
professional marketing deliverable
Inputs
8 required
Prompt depth
751 words

Copy-paste prompt

Replace the bracketed inputs with your real material.

You are a senior B2B web strategy and conversion lead. Produce a practitioner-ready deliverable for: Website personalization rules by source, segment, account, and lifecycle stage.

Objective
Design a safe personalization framework with eligibility, message variants, proof, exclusions, fallback, measurement, and governance.

Required practitioner depth
The work creates the scalable decision logic behind many website experiences. The work prevents contradictory or creepy personalization and defines what data quality is required before activation.
Do not collapse this assignment into a generic summary, brainstorm, or list of best practices....

[Full prompt continues for Pro members.]

Unlock the complete prompt

Pro includes the complete prompt library and every complete workflow.

View Pro options

What you provide

  • Business and buyer context
  • Current site evidence
  • Scope
  • Requirements
  • Systems and owners
  • Constraints
  • Success and rollback criteria
  • Task-specific evidence

What you receive

  • Primary deliverable that fully executes this job: Design a safe personalization framework with eligibility, message variants, proof, exclusions, fallback, measurement, and governance.
  • Practitioner-depth requirements: The work creates the scalable decision logic behind many website experiences. The work prevents contradictory or creepy personalization and defines what data quality is required before activation.
  • Buyer task, evidence, and current-state problem map.
  • Page, IA, form, personalization, experiment, launch, or governance specification with copy and system requirements.
  • Acceptance tests, monitoring, ownership, dependencies, and rollback or maintenance plan.

Quality checks

  • Do not change measurement, consent, SEO, accessibility, or routing behavior without explicit requirements.
  • Separate user evidence from internal stakeholder preference.
  • Include acceptance tests, monitoring, ownership, and rollback for launch changes.
  • Do not claim a conversion lift without an experiment or credible comparison.
  • Missing or conflicting inputs are surfaced rather than silently resolved.
  • Every material recommendation has evidence, confidence, owner, and a validation or reversal condition.