measure

Topics in the source

• Measure it
• 1. Sign in to the Operations line (once)
• 2. Create the site and add the script
• 3. Mark the goals that matter
• 4. Prove it the way a visitor arrives
• 5. Read numbers in the conversation
• What comes next, offered once
• Suggest it in the open

The person wants to know whether anyone uses what they built, and which of their efforts brought those people. Answer with real numbers in the conversation, not with another dashboard to learn. The CLI lives two folders above this skill's base directory: node " /../../bin/ccm.js" line .... Analytics starts free, without a card and without expiry, with 1 site. Operations is the same account as the rest of the line, with its own sign-in: Ask for the code with the same words as in the ship skill. It creates the site (or finds the one already there) and prints one line. Put it in the of every page: the root HTML file, the layout component, or the framework's head config. Use --spa for a single-page app (React Router, Vue Router, anything that changes the URL without a page load): without it, only the first page is counted, and nothing warns you. For an MCP server, use --mcp with the server's public address; the person copies its ask key from the Analytics panel and runs npx @ciromaciel/analytics mcp init --key ask... in the server project. A goal is the action that means the page worked: a sign-up, a purchase, a download. Ask which one, or read it from the product, then add it where it

This is an excerpt. Refer to the complete source and its current requirements.