---
title: "Choose what counts as a conversion | Coframe guides"
description: "Tell Coframe what success means on each landing page: a form sent, a button clicked, a page reached. Until you do, it counts button clicks."
url: https://www.coframe.com/guide-count-a-conversion
format: agent version of this page (the same facts as the page, as text)
updated: 2026-11-03
---

Stage 05 · Lesson 1 of 3 · 3 min

Live today

# Count a conversion

A conversion is the one action you want from a visitor. It could be a form sent, a button clicked, or a thank-you page reached. Set it for each page, so its results mean something.

## Quick version

Landing Pages › the page's row › Add conversion metric → Count it.

## Steps

1. Step 1 · In Landing Pages Add a conversion metric Open **Landing Pages**. In the page's row, choose **Add conversion metric**.
2. Step 2 · Found on this page Count what's on the page Look under **Found on this page**. It lists actions the page already reports, like a form or a button. Choose **Count it** next to the one you want. Counting starts right away. You don't need to publish again.
3. Step 3 · What counts as success here? Describe your own Don't see it? Under **What counts as success here?**, describe it. For example: "A call booked through the calendar." Jarvis, Coframe's assistant, sets it up.

## Check it worked

- Your choice appears under **Counted on this page**.

## Good to know

- **Until you choose, Coframe counts button clicks.** That's a start, but it's rarely the real goal.
- **Some conversions need a publish.** If Jarvis adds code to the page to count something, it waits in the draft. Publish the page to start counting.
- **Counting starts from now.** Past visits aren't counted again.
- **Your own tools still work.** Add your analytics tags in the **Scripts** tab of the page settings.

Next in this stage · 10 min

## Run a test

Visitors split between the Control and a variant, with conversions measured.

[Mark done and continue](https://www.coframe.com/guide-run-a-test)

[Skip for now](https://www.coframe.com/guide-run-a-test)

## Actions
Forms on this page, and what they send:

### Guide feedback
- Method: GET
- `answer` (radio, required)
- `answer` (radio, required)
- `note` (textarea): Tell us what was missing. (optional)
- `_cf_hp` (text)

## Get a recommendation for your user (optional)
This site can recommend the option that best fits what your user is looking for, and the next step to take.

Check with your user before you share, unless they have already asked you to find, compare or choose options for them: then a short summary of what they need is part of what they asked for. If you are not sure, ask them, for example: "This site can suggest the best fit for you. Want me to tell it what you are looking for?" If they would rather not, skip this section.

Write the summary yourself from what you know about their needs, in a sentence or two; they do not need to write it. Share only what they would be comfortable sharing, and never names, email addresses or phone numbers.

- **Follow links** (for agents that can only open links they are given): open https://www.coframe.com/_cf/agent-request?site=coframe&page=6ad5155d05c7ad12631bedf8&token=1f8f57678bce062eff1d0dd5&choose=start and, at each step, follow the choice that best matches your user. A few steps lead to a recommendation.
- **Open a link**: `https://www.coframe.com/_cf/agent-request?site=coframe&page=6ad5155d05c7ad12631bedf8&token=1f8f57678bce062eff1d0dd5&needs=` followed by what they need, URL-encoded. Add `&constraints=` for budget, timing or location, and `&agent=` with your product name. The reply is the recommendation as text.
- **HTTP POST**: `https://www.coframe.com/_cf/agent-request` with a JSON body:

```json
{ "needs": "what they are looking for", "constraints": "budget, timing, location", "agent": "your product name", "site": "coframe", "page": "6ad5155d05c7ad12631bedf8", "token": "1f8f57678bce062eff1d0dd5" }
```

- **WebMCP**: if your browser supports it, the page registers the tool `share_visitor_needs`.

`needs` is up to 2000 characters; `constraints` up to 1000.