Read a widget's analytics

The Analytics tab of a widget shows what the widget did for a range of time: how many visitors it checked, how many passed, whether your server verified their tokens, and the hostnames, actions, countries, browsers and operating systems they came from. Read it when you add a widget, to see that it works, and when a widget shows up in the list with something that needs attention.

• The widget must be on your account. Any role can read its analytics.
• Analytics go back as far as your plan keeps them: 7 days on Free, 30 on Pro, 90 on Business and 365 on Enterprise (Wicket limits).

1. In the dashboard, go to Security and select Open Wicket.
2. Select the widget's name, or Open in the menu on its card.

The widget's name is the page's heading, with its mode and Active or Turned off beside it and its site key under it, with a copy button. The tabs are Analytics, Install and Settings, and Analytics is the one that opens. The address without a tab opens it too. A widget that is not on your account shows We could not find that widget.

Under the tabs, choose 24 hours, 7 days, 30 days, 90 days or 365 days. The range is in the address as ?range=7d, so a link opens the same view.

A range longer than your plan keeps shows the numbers for the days the plan does keep, and a notice above them says Your plan keeps analytics for 7 days. The notice offers the plan that allows the range you chose, with its price. Choose a shorter range, or upgrade. Enterprise keeps 365 days, so every range shows in full.

Challenges

How many visitors the widget checked in the range.

Passed

How many of those checks passed.

Failed

How many checks ended in a failure. A check that was started and never finished is in neither Passed nor Failed.

Solve rate

The share of checks that passed, with the share of the passes that needed a visitor to tick the box, such as 3% ticked the box. It reads — while there is nothing to measure.

Two charts follow, Challenges issued and Challenges passed, one point for each hour when the numbers cover 7 days or less, and one for each day when they cover more.

The Tokens verified card counts what your server did with the tokens the widget handed out, each counted when your server asked us to check it:

Valid

The token was good, and your server was told so.

Invalid

The token was not one of this widget's, or could not be opened.

Expired

The token was older than 300 seconds.

Used twice

The token had been verified before.

When the widget passes visitors and none of its tokens were verified, the card says Your server is not verifying tokens, with a How to verify button that opens the Install tab. Until your server makes the call, a script can send your form without the widget. The same warning appears above the tabs, and the list marks the widget in the same way when at least 20 checks passed in 24 hours and your server verified none (Install a widget).

Five tables rank where the challenges came from, ten rows each at most, with Challenges, Passed and Failed for each row:

• Top hostnames: the pages that showed the widget.
• Top actions: the action your page set on the widget, when it sets one.
• Top countries, Top browsers and Top operating systems: where the visitors were.

A table with nothing to rank says Nothing to show.

For a widget that is working, the Challenges and Passed figures rise as visitors load your form, Failed stays small, and Valid under Tokens verified rises with Passed.

A widget that has not seen a visitor shows No challenges yet instead of the figures, with Open Install. Open the page that holds the widget in a browser, then read the tab again.

No challenges yet

The widget has seen no visitor in the range. Check that the page loads the script and the box from the Install tab, and that the page's hostname is one of the widget's.

Your server is not verifying tokens

The widget passes visitors, but your server never asked us to verify a token. Add the call on the Install tab.

Your plan keeps analytics for 7 days

You chose a range longer than your plan keeps. The numbers shown cover the days it does keep.

Could not load the analytics

Select Try again. If it keeps failing, contact support.

• How Wicket works
• Add a widget
• Manage widgets with the API
• Wicket limits

• Install a widget to add the code that makes your server verify tokens.
• Change a widget's settings to add a hostname that a refused page needs.
• Troubleshoot Wicket when visitors fail checks they should pass.