This is the way a new account gets from sign-up to the first signal of the widget. The film below shows it on the real dashboard, silent and with short captions. The text under it says the same in words, so you can follow along without playing the film.
The film in short
The film starts on the start page, registers an account, answers the setup assistant and ends when the dashboard shows that the widget is reporting. It runs on a test page with sample data; nothing in it belongs to a real customer. It has no sound and does not start by itself.
Step 1: create the account
Registration has two screens. First your email address and the tick that confirms the terms, the privacy policy and the data processing agreement. Then your name, your company and a password. You confirm the address with the link in the email we send; only then can you sign in.
Step 2: tell the assistant what your site is built with
The setup assistant opens by itself. Its first question is “What is your site built with?” — WordPress, Next.js, HTML or something else — and then what your server runs: PHP, Node.js, Python, Go or no backend of your own. From here on it only shows the code that applies to your stack. With WordPress the plugin covers both halves in one step.
Step 3: create the key and enter your domain
Two fields, and the second one fills itself: the domain of your site and a name for the key that only you see. You also choose what the key should protect, and you can change that later. The key is bound to the domain you enter.
Step 4: put the widget in
One line of code embeds the widget in your page; the assistant shows it for your stack. Read the note next to it: the widget alone only shows a score. Protection is complete when your server also checks the result, and without that check anyone can still send your form directly.
Step 5: check that it reports
Open the page with your form once in the browser. The assistant waits with you until data arrives and then lights up “Widget is reporting”. The second light, “Server verifies the nonce”, stays off until your server has asked for a verdict; until then the form is not protected. Confirming the domain with a DNS entry is optional.
What comes next
After the check the assistant asks which forms should be protected and offers a few small settings. Once visitors reach your form, how to read the result shows where to look in your dashboard.