Control exactly which components appear on every page

Spectare now lets you decide exactly which content components are allowed to appear on your site, and you can now narrow or widen that control by audience type and funnel stage without touching any code. Inside the Personalisation Settings panel, each component can be enabled or disabled globally, and you can also specify which visitor audiences and buying stages it should appear for. A testimonial component can be restricted to decision-stage executive visitors, while a technical deep-dive can be limited to developers in the consideration stage.

This works by replacing the platform defaults for your workspace specifically. The registry ships with sensible defaults for every component, but your per-org overrides take precedence entirely when set. You can use the wildcard setting to open a component to all audiences or all stages if you want it to appear everywhere regardless of intent.

The practical effect is that your content assembly becomes far more predictable. Rather than relying solely on the AI to decide what fits, you set the boundaries and the AI works within them. A component that should never appear in an awareness context simply will not, no matter what the visitor signal looks like.

This level of control matters most for teams with brand guidelines around what content is appropriate at each stage of the funnel. You write the rules once in settings, and every personalised page respects them automatically.