Events
Declare the milestones your product reports with track(), see how many arrived in each environment, and find a name that is arriving and not declared.
Configure > Events lists the milestones 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; a member reads the list and the numbers. The counts read the environment picked in the sidebar; the list itself 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 Target that completes on it cannot break. Lowercase letters, numbers and underscores, starting with a letter, up to 64 characters. Typing a display name fills this in, transliterated: "Ödeme tamamlandı" givesodeme_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.
- 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, Copy the track() line and Archive. Brief for a developer copies every declared event, its call and where each belongs, as one message for whoever owns the code.
Hand it to your agent opens Set up your events on
ARCY MCP. Your agent reads your Endpoints and your
code, proposes an event per milestone and writes the arcy.track() calls. Proposals show under Proposed by your agent, accepted
or discarded together.
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 in your code costs you nothing and reads on this page with its own count.
What arcy.js reports on its own, under the table, counts page loads, clicks, flow steps and widget use. You declare none of them, and they count against the same allowance.
Every event picker offers your declared events: a flow's completion event, a funnel step, a Target's conditions and a checklist item's Done rule. Publishing a flow, a Target or a checklist that names an undeclared event is refused.
The Source column says where each one comes from. An event your analytics tool already
sends wears From the 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.
| Row reads | Meaning |
|---|---|
| A count and a last-seen time | Events are arriving under this name. |
| Never received | Declared, and nothing has arrived here. Usually a missing track() call. |
| Not declared | Arriving with nothing declaring it, so every one was dropped. |
Archiving an event is refused while any flow, Target, checklist, funnel or mapping reads it, and the refusal names what does. Archive it and the same code name can be declared 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 the name is spelled differently. Check the call, then the environment
picked in the sidebar.
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.