Installation

Settings > Installation builds the install code for the environment selected in the sidebar, with that environment's token already in it, and lists every step between "no code" and "this environment can carry real users".

Before you start

• The page follows the environment switcher in the sidebar. To install a different environment, switch there first.
• The Development environment answers from any address. Production answers only for a domain you have verified on Origins, and the DNS record that proves it can take hours to spread, so add the domain early.

Setting it up

Three steps are required:

1. Add arcy.js. Pick your framework and how you sign users in. The code itself, and what init() and identify() do, is on the Quickstart.
2. Replace the placeholders. This step appears only when the code you picked contains placeholders. What each one means is on the Quickstart.
3. Verify installation. Run the check once the code is live. It watches for a session carrying this environment's token.

Then the readiness steps, in the order you do them:

1. Add custom attributes. Undeclared keys are dropped.
2. Enforce identity verification. Not shown on the Development environment.
3. Verify your domain.
4. Train the agent.
5. Set the persona.
6. Match your brand.
7. Set your limits.
8. Go live. Switch the environment live and point your production build at its token.
9. Create your first flow. Flows are authored on your live site, so this comes after going live.
10. Measure your first flow.

Two buttons hand the page to someone else. Copy developer instructions copies the whole page as one document: the install code for the framework and sign-in method you picked, the token, and the steps after it, written for an email or a ticket. Hand it to a coding agent copies the same install as a task for an agent to run in your repository.

What it changes

A step is marked done when ARCY sees it happen, never because you clicked it. Identity verification is the exception: you decide when the dry run is over. On the Development environment every readiness step is optional. Once every step is done the page says so and folds the steps shut, where you can still open them.

When it goes wrong

The verify check names the failure:

• No traffic from this environment: open your site in another tab so arcy.js loads. The check picks it up on its own.
• Another environment is receiving sessions: the live code carries that environment's token. Switch the page to it, or replace the token in your code.
• Requests from an origin are refused: that origin is not verified for this environment. Verify it on Origins and assign it to the environment.
• Identity verification is failing: sessions with a wrong signature continue as anonymous. Check the signature your server creates on Identity verification.
• Unknown attributes: the check lists them. They are dropped until you declare them on Attributes.
• Only localhost traffic so far: the install works, but the environment has not been seen from a verified production origin yet.

See also

• Quickstart
• Environments
• Origins