LEGACY INTEGRATIONS
Legacy email & AI summaries
Configure checkout digests and event summaries in the Pro add-on.
In this guide 3 sections
This preview’s digest covers the legacy checkout categories. Digests contain fixed category counts and a link to the site’s admin area, without recording payloads or session notes. Digests are deduplicated to at most once per 24-hour interval after acceptance. Notifications start disabled.
- Configure and test your WordPress mail transport.
- Open Legacy checkout → Legacy checkout notifications & AI and enable the daily email digest. Enter an authorised recipient and a minimum affected-recording threshold.
- Save workspace settings. Saving does not itself send an email. The scheduled digest runs through WordPress cron.
- Check the mail status and verify actual inbox delivery. Transport acceptance alone does not prove delivery.
This preview summarises legacy checkout evidence only. It does not summarise ordinary click and scroll activity or the visual replay. A recording without checkout signals has no evidence for this tool.
The request sends fixed event categories, counts and relative timing. It excludes DOM content, page paths, notes, raw order IDs and customer details. Usage is charged to the connected API account; the plugin caps requests at 20 per UTC day.
Outputs must cite existing evidence references, but a cited interpretation can still be wrong. ClickClue does not automatically change a store or establish a diagnosis.
Requests use store:false. That setting is not a promise of zero provider retention; check your account’s data controls.
- In Legacy checkout → Legacy checkout notifications & AI, enter your OpenAI API key and a Responses-compatible model. Enable manual AI summaries and save.
- Open a recording with legacy checkout signals. Expand Legacy checkout AI summary and read the processing description. Choose Summarise checkout with OpenAI only when you want to send that evidence.
- Review the interpretation and use its evidence buttons to inspect the corresponding signals.
Remove OpenAI key disables further processing. Disable email to stop future digests. Keys and application passwords are encrypted with authenticated encryption and WordPress salts; changing those salts can require reconnecting.