Goals & funnels

Define conversions in the product UI from paths and event names you already send. A goal is a rule, not a new beacon. Creating a goal does not emit extra billable events. The events that match the rule were already counted when the browser sent them.

Funnels are ordered steps of those same paths and event names. They answer whether a visit that hit step one later hit step two, inside the daily visitor hash. They do not stitch a person across days. A visitor who returns tomorrow is a new hash.

Use goals for a thank-you path or a named event such as signup_completed. Keep event names lowercase and stable. An agent querying MCP can ask for that name. It cannot invent the schema for you.

Search Console clicks are not goal completions. A SERP click and an on-site conversion are different events. Report them side by side.

Define one

1. Register if you still need an account. The trial is 7 days, no card, from $4.99/mo.
2. Send the pageview or the custom event you want to count. A goal cannot match a beacon that never arrives.
3. In the product, add a goal. Match an exact path such as /thanks, or a stable event name such as signup_completed.
4. Add a funnel only when the question is ordered: step one, then step two, inside the same daily visitor hash. Tomorrow's visit is a new hash.
5. Read the goal next to Search Console. A query that earned a click is not the same row as a goal completion.

Creating the rule does not emit a billable event. The events that match it were counted when the browser sent them. Keep names lowercase and stable so an MCP query can ask for the same name. The agent cannot invent the schema for you.