Installing
Node.js is too old. Setup needs Node 22 or later. Check with node --version.
Your login has several Cloudflare accounts. Pass one: npx datapenny deploy --account <id>.
It asks for a workers.dev subdomain. New Cloudflare accounts need one. Open Workers & Pages in the Cloudflare dashboard once, pick a name, and run setup again.
Signing in
The sign-in page says the password is missing or too short. The password must be 12 or more characters. Run npx datapenny password.
Sign-in says to try again later. After 10 attempts from one IP address, sign-in pauses for 15 minutes.
You forgot the password. See Reset password.
No visits showing
- The tag is missing or in the wrong place. View your page’s source and look for
data-site. - You’re testing your own site. An ad blocker may stop the script, and Setup → Your own visits may be leaving your browser out. Try a private window with blockers off.
- You’re on localhost. Add
data-devto the tag to test there. - The hostname doesn’t match. Events are accepted from the site’s domain and its subdomains.
- A Content-Security-Policy blocks it. Allow your DataPenny address in
script-srcandconnect-src.
Sales not showing
- The key can’t create webhooks. Each provider’s page lists the permissions its key needs. See Revenue attribution, or connect by hand.
- The webhook isn’t reaching DataPenny. Your provider’s dashboard shows each delivery. A 401 means the secret in Setup → Payments doesn’t match, so connect again.
- The webhook is for another site. The URL ends in the site’s id.
Sales without a source
Every unmatched sale says why. The usual cause is a server-created checkout that doesn’t pass the visitor id. See Revenue attribution. Once that’s fixed, use the Match unattributed sales again button on the Revenue page.
Still stuck
Email support@mightybench.com and mention DataPenny.