Skip to content

Quick Start

This guide walks you through the core flow: set up your workspace, connect your product, let Marketrix learn it, and then choose what to do with that understanding.

Open the Marketrix dashboard and sign in. You can authenticate with your email and password or with single sign-on.

The first time you sign in, you’ll create a workspace:

  • Create a new workspace — Enter your company name, domain, and a workspace slug.
  • The slug is already taken — Someone has claimed that workspace name. You cannot join a workspace by name; instead choose Ask the admins to invite me, which emails that workspace’s admins. You are in only once one of them sends you an invitation and you accept it.

A workspace holds your Applications and team members.

An Application connects a web app or website to Marketrix. Every workspace needs at least one — when you have none, the dashboard prompts you to create your first.

Click New App, then provide a name and the URL of your site. This application requires authentication credentials is on by default, so an app behind a login only needs the username and password Marketrix should use to sign in. Turn it off for a public site, which needs no credentials. See Creating Applications.

Open the Knowledge page and bring in material that describes your product — PDFs, Word documents, plain text, or Markdown files. You can also add videos or import a document from a URL. Marketrix reads this material to understand your features, terminology, and workflows. See Knowledge.

Open Simulations and start a run against your Application. Marketrix autonomously navigates your app, exploring features and recording everything it sees and does. See Simulations.

Once a Simulation completes, check what came out of it:

  • Open the Simulation and click View Graph to see what that single run discovered, or click View Application Graph on the Simulations page for the Application Graph aggregated across every run.
  • Open Skills to see the reusable routines it distilled from the run. See Skills.
  • Open Personas to review the user types it derived for you. See Personas.

This foundation is what every tool below is built on, so it’s worth a look before you go further.

With an Application that Marketrix understands, choose what you need. Each of these works on its own — you don’t have to adopt them in order.

CX Tools

  • User Studies — Run UX Research or A/B Studies with Personas, or use a Survey for organic and simulated responses.
  • User Support — Deploy the support Widget on your site.

Dev Tools

  • QA Flows — Generate persona-driven Journeys and run them against your app.
  • Workflows — Trigger Marketrix from GitHub, Slack, or a schedule.

If in-product support is what you came for, create a Widget from the User Support section. Customize its appearance and behavior, then copy the embed snippet onto your site. Visitors can then chat in the three interaction modes — Tell, Show, and Do. See Widgets and Interaction Modes.

Before you embed it, use Open Playground on the Widget page — a fullscreen view where you watch the widget act on your real application in a live browser. See Testing the Widget.