[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Add goal

> Add a pageview or custom event goal in the site settings. Inputs, cURL, Python and Node.js examples and an example response.

Source: https://cotlet.dev/docs/api/plausible/add_goal

Docs sections: [Get started](https://cotlet.dev/docs.md) · [REST API](https://cotlet.dev/docs/api.md) · [MCP](https://cotlet.dev/docs/mcp.md) · [SDKs & CLI](https://cotlet.dev/docs/sdks.md) · [Integrations](https://cotlet.dev/docs/integrations.md)

Add a pageview or custom event goal in the site settings.

Plausible API: https://cotlet.dev/docs/api/plausible.md

`POST https://cotlet.dev/api/v1/plausible/goals`

Access: write.

Opens Goals in the site settings, clicks + Add goal and saves it. A custom event name must match what your site sends, including capitalisation. Plausible counts a goal only from the moment it exists and does not backfill, and shows it in the dashboard after its first conversion. It reaches no one, and the goal can be edited in the settings at any time.

## Parameters

| Name | Type | Required | Description |
|---|---|---|---|
| `site` | string | yes | Domain of the site as the Sites page lists it, e.g. acme-shop.example. |
| `trigger` | string | yes | pageview or custom_event. |
| `target` | string | yes | Page path for a pageview goal (an asterisk matches a pattern, e.g. /blog*), exact event name for a custom event goal. |
| `display_name` | string | no | Name shown in the Goals report. Default: Plausible fills it from the path or event name. |

## Request

**cURL**

```bash
curl -X POST https://cotlet.dev/api/v1/plausible/goals \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"site":"acme-shop.example","trigger":"pageview","target":"/checkout/thank-you","display_name":"Checkout complete"}'
```

**Python**

```python
result = client.call("plausible", "add_goal", {"site":"acme-shop.example","trigger":"pageview","target":"/checkout/thank-you","display_name":"Checkout complete"})
```

**Node.js**

```js
const result = await cotlet.call('plausible', 'add_goal', {"site":"acme-shop.example","trigger":"pageview","target":"/checkout/thank-you","display_name":"Checkout complete"});
```

**CLI**

```bash
cotlet call plausible add_goal --data '{"site":"acme-shop.example","trigger":"pageview","target":"/checkout/thank-you","display_name":"Checkout complete"}'
```

## Example response

```json
{
  "site": "acme-shop.example",
  "name": "Checkout complete",
  "trigger": "pageview",
  "target": "/checkout/thank-you",
  "status": "added"
}
```

Previous: [Create site](https://cotlet.dev/docs/api/plausible/create_site.md)
Next: [Create shared link](https://cotlet.dev/docs/api/plausible/create_shared_link.md)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.