Integrations

Configure > Integrations is where ARCY listens, in the browser, to the analytics tools already running on your pages. Per environment: a tool switched on for Staging is not listened to on Production. ARCY reads nothing from an analytics tool's servers, holds no key, reads no cookie. It hears event names on the page and nothing else.

Before you start

• Only an admin can switch a tool on, accept an event or connect a helpdesk. A member sees the same page read-only.
• A visitor must have accepted your consent banner before an event name is reported. On the page you test with, accept the banner first. See Consent.
• The tool must be on the page as a global (window.posthog, window.mixpanel, window.amplitude, or dataLayer for Google Analytics 4). A tool installed from npm has no global; hand its instance to arcy.init with the listen option, documented on Reference.

Setting it up

Analytics. Four switches: PostHog, Mixpanel, Amplitude, Google Analytics 4. A tool that is off is never touched, not even to check it is there. A tool a tag manager adds within ten seconds of arcy.js loading is still found. Hand it to your agent with the ARCY MCP opens Connect your analytics on ARCY MCP: your coding agent finds the events your tool already sends and proposes a mapping for each, shown here as Proposed by your agent. Accept turns the tool on and maps the event. An event ARCY has not heard yet is refused: do the action in your Product once, then accept again.

Seen events, on the switched-on tool's own page, which its card opens. Every event name arcy.js has heard leaving it, and when it was last heard. A tool's own names never appear here: PostHog's and Mixpanel's $... events, Amplitude's [Amplitude] ... events and Google Analytics 4's automatic events such as page_view or scroll.

Each row carries an ARCY name, pre-filled as a plain slug of the tool's name: Checkout Completed becomes checkout_completed. Lowercase letters, digits and underscores, at most 64 characters, starting with a letter. Edit it if you like, then press Accept. Two tool names may share one ARCY name. Update saves an edited name on an accepted row. Remove, in the row's menu, stops recording it.

Helpdesk. When a visitor asks to talk to a person, ARCY opens a ticket in the helpdesk you connect here, and the reply comes from your own team. There is no live transfer. Zendesk, Intercom and HubSpot connect by signing in. Freshdesk takes your Freshdesk name and an API key, Crisp a Website ID with a Plugin identifier and Plugin key. A key is never shown again after you type it, and Disconnect deletes it. One helpdesk per environment: disconnect the first to send tickets to another. Nothing leaves ARCY until the visitor reads the summary and presses yes, and what the ticket carries is on How AI request content is handled.

What it changes

• From the next page load after Accept, every time the tool sends that event ARCY records the event under the ARCY name in the same session. Name only: the properties the tool attached are dropped in the browser and never sent.
• A recorded event counts as a tracked event against your plan, obeys consent like every other event, appears on a session's Activity, and can be picked as a flow's completion event on Flows. Names nobody accepts are dropped after 90 days.
• The list holds at most 1,000 names per environment. Past that, a new name is not listed until unaccepted names drop out. One page load reports at most 200 names per tool.
• If a switched-on tool already sends an event, do not also call arcy.track() with the same name. You would record it twice.
• Only what happens in the browser is heard. An event your backend sends to a tool's server SDK never passes through the page. Keep arcy.track() for those.

When it goes wrong

• Accept answers "The mapping could not be saved." and the row disappears: the name dropped out of the list while the page was open. It returns on the page's next load, and Accept works then.
• A helpdesk reads Needs attention: the vendor refused the credential ARCY holds, and no ticket has opened since. Connect again.
• A vendor's page says its sign-in is not set up: ARCY has not registered its sign-in with that vendor yet. Connect a helpdesk that takes a key instead.

See also

• Flows
• Reference
• Bring Your Own Data