Analytics

View as Markdown

Analytics is the Usage tab of the canvas. The canvas shows what is attached to this agent. The Usage tab adds how many requests came in through each path and what they cost.

When to use it

After you turn on Live, to see how many people visited, how many started a chat and how many credits those chats use.
To find which API key your integrations call the most.
To find the day channel or routine usage went up.

To compare every agent at once, use the usage dashboard. Analytics looks at one agent.

Getting there

Open the agent’s Studio.
Select the Usage tab at the top of the canvas. The Analytics cell under the agent card takes you to the same view.
Pick a period at the top right: 7, 30 or 90 days. The period only exists on the Usage tab.

Figures on the canvas

On the Usage tab, the nodes in the left column (Requests come in) show figures.

Node	What it shows
Channel, Live, API header rows	Chats and credits for that source. The Live row starts with visits
Channel connection, API key	Chats, replies and credits for that one path
Live address	Visits, chats started and credits for that address
Other requests	Usage with no path to configure, such as app chats, routines and spaces

The line into the agent gets thicker with usage. Paths with no usage in the period are drawn as faint dashed lines.

The API header total includes calls made with account-wide keys. The canvas only draws keys dedicated to this agent, so the key nodes can add up to less than the header row.

The chart below

A daily bar chart sits under the canvas. Bars stack by source, and every day in the period gets a slot. Days with no usage are empty.

The chart header shows the period totals: chats, replies, tokens and credits.
Choose Tokens, Credits or Replies for the bars. While Live is in focus there is a fourth choice, Visits.
Select a source chip below the chart to hide or show that source.
If you collapse the chart, it stays collapsed next time.

Chats are not drawn as bars. Adding daily chat counts would count a chat that spans several days more than once. Read the period’s chat count in the chart header.

Focusing on a path

Select a node on the Usage tab to open the Analytics panel on the right. The chart then shows only that path.

A source (the Channel, Live or API header row, or Other requests) keeps only that source’s bars in full color.
An API key or channel connection shows that path’s daily values against the day’s total.

The Analytics panel has two tables.

Sources: chats, replies, tokens, credits and share for all six sources. Sources with no usage stay as rows so you can compare.
Paths: calls, tokens and credits by API key and by channel connection. Keys only show their prefix. Select › at the end of a row to open that key’s or channel’s settings. The third tab, Live, is covered in Live visits.

The focused path shows as a chip in the chart header and the panel header. Select × on the chip to go back to everything.

Live visits

With Live on, the Usage tab also counts the people who open your agent’s endue.live page or the chat window embedded on a site. A visit is counted even when the visitor leaves without sending a message, so you can see how many of the people who came went on to chat.

Select the Live header row or the Live address under it. Visits then show in three places.

On the canvas: the Live header row reads visits, chats and credits. The Live address reads visits and chats started.
In the Analytics panel: Paths opens on its Live tab. It has the period totals, a table by site, a table by referrer and the languages visitors use.
In the chart: Visits becomes a choice for the bars. Each bar splits into page and embed.

What is counted

Figure	What it counts
Visits	Each time the endue.live page or the embedded chat window is shown to a visitor. A reload adds a visit.
Unique visitors	The same visitor on the same day at the same agent, counted once. The period figure adds up the daily figures.
Chats started	Visits in which the visitor sent at least one message.
Start rate	Chats started divided by visits.
Valid chats	Visits in which the visitor sent two or more messages.

A day runs from midnight to midnight UTC. A message counts once the agent accepts it. One that is refused, because the visitor is sending too fast or the account is out of credits, is not counted.

Chats started and Chats are different numbers. Chats started counts visits. Chats counts conversations the agent answered at least once. A visitor who comes back the next day and continues the same conversation adds two chats started and one chat.

The site table has one row for the endue.live page and one for each site the chat window is embedded on. Each row shows Visits, Chats, Messages and Credits. Chats, messages and credits add up to the Live row of the Sources table.

Where visitors came from

The referrer table groups visits by where the visitor came from. Each visit goes to the first row that fits, reading from the top.

Row	A visit lands here when
Site · example.com	The visitor opened the chat window embedded on that site.
Campaign · newsletter	The link had a `utm_source`. Its value becomes the name.
Direct	The browser sent no referrer. The visitor typed the address, used a bookmark, or came from an app that does not pass one.
endue.live Explore, endue.ai	The visitor came from endue.live or endue.ai.
Search · Google	The visitor came from a search engine endue recognizes.
Social · X	The visitor came from a social network or messenger endue recognizes.
Site · blog.example.com	The visitor came from any other site. Only the host is shown.
Unknown	A message arrived but the visit itself was never recorded, for example because the browser blocked it.

The table shows the 20 rows with the most visits and folds the rest into one line.

To tell the links you hand out apart, add utm_source to the address, as in endue.live/@your-agent?utm_source=newsletter. A value can use letters, digits and . _ ~ -, up to 64 characters. A value in any other shape is dropped.

Visits that are left out

Two kinds of visits are recorded and kept out of every figure above.

Owner: when you open the Live page from inside endue (the address in the agent’s Live settings, or the button on the agent’s home), that browser is remembered as the owner’s. Its visits count as owner from then on. An embed running on localhost counts as owner too.
Bots: crawlers and link previews that do not run scripts are never recorded. Automated browsers and known bots that do run them count as bots.

The last line of the Live tab shows how many were left out, as in Excluded visits: owner 14 · bots 37.

Credits work differently. Chats you had yourself while testing used credits, so they stay in the credit figures.

What a visit record keeps

This covers visit counting. When a visitor chats, the conversation itself is saved the same way as before.

Kept for each visit:

The agent, and whether it was the page or an embed. For an embed, the host of the site it is on.
The referrer as a kind and a name. The name is a host, a search engine or network, or the utm_source value.
utm_medium and utm_campaign, when the link has them.
The browser language, the country and the device type (desktop, mobile or tablet).
The time of the visit and how many messages the visitor sent.
A visitor key, used only to count unique visitors.

Not kept:

The visitor’s IP address.
Cookies. endue writes nothing to a visitor’s browser to count visits.
The full address of the page the visitor came from. The path and query are dropped and only the host remains.
The browser’s user agent string.

The visitor key is worked out from the IP address, changes every day and is different for every agent. It cannot connect one person’s visits across days or across agents, which is why unique visitors are counted per day.

Visit records are deleted after 400 days.

Reading the numbers

Chats are conversations this agent answered at least once in the period. Conversations it never answered are not counted.
Replies are the number of times the agent answered.
Credits are the settled cost. One credit is US$1.
For the same period, the token total matches the Agents tab of the usage dashboard.

Who can see it

Only the agent’s owner. Other people don’t see the Usage tab or the Analytics cell. When someone else uses this agent, that usage is counted on their account and does not appear here.

Limits

Tool calls (connectors and skills) are not counted yet. That is why the right column of the canvas has no figures.
Device costs (computer and browser) are not included.
Usage is recorded when a run finishes. A run in progress shows up after it ends.
Visits have no history from before visit counting was added. Chats and credits from that time are still shown.
Unique visitors are told apart by network, one day at a time. Several people on one network count as one visitor.
For an embed, a visit is the chat window opening. The chat button appearing on your site is not counted, so an embed’s start rate reads higher than the page’s.
The owner mark belongs to one browser. On another device or browser you count as a visitor until you open the Live page from inside endue there.
Referrer rows stop at visits and chats started. Chats, messages and credits are split by site only.

CanvasThe Setup tab: what is attached.

Usage dashboardEvery agent at once.

Agent APICall your agent with an API key.

Plans and usageHow credits and included usage work.