Spectare Personalisation

[spectare_slot name="primary"]
[spectare_slot name="supporting"]
[spectare_slot name="secondary"]

[spectare_slot name="primary" height="200"]

[spectare_zone zone="hero"]
[spectare_zone zone="body"]
[spectare_zone zone="proof"]
[spectare_zone zone="cta"]

Changelog

1.11.3

• All script and style output now travels through the WordPress enqueue system: the zone
  stylesheet is an inline style enqueued in the head, the conversion-attribution snippet an
  inline script enqueued in the footer, and the import page script an admin enqueue scoped
  to its own page. No raw script or style tags remain.
• Shortcode fallback content is passed through wp_kses_post on return.

1.11.2

• The Plugin URI now points to the plugin guide at spectare.ai/guide/wordpress, distinct from
  the Author URI, as the directory requires.

1.11.1

• Plugin Check pass: settings fields now escape at the point of output, the UTM reads and the
  DONOTCACHEPAGE convention constant carry documented sniff exemptions, and the renderer
  fallback notice only logs under WP_DEBUG.

1.11.0

• WordPress.org directory release. The build distributed through the directory updates via
  WordPress.org only; the self-hosted update channel is not present in it.
• New “External services” section in this readme documenting every call the plugin makes to
  the Spectare service and what data travels with it.
• Tested against WordPress 7.1.

1.10.0

• Zone pages now tell Spectare which zones they placed, detected from the page’s own
  shortcodes and blocks. The assembled content is then composed only from components those
  zones can render, so a page with just a body zone gets a fuller body instead of a hero
  and call to action it never shows. Pages the plugin cannot read (page builders, widgets)
  behave exactly as before.
• Conversions on zone pages now credit the hero image that was shown, so image selection
  can learn which images convert on WordPress sites.

1.9.0

• Zones now respect per-component zone placements set in your Spectare settings. Previously a
  zone override saved in Spectare was silently ignored on WordPress, which rendered every
  component in its default zone. If you set zone overrides, components may move to the zone
  you actually chose after this update.
• The llms.txt feature is now described as what it is: an agent entry point. A curated map of
  your content so an AI agent reading your site extracts accurate facts from a few fetches,
  rather than a visibility promise.

1.8.2

• The Spectare logo now appears on the settings page, on update rows and in the plugin
  details window, so the plugin is recognisable at a glance in a busy admin.

1.8.1

• Supporting content now renders as a compact card: the title, a one-sentence summary, and the
  full text one tap away. Pages read as pages rather than columns of full prose, and nothing
  becomes unreachable.

1.8.0

• Form conversions. Submissions through Gravity Forms, WPForms and Contact Form 7 now report a
  lead conversion to Spectare automatically, with no thank-you page or URL goal needed. Rename
  the goal with the spectare_form_goal_name filter, or disable with spectare_track_forms.
• Click goals. Clicks on phone numbers, email links and booking platforms (OpenTable, Tock,
  Design My Night, SevenRooms, Resy, Eventbrite and others) count as conversions, since those
  journeys never end on a page a URL goal could match. On by default; switch off in settings.

1.7.0

• Automatic updates. The plugin now checks spectare.ai for new versions and updates through the
  normal WordPress update screen. This is the last version you install by uploading a zip.
• WooCommerce order tracking. When WooCommerce is active and your API key is set, every paid
  order reports a conversion to Spectare with the real order total and currency, so the
  analytics and the learning loop see what actually sells. No configuration needed; disable
  with the spectare_track_woocommerce filter.
• The comparison table now carries proper header scope attributes for screen readers.

1.6.1

• The announcement zone added in 1.6.0 was missing from the block editor’s zone list and from the
  setup instructions, so the only way to use it was to type the shortcode by hand. It is now
  offered like every other zone.

1.6.0

• New announcement bar. A single line above the rest of a personalised section, for one
  time-limited fact worth knowing first: a member priority window, the last days of a run,
  under-12s free this month. Place it with [spectare_zone zone=”announce”].
• It only appears when your content actually states such a fact and carries the dates it is true
  between, so it disappears on its own when the offer ends rather than sitting there out of date.

1.5.4

• Longer content in a personalised section was cut off after four lines, mid-sentence, with no
  way for the reader to see the rest. The shortening was meant for a narrow column beside another
  block, and sections are laid out full width, so it was hiding content for no reason.

1.5.3

• Personalised sections can now hold your own content as a fallback. Write it between the tags,
  for example [spectare_zone zone=”hero”]Your normal hero copy[/spectare_zone], and it is shown
  whenever there is nothing personalised to show: if the connection fails, if you have not
  published content for that visitor yet, or before the page finishes loading. Previously those
  situations left a gap and there was no way to say what belonged there.

