---
title: "Goal Conversion Tracking in HitKeep | HitKeep"
description: "Track path-based and event-based conversion goals in HitKeep for signups, forms, purchases, AI referrals, and chatbot-assisted outcomes."
canonical: "https://hitkeep.com/guides/analytics/goals/"
---

# Goal Conversion Tracking in HitKeep

You want to track real conversions without adding another external analytics service. Goals in HitKeep let you measure meaningful actions (event-based or path-based) directly inside your instance.

![HitKeep goal report with conversion KPIs, trend analysis, and matching session traffic](https://hitkeep.com/_astro/analytics-goals.C2tKB0q7_1z7GRi.webp)

One goal report combines conversion KPIs, the comparison trend, matching traffic, exports, and definition management.

Use the generated API reference for goal management:

- [List goals](https://hitkeep.com/api/#tag/goals/GET/api/sites/%7Bid%7D/goals)
- [Create a goal](https://hitkeep.com/api/#tag/goals/POST/api/sites/%7Bid%7D/goals)
- [Update a goal](https://hitkeep.com/api/#tag/goals/PUT/api/sites/%7Bid%7D/goals/%7BgoalID%7D)
- [Delete a goal](https://hitkeep.com/api/#tag/goals/DELETE/api/sites/%7Bid%7D/goals/%7BgoalID%7D)
- [Get goal timeseries](https://hitkeep.com/api/#tag/goals/GET/api/sites/%7Bid%7D/goals/timeseries)

When another system needs to react to a conversion, subscribe a site or instance endpoint to `goal.converted`. The [signed outbound webhook guide](https://hitkeep.com/guides/integrations/webhooks/) covers event IDs, HMAC verification, retries, and idempotent processing.

## Goal Types

- Path goal: counts sessions that hit a specific path (e.g. `/pricing`).
- Event goal: counts sessions that emit an event name (e.g. `signup`).

Use path goals when the conversion is represented by a URL, such as `/thank-you`, `/checkout/success`, or a documentation signup page. Use event goals when the conversion happens inside a page, modal, checkout, embedded form, or product flow where the URL does not change.

Common goal examples:

| Goal | Recommended type | Example |
| --- | --- | --- |
| Contact form submission | Event | form_submit or lead_form_submit |
| Newsletter signup | Event | newsletter_signup |
| Pricing page reached | Path | /pricing |
| Trial started | Event or path | trial_start or /signup/complete |
| Purchase completed | Event | purchase |
| AI assistant helped conversion | Event | assistant.goal_assisted |

## Dashboard Workflow

1. Open your site in the dashboard.
2. Navigate to Goals.
3. Create a new goal (path or event).
4. Select **All goals** or one goal to update conversions, converting sessions, conversion rate, and the trend chart.
5. Review and export **Matching traffic** below the trend. One selected goal shows page hits from sessions that completed it; **All goals** shows the union of sessions that completed any goal.

The Goals report keeps analysis and definition management together. Search, sorting, pagination, date changes, and exports retain the selected goal cohort.

For cross-dimensional investigation, select a goal from the Dashboard’s Conversions card. The goal chip filters Dashboard KPIs, charts, dimensions, raw traffic, and exports to page hits from sessions that completed the selected goal during the report window. Normal page, source, device, and location filters intersect with the cohort. Clear the chip to restore unfiltered reporting.

Goal definitions are managed inline in the searchable table. Editing a goal keeps its ID and creation timestamp, while recalculating analytics from the updated definition.

## How goals relate to events and funnels

Goals answer “did this outcome happen?” Funnels answer “where did people drop out before this outcome?” Events provide the raw named actions that event goals and funnel steps can use.

For a SaaS signup flow, a typical setup is:

1. Create an event goal for `trial_start`.
2. Create a funnel with steps for `/pricing`, `/signup`, and `trial_start`.
3. Use UTM filters to compare campaign quality.
4. Use source, country, city, provider, and ASN filters to spot traffic segments that convert or stall.

## AI and assistant conversions

Goals also work with AI-related traffic. Use path goals or event goals to see whether AI-referred visits reach important pages, and use `assistant.goal_assisted` events when an on-site chatbot contributes to a conversion.

## Related

- [Google Analytics Alternative for WordPress](https://hitkeep.com/use-cases/google-analytics-alternative-wordpress/)
- [Configuration Reference](https://hitkeep.com/reference/configuration/)
- [AI Visibility Analytics](https://hitkeep.com/guides/analytics/ai-visibility/)
- [AI Chatbot Analytics](https://hitkeep.com/guides/analytics/ai-chatbot-analytics/)
- [Signed Outbound Webhooks](https://hitkeep.com/guides/integrations/webhooks/)
- [REST API Reference](https://hitkeep.com/api/)

Prefer a managed setup with backups and upgrades handled for you? [Start with HitKeep Cloud →](https://cloud.hitkeep.eu/signup?plan=free&billing=monthly&utm_source=hitkeep_docs&utm_medium=referral&utm_campaign=cloud_signup&utm_content=docs_inline)

[Previous Event analytics](https://hitkeep.com/guides/analytics/events/)[Next Funnels](https://hitkeep.com/guides/analytics/funnels/)