Kaleta 2.3.0

Kaleta 2.3 answers the question site owners ask most: what brings us enquiries? Statistics now show which pages, campaigns and sites bring leads, and Claude can read the same report. Forms, embeds and an accessibility check round it off.

What brings enquiries

Statistics is now a report on leads as well as traffic:

• Pages that bring leads: views, enquiries and newsletter sign-ups, and the conversion rate of each page.
• Campaigns: visits from links with utm parameters, and the enquiries and sign-ups they brought.
• First pages of visits that ended with a lead, and the sites the visitors came from.
• Devices: phone, tablet or computer.
• Pop-ups: views, conversions and the conversion rate.
• Periods: 7, 30, 90 days or a year.

Claude reads the same report with the new get_stats tool. It returns counts only, never personal data.

Where each lead came from

Turn on Settings → Cookies → Remember where leads came from. Every enquiry and sign-up then also records:

• the first page of the visit;
• its campaign;
• the site that sent the visitor – even when the form is on a different page.

What that takes:

• It is off by default. It needs the built-in cookie bar, and turning it on adds a marketing choice there.
• Only with consent: it is remembered only for visitors who allow marketing, and only for their browser tab (sessionStorage).
• Without it: an enquiry still records the campaign of the page with the form, as before, with no storage at all.

The enquiry detail, list_enquiries and the enquiry webhook show the new fields. The webhook also sends the form's id, so Make or Zapier can route each form its own way.

Global Privacy Control: a browser that sends the signal counts as "only necessary" without the cookie bar asking.

Forms

Two new field types:

• Several ticked options: checkboxes. Required means at least one ticked; only the offered options are kept.
• Hidden value: e.g. the product the form is about. It is sent with every enquiry but never shown, and the visitor cannot change it.

Embed

A new Embed element shows a booking calendar, a form or a player from:

• Calendly;
• Google Calendar and Google Forms;
• Microsoft Forms;
• Tally, Typeform and Airtable;
• Spotify and SoundCloud.

How it works:

• Paste the address you would share, and choose the height.
• It loads only after a click, so the page sends nothing to the service before that, and no consent is needed.
• A link to the service is always next to it.
• Any other address is refused.

Code in the head of one page

Administrators can add code to the <head> of a single page, e.g. the conversion tag of a landing page:

• in Page settings → Search engines and sharing;
• over the Claude connection, with head_code of create_page and update_page, through a connection with full access only.

Accessibility in the site audit

The site audit has a new group for the European Accessibility Act (WCAG 2.2 AA):

• the colour contrast of the design system, in light and dark mode;
• links and buttons whose text does not say where they lead ("click here", in eight languages);
• images in text without a description, and empty links;
• tables without header cells, and frames without a title;
• a missing accessibility statement.

Claude sees them with site_audit, kind: accessibility.

For contributors

• Core\Report builds the statistics report for the admin and for get_stats.
• Front\Forms::attribution() checks what a form sends about its origin.
• New pieces:
  • Builder\Elements\Embed – its SERVICES and the allowlist in image/web.js are kept in step by a unit test;
  • migration 0036: lead origin columns, ka_stat_kampane, ka_stat_zarizeni, ka_stranky.kod_hlavicky.
• The recorded contracts gain get_stats, head_code and the Embed element.

Updating

Update from Settings → Backups and updates. It works from every earlier release.