1.5.2

• A personalised section containing a content block this version of the plugin does not know
  how to draw used to leave a gap, with nothing in the logs to say why. It now draws the block
  as a content card and records a note, so an out-of-date plugin degrades visibly rather than
  quietly dropping content.

1.5.1

• The primary button in a call to action block was white on a white background, so on most
  themes it was invisible. It now uses your brand colour, which you can set in Settings.
• New “Brand colour” setting. Personalised sections already inherit your theme’s background and
  text colour; this is the one colour Spectare picks, used for links, labels and the primary
  button. Previously it could only be changed by overriding a CSS variable, which worked or did
  not depending on the order your stylesheets loaded in.
• Improved the contrast of the faintest text colour, which fell below the accessibility minimum
  on light themes.

1.5.0

• Atom content written with paragraphs, lists, bold or headings rendered as one unbroken block
  of text in server-rendered zones. It is now converted to HTML, matching every other way
  Spectare content is displayed.
• Added the styles that markdown content needs, including the three code styles that were
  missing, so an atom containing code no longer renders unstyled.

1.4.1

• Security fix. The page URL is sent to Spectare and shapes the personalisation, but was not
  part of the key used to cache a zone’s assembly. Because that URL includes the query string,
  two visitors on the same page with different query strings shared one cached entry, so one
  visitor could be served content assembled for another. Found by a security review. Zone
  assemblies now cache per page URL as well as per referrer, campaign and visit history.

1.4.0

• Server-rendered zones can now personalise for returning visitors. Zones are rendered on your
  server, which cannot see the page history Spectare keeps in the visitor’s browser, so a
  returning visitor previously looked new to them and got your default content. Enable
  “Returning visitors in zones” in Settings to store the visitor’s last three page paths in a
  first-party cookie on your own domain, which your server passes to Spectare. Off by default,
  because it adds a cookie: check your cookie policy before enabling. Slots have always
  personalised for returning visitors and are unaffected either way.
• Zone assemblies are cached per visit history as well as per referrer and campaign, so two
  visitors with different histories no longer share a cached zone.

1.3.1

• Atom body text in server-rendered zones is now clamped to four lines instead of printing
  the full atom. Long atoms were rendering as a wall of prose beside structured components.
  Set full on an atom in the assembly to print the whole body.
• Zone assemblies are now cached for an hour instead of a minute. At one minute the cache
  expired between visitors on lower traffic sites, so most visitors paid a cold blocking
  render and billed a personalisation. Filter: spectare_assembly_cache_ttl.
• The zone request timeout is now 15 seconds instead of 20. This call blocks the page render,
  so it stays bounded, but it has to sit above a cold assembly rather than below it: a cold
  miss is a full model call and can take 9 to 13 seconds. With the hour-long cache above, at
  most one visitor per hour per traffic source waits that long. Filter:
  spectare_assembly_timeout.
• A failed zone request is remembered for 30 seconds, so a slow or unavailable backend costs
  one visitor the timeout rather than every visitor until it recovers. Filter:
  spectare_assembly_fail_ttl.

1.3.0

• Added content import (Settings → Spectare Import): scan your published pages, pick which to import, and Spectare rewrites them into focused content atoms saved as drafts for review. Nothing is published automatically. Reads raw Gutenberg blocks where available and falls back to a heading split for classic/page-builder content. Requires your Spectare API key.

1.2.0

• Added an agent entry point: the plugin serves an llms.txt at your domain root, generated from your published Spectare content, so an AI agent reading your site extracts accurate facts from a few fetches.
• Added “Serve llms.txt” toggle (off by default) and a “Refresh llms.txt” button in Settings → Spectare.
• llms.txt is cached locally and refreshes automatically as your content changes. Requires pretty permalinks.

1.1.0

• Added server-side Zone blocks: the [spectare_zone] shortcode and Spectare Zone Gutenberg block render personalised components in named zones (hero, body, proof, cta) via server-side assembly.
• Added an API key setting (Settings → Spectare) required for the server-side zone path.
• Pages using [spectare_zone] now send a Cache-Control: no-store header automatically to prevent caching plugins from serving stale personalised content.
• Reorganised the settings Quick start into Option A (client-side slots) and Option B (server-side zones).

1.0.0

• Initial release.
• Auto-inject of Spectare widget script via wp_enqueue_scripts.
• Gutenberg block (Spectare Slot) with slot selector, custom name, and reserved height options.
• Shortcode [spectare_slot] with name and height attributes.
• Settings page with organisation slug, base URL, and auto-inject toggle.