Goals track meaningful visitor actions on your site. When an event matches a goal's conditions, it counts as a conversion and appears in your KPIs and Goals panel.
Goals let you identify which pages and traffic sources drive actual outcomes, not just visits. Set up goals for the actions that matter to your business: purchases, signups, downloads, affiliate clicks, form submissions, or any custom event your tracker sends.
Each goal has a type, one or more matching conditions, and a badge for visualization. Goals marked as conversions feed the Conversions and Conversion Rate KPIs at the top of your dashboard.
Click goals match outbound link clicks based on URL, domain, element text, title, or Amazon ASIN. Use these for affiliate links, buy buttons, and external content.
Available fields:
Pageview goals match when a visitor loads a specific page. Use these for thank-you pages, order confirmations, signup completions, or any page visit that indicates success.
Available fields:
Pageview goals support the full range of operators. Use contains for flexible matching (any page with "/checkout/" in the path) or equals for exact paths like /impressum/.
Form goals track form submissions. Clickport auto-detects Contact Form 7, WPForms, Gravity Forms, and native HTML form submits without requiring additional scripts.
Available fields:
Custom event goals match events sent via the clickport.track() API. Use these for any action not covered by the standard types: video plays, downloads, account upgrades, cart additions, purchases.
Available fields:
clickport.track()Custom events support revenue tracking. Pass a revenue amount and currency to clickport.track() and the Goals panel will show total revenue per goal.
clickport.track('Purchase',
{ product: 'Pro Plan', category: 'Subscription' },
{ amount: 29.99, currency: 'USD' }
);
Open the Goals configuration modal from the Settings menu in the top right corner of the dashboard. Click "Add Goal" to create a new goal.
Each goal has one or more conditions that define when it matches. Conditions use a field, an operator, and a value.
All goal types support these operators:
When a goal has multiple conditions, the match logic controls how they combine:
Goals are evaluated in order from highest to lowest priority. The first matching goal wins. Drag goals in the configuration modal to reorder them and change priorities.
This matters when you have overlapping conditions. For example, a specific "Premium Plan Purchase" goal should rank higher than a generic "All Purchases" goal so premium conversions get tagged correctly.
Goals appear in two places on your dashboard: the Conversions and Conversion Rate KPIs, and the Goals panel.
When you have at least one goal marked as "Counts as Conversion", two additional KPI cards appear in the top row: Conversions and Conversion Rate.
The Conversions count is the total number of goal completions. Conversion Rate is calculated as conversions divided by visitors, expressed as a percentage.
The Goals panel shows detailed stats for each configured goal. Click the Goals tab in the right content column to view it.
For custom event goals with revenue tracking, the panel shows total revenue next to visitor count.
Goals are evaluated at event ingestion time on the server. When an event comes in, the system checks it against all configured goals in priority order. The first matching goal sets the has_converted flag on that session.
This means goal matching happens once, when the event is recorded. Changing goal conditions later does not retroactively update past sessions.
Custom event goals support revenue tracking. Pass a revenue amount and currency when calling clickport.track():
clickport.track('Purchase',
{ plan: 'Pro', billing: 'annual' },
{ amount: 299.00, currency: 'USD' }
);
The Goals panel aggregates revenue per goal, showing the total across all matching events. This lets you see which traffic sources and campaigns drive actual revenue, not just conversions.
After configuring a goal, trigger the action on your site and check the Sessions panel. Find your session, expand it, and look for the goal badge on matching events. If the goal did not trigger, review your conditions and operators.