> ## Documentation Index
> Fetch the complete documentation index at: https://help.trfyx.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

> Set up your first Trfyx project, verify tracking, and start exploring your analytics.

# Get your first Trfyx report

This guide takes you from a new workspace to a verified analytics setup. The exact installation instructions depend on how your website or application is built, so use the tracking setup shown inside your Trfyx dashboard rather than copying an unverified snippet from an example.

<Note>
  Trfyx can only report on data that it receives. Complete the setup and verification steps before using reports to make product or marketing decisions.
</Note>

## Before you begin

Make sure you have:

* Access to your Trfyx workspace.
* Permission to change your website or application, or access to the tag manager/deployment workflow your team uses.
* A clear idea of the first outcome you want to measure, such as a signup, trial start, lead submission, or purchase.

## Set up Trfyx

<Steps>
  <Step title="Create or select your project">
    Open your Trfyx dashboard and choose the website or project you want to measure. Check that the domain and environment are correct before installing tracking.
  </Step>

  <Step title="Install the tracking code">
    Follow the [Install tracking guide](/install-tracking) and open the project's installation instructions in Trfyx. Use the option that matches your stack and add the project-specific tracking code to the site you want to measure.

    If you manage deployments through a tag manager, framework integration, or shared layout, make sure the tracking code is loaded on the pages you want included.
  </Step>

  <Step title="Publish and verify">
    Deploy the change to the correct environment, then visit the website yourself. Return to Trfyx and confirm that the visit or incoming events appear in the relevant reports.

    If data does not appear, see [Troubleshooting](/troubleshooting) before continuing.
  </Step>

  <Step title="Choose an outcome to measure">
    Configure a goal for a meaningful action, such as completing signup or submitting a lead form. Use the event or goal setup available in your workspace and make sure the action is triggered only when the intended outcome occurs.
  </Step>

  <Step title="Explore behavior and conversion">
    Use the analytics overview to understand traffic, [funnels](/funnels) to inspect conversion between steps, [user journeys](/user-journeys) to understand navigation, and [session replay](/session-replay) to inspect individual recorded experiences.
  </Step>
</Steps>

## Your first-week checklist

* [ ] Confirm that visits are being collected from the intended domain.
* [ ] Check that internal testing and production traffic are not being confused.
* [ ] Define one or two meaningful goals rather than tracking every click indiscriminately.
* [ ] Build a funnel for a high-value flow, such as landing page to signup.
* [ ] Review a sample of session replays to understand friction behind aggregate metrics.
* [ ] Confirm whether revenue data needs a payment integration or import before interpreting attribution reports.
* [ ] Share a dashboard with the teammates who need to monitor performance.

## What to read next

<CardGroup cols={2}>
  <Card title="Analytics overview" icon="chart-no-axes-combined" href="/analytics/overview">
    Learn how to read your core reports.
  </Card>

  <Card title="Goals and conversions" icon="target" href="/goals">
    Decide which user actions count as success.
  </Card>

  <Card title="Funnels" icon="git-branch" href="/funnels">
    Find where users leave a conversion flow.
  </Card>

  <Card title="Revenue attribution" icon="badge-dollar-sign" href="/revenue-attribution">
    Understand how acquisition connects to revenue.
  </Card>
</CardGroup>

## A note about data quality

Tracking code, blocked requests, consent settings, ad blockers, duplicate installations, test environments, event definitions, and integration delays can all affect the data you see. Verify the collection path and definitions before treating a change in a report as a change in user behavior.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.