Skip to main content
At the end of this page, your agent has at least one goal. You can read how many conversations achieve it and where the rest drop off.

Before you start

Before you start, sign in to the dashboard and select the organization you want to work in.
  • You need a role with analytics access. Without it, the analytics pages redirect you away.
  • You need an agent with a flow, because a goal trigger points at a gambit or at a captured field.

Where goals live

Goals belong to an agent. You define them in the Goals & Behavior section of the agent’s Configure screen. Every goal you define there is counted on the Goals tab in Analytics. A deployment can also mark one of those goals as its primary goal, which drives the conversion block on the Overview tab. See Read the Overview tab.

Create a goal

1

Open your agent and select Configure in the builder sidebar

The Configure screen lists its sections on the left under Settings.
2

Select Goals & Behavior

The section heading reads Goals with the line “Define the successful actions counted in analytics.” The Goal definitions card sits at the top.
3

Start a goal

With no goals yet, the card reads Choose what counts as a lead. Select Create a different goal to open the goal form. When goals already exist, select Add goal instead.
4

Enter a Label and pick a Kind

The label names the goal in lists and charts, for example Demo booked. The kind is Lead, Booking, Purchase, Resolution, or Custom.
5

Pick a Trigger

Choose A specific step is completed or Contact info is captured. The fields below the dropdown change with your choice.
6

Decide on Default primary goal

Turn on the switch when this goal should be the suggested primary goal for deployments of this agent.
7

Select Create goal

The toast reads Goal created and the goal appears in the list. Cancel discards the form.
The form refuses to save until it is complete, and an error toast names the gap. An empty label shows Enter a goal label. A step trigger without a step shows Choose a step, and a captured-info trigger with nothing ticked shows Choose email, phone, or both.

The one-click lead goal

The empty card offers a shortcut button, Count a captured email or phone number as a lead. It creates a goal named Leads of kind Lead that triggers when the agent captures an email or a phone number. The goal becomes the default primary goal. The toast reads Lead goal created. Use it when your agent exists to collect email addresses or phone numbers, and edit it later if you need a different label.

Trigger: A specific step is completed

A Step dropdown appears and lists the gambits of the agent’s flow by their labels. The goal counts once per conversation when the conversation completes that gambit: If the gambit is later deleted from the flow, the form shows Step no longer available for that goal. Pick a new step or delete the goal.

Trigger: Contact info is captured

Two checkboxes appear, Email and Phone, and both start ticked. The goal counts when any gambit in the flow captures a value of a ticked kind. Tars recognizes the kind from the gambit’s validation type, its input type, or its variable name. A question that stores its answer in a variable named email or phone_number counts without extra setup.

Read the goal list

Each row in the Goal definitions card shows the goal’s label and a kind badge such as Booking. The agent’s default goal also carries a Default primary badge. Under the label, a summary line reads Completes Book a demo for a step trigger, or Captures email or phone for a captured-info trigger.
  • The pencil button opens the same form with the goal loaded. Save goal confirms and the toast reads Goal updated.
  • The trash button opens a Delete Demo booked? dialog that reads “This goal will stop being counted for future conversations.” Select Delete to confirm.
Deleting a goal also clears it from any deployment that used it as the primary goal. Gambits and tool actions that referenced the goal lose that reference too. Conversations that already achieved the goal stay counted in past windows.

Choose the primary goal for a deployment

The first goal you create for an agent becomes its default primary goal automatically. Turning on Default primary goal for another goal moves the badge to that goal, because an agent has only one default. Each deployment then picks its own primary goal. Open Conversations, select Settings, then Inboxes, open the deployment’s inbox, and select the Analytics tab. The Primary analytics goal card lists the agent’s goals as Demo booked (booking). See Set up inboxes. Without a primary goal, the Overview tab shows no conversion block, but the Goals tab still counts every goal.

Read goal conversion on the Goals tab

Open Analytics from the sidebar and select the Goals tab. The scope bar and the freshness stamp work the same as on every tab. See Analytics overview.

The headline card

A narration line under the count reads, for example, “12 conversations achieved a goal from 80 conversations started”. A goal counts a conversation once, even when the conversation achieves two goals. When the window has no conversations, the funnel reads No conversations in this window. A note that the cohort is still settling means conversations from the last 48 hours can still change the numbers.

Goals over time

The Goals over time card plots unique goal-achieving conversations per time bucket. A solid line marks This period and a dashed line marks Previous period. When nothing converted in the window, the card reads No goals achieved in this window.

Detailed funnels

The Detailed funnels card sits collapsed below the chart. Select Show details to expand it into two funnels, and Hide details to collapse it again. The Field capture funnel table lists each field the agent requested. Columns are Field, Capture, Asked, Provided, Rate, and Missing. The Asked column counts conversations where the agent requested the field, Provided counts those where a value was captured, and Rate divides the two. Rates below fifty percent render in a warning color. Selecting a red Missing count opens the conversation drawer with the conversations that never provided the field. An empty table reads No field capture events in this window. The Campaign → goal card chains Sent, Delivered, Replied, Engaged, and Goals achieved, with a drop-off chip at each step. Below the chain, a table breaks the numbers out per campaign, ending in Goal rate and a Conversations drill button. Selecting a campaign row opens that campaign’s analytics page with its Delivery funnel, Daily performance, and Recipients cards. With no deliveries in the window, the card reads No campaign deliveries in this window.

Verify

Open a live conversation on the deployment and complete the goal, for example by answering the email question. Reload the Goals tab. The Goals achieved count includes that conversation. Rates stay provisional for 48 hours.