ARCY AI
SettingsInstall

Events

Declare the events your product reports with track(), mark those that count as value, see how many arrived and how many ARCY reported, and catch an undeclared name.

Settings > Install > Events lists the events your product reports to ARCY by name. Your code sends one with arcy.track("checkout_done") (Reference). A name that is not declared here is dropped: declare first, then send.

Before you start

Declaring, editing and archiving take an organization admin. The counts read the environment in the address; the list is the same in every one.

Setting it up

Press Add event and fill in:

  • Display name: what your team reads. Accents are kept.
  • Code name: the name your code passes to arcy.track(). Permanent once declared, so a published flow that counts it cannot break. Lowercase letters, numbers and underscores, up to 64 characters. Typing a display name fills it in, transliterated: "Ödeme tamamlandı" gives odeme_tamamlandi.
  • Description: what moment it marks.
  • How often it should happen: Once per person, Once per session, Repeating, or left out. Repeating cannot be a flow's completion event.
  • Counts as value: on when this event is the moment a person got what they came for.
  • Where it happens in the code: one line, so a teammate finds the call.

Each row's menu holds Edit for the words on an event, Count it as value, Copy the track() line and Archive. Brief for a developer copies every declared event and its call as one message.

Hand it to your agent opens Set up your events on ARCY MCP. Your agent reads your Endpoints and your code, proposes one event per moment worth naming, says which of them count as value, and writes the arcy.track() calls. Ask your developer, beside it, gives you a link to send instead (ARCY MCP).

What it changes

A name no event declares is not stored, and it does not count against your plan's tracked events (Usage). A typo costs you nothing and reads here with its own count.

What arcy.js reports on its own, under the table, counts page loads, clicks, flow steps and widget use against the same allowance. You declare none of them.

Counts as value is how ARCY reads value in your Product. The chat tests read the mark.

Every event picker offers your declared events: a flow's completion event, a funnel step and a checklist item's Done rule. Publishing a flow or a checklist that names an undeclared event is refused.

An event your analytics tool already sends wears From Integrations and is never wired as a track() call; arcy.js forwards it, and a second call would count the moment twice. You describe it with Edit here and remove it on Integrations.

ARCY sends the event an endpoint's Reports Event names each time it performs that operation and the answer reads as done, and Arrived says how many came from ARCY (Endpoints). Sent by ARCY alone, a flow finishing on it reads no Lift difference.

Row readsMeaning
Never receivedDeclared, and nothing has arrived here. Usually a missing track() call.
Not declaredArriving with nothing declaring it, so every one was dropped.
A second count, imported over the last 12 monthsPast events an Import brought, outside your plan's tracked events.

Archiving is refused while any flow, checklist, funnel or mapping reads it, and the refusal names what does. Archive it and the same code name declares again with its history.

When it goes wrong

A row reads Never received. Your code is not calling arcy.track() with this name in this environment, or spells it differently. Check the call, then the environment in the address.

A name reads Not declared. Press Declare to keep it, or fix the spelling in your code.

A row wears Repeating and a completion event picker will not take it. The Lift reading would count almost everyone as finished. Pick a once-per-person event, or declare one.

See also

On this page