Agents

Agents holds the three agents as sections: Convert, where a browser becomes a person; Activate, where a new person reaches your Product's first value; Retain, where a person at risk of leaving comes back. Each lists that agent's Targets: an outcome you publish for one population, with who enters, what counts as done and how many days it has. Every Product starts with Anonymous to Identified and Back within 30 days published and First 7 days as a Draft with its Completion left open.

Before you start

Publishing, editing and creating a Target takes an admin; members read every card and page. A Target counts only consented browsers (Consent) in the environment picked in the sidebar. A person enters an Activate or Retain Target only after identify() resolves (Quickstart).

Setting it up

Create Agent asks which agent the Target is for, then offers that agent's presets and its blank card, Blank Convert Target, Blank Activate Target or Blank Retain Target. Activate presets open with the Completion to fill; Key action kept up and Segment at risk with the Entry to fill; a blank Target with the Entry and Window set. Create Draft opens the new Draft. One thing to fill marks a field left open; Needs attention means the Completion names the last step of a flow this environment no longer serves. The card's menu holds Rename, Publish and Delete, refused while any environment serves the Target.

Definition holds the four parts. Entry is fixed for Convert (the first consented load as Anonymous) and Activate (the moment identify() resolves, once per person). For Retain it is a risk rule: Days since the last Session (Back within 30 days uses 14), Days since the last Custom event, or Joined a Segment (Segments); a person can enter more than once. Narrowing keeps only people whose attributes match, so any clause drops anonymous browsers. Completion is one or more conditions, any of which counts: a Custom event from arcy.track(), a route reached, a flow's last step, Identified on Convert only, or Came back on Retain only. Window is the days after Entry inside which done counts: 7 for Convert and Activate, 30 for Retain, 365 at most. After Save the pill reads Pending changes until you publish again.

Publish freezes the Definition and the triggers for this environment; it stays disabled, with the reason, while the Completion is empty or a Retain Entry needs its event or Segment. Unpublish stops measuring and every trigger here.

Triggers say what ARCY does for someone inside the Window who has not completed. Add trigger opens the flow step's condition builder with the standing conditions added under checked when the visit starts: Day in Window, Segment membership, Sessions since Entry, Days since last Session, Visited a route, Ran a flow, Struggled on a route, Custom event fired, Attribute, Acquisition channel and Checklist state. Every trigger needs one live condition, such as the current page: the moment ARCY acts. Then is Suggest, Run or Show. A Suggest is a closable offer, as the chat bar itself (Bar) or a pill above it (Pill); one at a time, never while the panel is open or a flow runs, and closed for the session once closed. A Run starts the flow on its own, once per person until you republish, after the condition has held for Settle time (2 seconds by default); the bar shows the flow's name, the step and Stop. A Run waits while a flow runs, a question is pending, the visitor is typing or an offer is showing, and starts only where the flow's first element is on the page. A Show puts a published Checklist on the chat bar; its condition, Where it shows, takes page and element conditions only. A Retain trigger acts only when the person is back on a page: ARCY never emails an end user. Only flows and Checklists published here can be picked; one that leaves the environment reads inert while the Target keeps measuring. Suggest line (optional) replaces the flow's public name and can be translated after the first save. Each saved row shows its counts over the last 56 days: fired, dismissed and ran for a Suggest; fired, ran and stopped for a Run; shown, opened, dismissed and tapped for a Show.

What it changes

Lift draws the Target rate by Entry week: who entered against who completed inside the Window, a week still open marked as still counting. The rate stays hidden until a week has 30 people; the counts always show. Convert counts browsers and adds the split by Acquisition channel, the top four and Other; Activate and Retain count identified people once each. History begins at consent, and a person is never followed across devices. A Custom event in the Completion counts from the moment it is reported, so wire arcy.track() before you publish (Reference).

Under the rate, With ARCY against Baseline compares the people who entered and ran a flow a trigger names inside their Window, a Checklist item's flow included, against everyone else who entered: Activation lift, then Finish rate, Time to finish and Counted With ARCY, each with the Baseline value under it. Both groups count as finished by this Target's Completion; someone who only chatted or only saw a Checklist is Baseline. The rates stay hidden until both groups have 30 counted. With a Run trigger published, the note under the tiles says the With ARCY group was chosen by the trigger's condition rather than by the person.

Each card shows this week's rate against four weeks ago and how many are inside the Window and not done. A change to Entry, Narrowing, Completion or Window recomputes the rate over all history at the next publish; a rename or a priority change does not.

People counts who is inside the Window right now and not done, named people and anonymous browsers apart; a Target with a Show trigger adds a Checklist column. On a Retain Target it is the At-risk list: named people sorted by last seen with their plan and the routes they used most, each opening their page on Users; anonymous browsers are counted, never listed. At-risk list grew on Alerts emails you when it doubles since last week and reaches the floor you set per Target.

The section's agent writes a narrative for every published Target each week, in both languages, from tool results only: what the rate did, where people stopped, one next action. Run now writes it again, once a day.

The agents also draft. Proposed by the agent at the top of the page lists a Target draft or proposed triggers, each marked with the sessions the agent read. Publish takes your own publish route; Discard deletes the draft and the agent does not propose that place again. A draft the Console wrote from your question carries Open the thread instead. Nothing an agent or the Console writes is live until you publish it. Ask the Console in the header opens the Console with a question about this Target.

Triggers are armed on each page load that carries a grant, when consent is granted, when identify() resolves and when a flow run ends, never before consent.

See also

• Checklists
• Insights
• Alerts