# X3 Growth Intelligence > Cookieless first-party analytics, ad-cost attribution and server-side conversions – multi-tenant, with a REST API (OpenAPI 3.1), an embeddable SDK, a dashboard and an MCP server. - [OpenAPI 3.1 document](https://api.x3growth.io/v1/openapi.json): machine-readable REST API - [API reference (markdown)](https://api.x3growth.io/docs/api.md): every endpoint with schemas - [MCP server](https://api.x3growth.io/mcp): Streamable HTTP, OAuth sign-in or secret key; see the MCP guides below - [Public MCP docs endpoint](https://api.x3growth.io/mcp/public): docs, setup recipes and event validation without sign-in ## Getting started - [X3 overview](https://api.x3growth.io/v1/docs/index.md): What X3 measures, how it stays cookieless, how the pieces fit together, and where to start. - [Quickstart](https://api.x3growth.io/v1/docs/getting-started/quickstart.md): Two minutes from sign-up to the first live pageview – one script tag, no proxy, no build step. - [Guided onboarding](https://api.x3growth.io/v1/docs/getting-started/onboarding.md): The setup after sign-up – company, Claude, tracking, inquiries, ad platforms, team and plan, every step can be put off – with live status checks from real data and every reason code. - [Organizations, projects and keys](https://api.x3growth.io/v1/docs/concepts/organizations-projects.md): How 3x is structured for teams and agencies – organizations, projects, members, roles and the three kinds of credentials. - [Cookieless sessions](https://api.x3growth.io/v1/docs/concepts/sessions.md): How 3x builds sessions and visitors without cookies – in-memory ids, daily-salted server-side stitching, timeouts and consent upgrades. - [Visitors and traffic](https://api.x3growth.io/v1/docs/concepts/visitors.md): How X3 counts visitors without cookies – visits vs. visitors per day, channel groups, the measuring start, the change engine, return visits with their basis and small cells. - [Attribution and channels](https://api.x3growth.io/v1/docs/concepts/attribution.md): The 13 attribution keys, first-touch per session, value cleaning, and the versioned channel rules. - [Customer journeys](https://api.x3growth.io/v1/docs/concepts/journeys.md): How 3x links the sessions of one person across weeks and devices – consented visitor id or server-side facts only – and the journey attribution models. - [Relevance score](https://api.x3growth.io/v1/docs/concepts/relevance.md): The 0–100 score per session – default model, tiers, custom event and goal rules, versioning and retroactive rescoring. - [Goals and funnels](https://api.x3growth.io/v1/docs/concepts/goals-funnels.md): Define goals from events, pages, leads or conversions; build independent or sequential funnels and compare them over time; analyse questionnaire answers. - [Server-side conversions](https://api.x3growth.io/v1/docs/concepts/conversions.md): How 3x records conversions, deduplicates them with event ids, hashes identifiers and uploads them to ad platforms. - [Ad costs](https://api.x3growth.io/v1/docs/concepts/ad-costs.md): How spend from Google, Meta, LinkedIn and TikTok is imported through Composio and joined to the sessions it paid for. - [Privacy and GDPR](https://api.x3growth.io/v1/docs/concepts/privacy.md): Every device read the SDK makes before and after consent, the three consent modes, retention, erasure and the processor (DPA) note. - [Legal basis](https://api.x3growth.io/v1/docs/concepts/legal-basis.md): The TDDDG § 25 and GDPR reasoning behind cookieless measurement, consent upgrades and server-side conversions – and where it ends. - [Data model](https://api.x3growth.io/v1/docs/concepts/data-model.md): Sessions, pageviews, events, video plays, leads, conversions and ad tables – what each row means and which columns you can query. - [Plans and limits](https://api.x3growth.io/v1/docs/concepts/plans-limits.md): X3's plans (Free, Projekt and Agency), what each includes, how usage is counted and what happens at a limit. - [Lead setup](https://api.x3growth.io/v1/docs/getting-started/lead-setup.md): What counts as a lead or a contact attempt, the hand-off to a technician or an AI, and every recipe. - [Technician page and hand-off](https://api.x3growth.io/v1/docs/getting-started/lead-handoff.md): How an owner hands an open point of the lead setup to a technician or an AI – the public page /auftrag/, its Markdown and status JSON, checks, limits and privacy. ## Insights - [Pulse and counting rules](https://api.x3growth.io/v1/docs/insights/pulse.md): What the four Pulse numbers mean, how leads are credited to campaigns (six counting rules, last click by default) and how sure each assignment is. - [Traffic quality](https://api.x3growth.io/v1/docs/insights/visitor-quality.md): How interested your visits are over time and by source – tiers, honest-chart rules, rolling 7-day sums, comparing sources, the table by source and the Pulse card. - [Project mode – leads, shop or both](https://api.x3growth.io/v1/docs/insights/project-mode.md): What the website is for decides metrics, columns and how closings are reported – leads with optional qualification, shop purchases with revenue, or both; plus the counting rule. - [Real ROAS – revenue of the lead cohort](https://api.x3growth.io/v1/docs/insights/real-roas.md): „Echter ROAS“ = revenue of the period's leads that became customers (from the CRM or entered) ÷ ad spend – in Pulse, Quellen down to the ad, portfolio and MCP. - [Leads, pipeline and revenue import](https://api.x3growth.io/v1/docs/insights/leads.md): Lead status from new to customer, notes, what a lead summary contains without contact data, and the bulk revenue import that reports appointments and sales to the ad platforms. - [Lead qualification – disqualified, lost and reasons](https://api.x3growth.io/v1/docs/insights/lead-qualification.md): The status „Disqualifiziert“ with optional reasons, the organization's own reason list, status history with undo, qualified leads as a metric and what is never reported to ad platforms. - [Recommendations and alerts](https://api.x3growth.io/v1/docs/insights/alerts-recommendations.md): The eight transparent recommendation rules with their minimums, how sure a recommendation is across counting rules, alert types, who sees them and how they are delivered. - [Tasks – everything X3 asks you to do](https://api.x3growth.io/v1/docs/insights/tasks.md): One state model for alerts, recommendations and notices – conditions instead of stored messages, live texts, resolved by themselves with reason and time, coming back only when it matters. - [Monthly budget](https://api.x3growth.io/v1/docs/insights/budget.md): Set a monthly ad budget per project, read the forecast and its share, take budgets from the ad accounts, and the alerts that fire when spend runs over or under. - [Client connection link](https://api.x3growth.io/v1/docs/insights/client-connect-link.md): Send a client a link to connect their own ad account with read-only access – no password sharing – and confirm the account before its costs count. - [Google Search Console](https://api.x3growth.io/v1/docs/insights/search-console.md): Connect Search Console read-only, choose the property, backfill up to 16 months and see queries, pages, countries and devices next to your organic Google visits and leads. - [Presets](https://api.x3growth.io/v1/docs/insights/presets.md): Built-in industry templates and your organization's own versioned presets – create them in the wizard, through the API or by asking Claude, and apply them to projects with a diff first. - [Annotations and deploy markers](https://api.x3growth.io/v1/docs/insights/annotations.md): Notes and automatic markers on every time series – manual notes per project or org-wide, deploys from CI/CD, campaign starts, stops and budget changes from the ad sync, and X3 setting changes. - [Demo data](https://api.x3growth.io/v1/docs/insights/demo.md): Seed a realistic, fictional clinic and agency portfolio for trials, screenshots and reviews – read-only demo login, a fixed clock and daily updates, never touching real projects. - [Share links and embedding](https://api.x3growth.io/v1/docs/insights/sharing.md): Read-only links without an account – dashboard sections or one recording, optional password, expiry, revoke, view counter, and iframe embedding with allowed origins and signed tokens. - [Weekly report by e-mail and Slack](https://api.x3growth.io/v1/docs/insights/weekly-report.md): A weekly summary of a project, an organization or your portfolio by e-mail or Slack – your weekday, time and time zone, with preview, test send and one-click unsubscribe. - [Heatmaps and the page map](https://api.x3growth.io/v1/docs/behavior/heatmaps.md): The page map („Seitenkarte“) with its layers, mass replay, the multi-page board, minimum visitor counts, the data basis label, patterns, reports and the API/MCP tools behind them. - [X3 App for iPhone, iPad and Android](https://api.x3growth.io/v1/docs/insights/x3-app.md): The X3 App for your team – sign-in per device, every analysis area on the phone, notifications for new leads and summaries, what stays on the web and account deletion. - [Turning on recordings](https://api.x3growth.io/v1/docs/behavior/recordings.md): The wizard „Aufnahmen einschalten“, what is kept and for how long, masking, the player, reconstructions without a recording, AI summaries with your own Anthropic key and deletion. - [Live and the world map](https://api.x3growth.io/v1/docs/behavior/live.md): The Live area in the main menu – live count, board with page tiles, single visitors, following a visit, the world map of current sessions, alerts, and how location is coarsened without storing IPs. - [Privacy and capture scope](https://api.x3growth.io/v1/docs/behavior/privacy-capture.md): Consent modes, the level of each signal with its risk traffic light, admin acknowledgements, generated privacy texts and everything that always stays on. - [Privacy center for visitors](https://api.x3growth.io/v1/docs/behavior/privacy-capture-center.md): The visitor's privacy panel on your site (stop capturing, show and delete my data), the public privacy page, the device proof and the opt-out link. - [Consent banners (CMP setup)](https://api.x3growth.io/v1/docs/behavior/privacy-capture-cmp.md): How to add X3 to your consent banner as a non-IAB vendor, report the visitor's choice per purpose and set it up in Usercentrics, Cookiebot, Borlabs, Complianz and others. ## Experiments - [Experiments (A/B tests)](https://api.x3growth.io/v1/docs/experiments/overview.md): Test funnel and quiz steps, button texts, headlines, videos, layouts and offers – with a pre-registered runtime, an honest rule and an automatic switch to the better version. - [Experiments in the SDK](https://api.x3growth.io/v1/docs/experiments/sdk.md): x3.variant(), x3.experiment(), x3.expose() and x3.experiments.ready() in the browser, the script-tag callback form and the React hooks useVariant, useExpose and . - [Experiments with Next.js and on the server](https://api.x3growth.io/v1/docs/experiments/next.md): getAssignments() in Server Components, , , the /v1/x proxy route and the server helper's experiments.assign and leads.addNote. - [Reading an experiment's results](https://api.x3growth.io/v1/docs/experiments/results.md): The experiment page – evaluation runs, self-resolving follow-ups, arm comparison, funnel by arm, course over time, segments, revenue, behaviour per arm and new versions. - [How X3 decides](https://api.x3growth.io/v1/docs/experiments/statistics.md): The rule x3-rule-v1: fixed runtime, one decision at P(best) ≥ 0.96, always-valid harm stops and early wins, honest planner, Nicht-schlechter-Test and every outcome. - [Experiment units and privacy](https://api.x3growth.io/v1/docs/experiments/privacy.md): Which unit is randomised per consent mode – page load, cookieless visit-day, consented visitor – what is never stored, honest bias statements and the public fields of an experiment. - [Experiments with Claude](https://api.x3growth.io/v1/docs/experiments/claude-workflow.md): What Claude does from idea to cleanup – honest plan, both arms with SDK flags, QA without side effects, start after your deploy, no early winners – with the MCP tools and prompts. - [Cleaning up after the decision](https://api.x3growth.io/v1/docs/experiments/cleanup.md): Remove the losing arms, hardcode the applied one and let the cleanup task resolve itself – and why X3 keeps answering the applied arm for 90 days. ## SDK - [Script tag](https://api.x3growth.io/v1/docs/sdk/script-tag.md): Install 3x with one script tag – builds, data attributes, the queue stub, plugins and the inline client config. - [npm package](https://api.x3growth.io/v1/docs/sdk/npm.md): Install @x3growth/sdk from npm – entry points, init options, plugins and tree-shaking. - [React](https://api.x3growth.io/v1/docs/sdk/react.md): X3Provider and useX3 for React apps – one tracker per app, StrictMode-safe, router-agnostic. - [Next.js](https://api.x3growth.io/v1/docs/sdk/nextjs.md): The X3Analytics component, server-fetched client config, CSP nonces and the proxy route for the App and Pages routers. - [SDK reference](https://api.x3growth.io/v1/docs/sdk/reference.md): Every method of the browser SDK – init, track, goal, funnelStep, page, identify, conversion, consent, flush, getIds, opt-out and the preset helpers. - [Custom events and presets](https://api.x3growth.io/v1/docs/sdk/events.md): Track your own events, register schemas for typed props, keep cardinality in check, and use the quiz, CTA, WhatsApp, calculator and booking presets. - [Data attributes](https://api.x3growth.io/v1/docs/sdk/data-attributes.md): Declarative tracking with data-x3-* attributes – custom click events, CTAs, labels, sections, videos, forms, ignore zones and 404 markers. - [Consent and CMPs](https://api.x3growth.io/v1/docs/sdk/consent.md): Wire your cookie banner or CMP to 3x – consent modes, the consent key, window events, built-in CMP adapters and the x3.consent() API. - [Identify and leads](https://api.x3growth.io/v1/docs/sdk/identify.md): Link sessions to people with identify() (hashed in the browser) or create leads server-side with plaintext only when the project allows it. - [Video](https://api.x3growth.io/v1/docs/sdk/video.md): Second-by-second video retention for HTML5 video, custom players, YouTube and Vimeo – plays, coverage, rewatches, drop-off zones, formats and completion. - [Sections](https://api.x3growth.io/v1/docs/sdk/sections.md): Section reach – which parts of a page are seen, how early and for how long, with stable section names. - [Forms](https://api.x3growth.io/v1/docs/sdk/forms.md): Form starts, submits and abandons without ever reading a field value. - [Auto-capture – outbound links, downloads, 404 pages](https://api.x3growth.io/v1/docs/sdk/auto-capture.md): What X3 counts without extra code, the per-project switches, how 404 pages are recognized (marker, meta tag, title rule) and where the results show up. - [Server helper](https://api.x3growth.io/v1/docs/sdk/server.md): @x3growth/sdk/server – leads, conversions and server-side events from Node or edge runtimes with a secret key, plus requestContext(). - [Content Security Policy](https://api.x3growth.io/v1/docs/sdk/csp.md): CSP directives for 3x with and without the first-party proxy, the hash of the inline stub, nonces and strict-dynamic. - [Troubleshooting](https://api.x3growth.io/v1/docs/sdk/troubleshooting.md): No data, 403s, missing sessions, merged visitors, missing events – how to find out what is wrong. - [Leads from the browser – x3.lead()](https://api.x3growth.io/v1/docs/sdk/lead.md): Send a form's lead to X3 straight from the page (no own server needed); X3 checks for spam and pushes it to your CRM in the background. - [Built-in event catalog](https://api.x3growth.io/v1/docs/sdk/event-catalog.md): Every built-in event with props, presets, delivery rules and labels. ## Frameworks - [Framework recipes](https://api.x3growth.io/v1/docs/frameworks.md): Install recipes per framework – and the machine-readable format Claude Code and the dashboard use to generate install steps. - [Next.js App Router](https://api.x3growth.io/v1/docs/frameworks/next-app.md): Install 3x in a Next.js App Router project – X3Analytics in the root layout, optional /n3 proxy route, consent and events. - [Next.js Pages Router](https://api.x3growth.io/v1/docs/frameworks/next-pages.md): Install 3x in a Next.js Pages Router project – X3Analytics in _app, optional API-route proxy, consent and events. - [React + Vite](https://api.x3growth.io/v1/docs/frameworks/react-vite.md): Install 3x in a React single-page app built with Vite – init before render, host-level proxy, consent and events. - [Astro](https://api.x3growth.io/v1/docs/frameworks/astro.md): Install 3x in an Astro site – script tag in the base layout, view transitions, SSR proxy endpoint, consent and events. - [WordPress](https://api.x3growth.io/v1/docs/frameworks/wordpress.md): Install 3x on WordPress with a must-use plugin – enqueue with data attributes, REST-route proxy, consent plugins and events. - [Webflow and plain HTML](https://api.x3growth.io/v1/docs/frameworks/webflow-html.md): Install 3x on Webflow, static HTML or any CMS with a head-code field – snippet, custom attributes, worker or CNAME proxy. - [Shopify](https://api.x3growth.io/v1/docs/frameworks/shopify.md): Install 3x on Shopify – theme snippet for the storefront and a custom web pixel for checkout events, with Customer Privacy consent. - [Any other site](https://api.x3growth.io/v1/docs/frameworks/other.md): The generic recipe – Vue, Nuxt, SvelteKit, Remix, Rails, Django, Laravel, Hugo or any server-rendered site. ## Proxy - [First-party proxy](https://api.x3growth.io/v1/docs/proxy.md): Why and how to route 3x through your own domain – ad-block resilience, correct visitor separation, the signed proxy protocol and its rules. - [Next.js route handler](https://api.x3growth.io/v1/docs/proxy/nextjs.md): The first-party proxy as a Next.js App Router route handler with createX3ProxyHandler – also usable in any Fetch-API runtime. - [Cloudflare Worker](https://api.x3growth.io/v1/docs/proxy/cloudflare-worker.md): The first-party proxy as a Cloudflare Worker route on your zone – for any site behind Cloudflare, including Webflow and static hosting. - [Nginx](https://api.x3growth.io/v1/docs/proxy/nginx.md): The first-party proxy as an Nginx location block with the proxy key, client IP and script caching. - [Netlify edge function](https://api.x3growth.io/v1/docs/proxy/netlify.md): The first-party proxy as a Netlify edge function – redirects cannot set headers, so an edge function forwards IP, country and the proxy key. - [WordPress REST route](https://api.x3growth.io/v1/docs/proxy/wordpress.md): The first-party proxy as a WordPress REST route – forwards events and scripts with wp_remote_request, IP and proxy key. - [CNAME subdomain](https://api.x3growth.io/v1/docs/proxy/cname.md): The no-code option – a subdomain such as t.example.com pointing at the 3x API; first-party by host, with its limits. - [Proxy paths for recordings, heatmaps and live](https://api.x3growth.io/v1/docs/proxy/recordings-paths.md): The extra path families the SDK uses for recordings, the live view, page snapshots and the privacy center, their body limits, the geo header, and how to add them to each proxy recipe. ## API - [Authentication and keys](https://api.x3growth.io/v1/docs/api/authentication.md): Publishable, secret, proxy and session credentials – how to create, scope, roll and revoke them. - [Scopes and roles](https://api.x3growth.io/v1/docs/api/scopes.md): What each scope allows, which roles hold it, and the OAuth consent sets. - [Errors](https://api.x3growth.io/v1/docs/api/errors.md): RFC 9457 problem details – every error code 3x returns, what causes it and what to do. - [Pagination](https://api.x3growth.io/v1/docs/api/pagination.md): Cursor pagination, sorting, column filters, search, field selection and CSV exports of list endpoints. - [Idempotency](https://api.x3growth.io/v1/docs/api/idempotency.md): Safe retries with the Idempotency-Key header and natural event ids for conversions and events. - [Filters](https://api.x3growth.io/v1/docs/api/filters.md): The analytics filter shared by REST, MCP and the dashboard – date ranges, UTMs, click ids, channels, devices, pages, behaviour, relevance and ads. - [Background runs and live progress (SSE)](https://api.x3growth.io/v1/docs/api/background-runs.md): Background work (first sync, sync now, conversion uploads, preset apply, imports) runs as a run with live progress, an outcome and an idempotent start – via SSE or polling. - [Rate limits and quotas](https://api.x3growth.io/v1/docs/api/rate-limits.md): Request limits per IP and principal, daily ingest budgets and per-project quotas. - [Ingest protocol](https://api.x3growth.io/v1/docs/api/ingest.md): The wire format and processing rules of POST /v1/e – for SDK authors, proxies and debugging. - [API reference](https://api.x3growth.io/v1/docs/api/reference.md): Every REST endpoint with auth, scopes, parameters and response – generated from the route contracts. ## MCP - [MCP server](https://api.x3growth.io/v1/docs/mcp.md): Let Claude analyse your traffic, manage projects and install 3x on a website through the Model Context Protocol. - [Claude Code](https://api.x3growth.io/v1/docs/mcp/claude-code.md): Connect Claude Code to X3 – keyless OAuth sign-in or a secret key created in the onboarding – and let it install X3 on your site. - [claude.ai connector](https://api.x3growth.io/v1/docs/mcp/claude-ai.md): Add X3 as a custom connector in claude.ai or Claude Desktop with OAuth 2.1 (dynamic client registration, PKCE). - [Claude skill and plugin](https://api.x3growth.io/v1/docs/mcp/claude-skill.md): The Claude skill x3-connect-website lets Claude connect a website to X3 end to end – install it as the plugin x3 from the public marketplace X3Growth/x3-claude, or use the MCP prompt connect_website. - [ChatGPT, Gemini and other apps](https://api.x3growth.io/v1/docs/mcp/other-apps.md): Connect the X3 MCP server to ChatGPT, Gemini CLI, Cursor, VS Code and any other MCP client – and which apps cannot connect yet (Grok, the Gemini app). - [Tools](https://api.x3growth.io/v1/docs/mcp/tools.md): Every MCP tool with its scope and purpose – insights, analysis, leads, conversions, ads, Search Console, annotations, weekly reports, share links, configuration and developer tools. - [Resources and prompts](https://api.x3growth.io/v1/docs/mcp/resources.md): MCP resources (docs, OpenAPI, schemas, project config, setup status, onboarding prompts, the Claude skill) and prompts (connect a website, onboarding, reports, presets). ## Ads - [Ads overview](https://api.x3growth.io/v1/docs/ads.md): Import spend from Google, Meta, LinkedIn and TikTok Ads through Composio and see what a relevant session and a lead really cost. - [Composio setup](https://api.x3growth.io/v1/docs/ads/composio-setup.md): Configure Composio once per 3x deployment – project API key, one auth config per ad platform, toolkit versions and the webhook. - [Connect Google Ads](https://api.x3growth.io/v1/docs/ads/google.md): Connect a Google Ads account or manager (MCC) account, select client accounts, and get exact click-level matches through the click view. - [Connect Meta Ads](https://api.x3growth.io/v1/docs/ads/meta.md): Connect Facebook and Instagram ad accounts with OAuth or a system-user token and import spend per campaign, ad set and ad. - [Connect LinkedIn Ads](https://api.x3growth.io/v1/docs/ads/linkedin.md): Connect LinkedIn Campaign Manager accounts through your own LinkedIn app and import spend per campaign group, campaign and creative. - [Connect TikTok Ads](https://api.x3growth.io/v1/docs/ads/tiktok.md): Connect TikTok For Business advertiser accounts and import spend per campaign, ad group and ad. - [UTM templates](https://api.x3growth.io/v1/docs/ads/utm-templates.md): Copy-paste UTM templates per ad platform that put platform ids into your URLs, so every session matches its exact campaign and ad. - [Matching sessions to ads](https://api.x3growth.io/v1/docs/ads/matching.md): The seven match methods that assign a session to a platform, campaign, ad set or ad – and how to fix unmatched UTMs with mapping rules or by naming unknown campaigns. - [Clean ad-level matching (Anzeigen sauber zuordnen)](https://api.x3growth.io/v1/docs/ads/clean-ad-matching.md): Why visits land in „Anzeige nicht erkennbar“, how X3 detects it (task „Anzeigen nicht zuordenbar“), and the URL parameter templates that match every visit to its exact ad. - [Cost KPIs](https://api.x3growth.io/v1/docs/ads/cost-kpis.md): Exact formulas for CPC, CTR, CPM, cost per session, cost per interested and hot visit, CPL, lead rate, interested and hot share, contact attempts, ROAS and the caveats behind them. - [Delivery status of campaigns, ad sets and ads](https://api.x3growth.io/v1/docs/ads/delivery-status.md): One status vocabulary across Meta, Google, LinkedIn and TikTok, paused parents applied to their children, „seit“ dates, status history and the filters of the sources report. ## Conversions - [Conversions overview](https://api.x3growth.io/v1/docs/conversions.md): Set up server-side conversion uploads to Meta, LinkedIn, Google Ads and TikTok – definitions, destinations, recording paths and status. - [Conversion definitions](https://api.x3growth.io/v1/docs/conversions/definitions.md): Define what counts as a conversion – trigger, source, value, per-platform mapping and server confirmation – with examples for common lead funnels. - [Meta Conversions API](https://api.x3growth.io/v1/docs/conversions/meta.md): Send conversions to Meta (Facebook/Instagram) through the Conversions API – pixel, access token, test event code and pixel deduplication. - [LinkedIn Conversions API](https://api.x3growth.io/v1/docs/conversions/linkedin.md): Send conversions to LinkedIn Campaign Manager through the Conversions API – conversion rules, access token, identifiers and version upkeep. - [Google Ads conversions](https://api.x3growth.io/v1/docs/conversions/google-ads.md): Upload offline click conversions to Google Ads with the scheduled CSV feed (no developer token) or the Google Ads API, including MCC access and enhanced conversions for leads. - [TikTok Events API](https://api.x3growth.io/v1/docs/conversions/tiktok.md): Send conversions to TikTok through the Events API – pixel code, access token, identifiers and test events. - [Test modes](https://api.x3growth.io/v1/docs/conversions/test-modes.md): How dry_run, test and live interact with the deployment ceiling, the kill switch and local provider mocks – so development never uploads real conversions. - [Troubleshooting conversions](https://api.x3growth.io/v1/docs/conversions/troubleshooting.md): Every upload status and common error with its cause and fix – skipped, not_configured, failed, error, held and missing conversions. - [Shop purchases and refunds](https://api.x3growth.io/v1/docs/conversions/purchases.md): Report every purchase with value, currency and order id to Meta, Google Ads and TikTok – from your server (REST or the server helper), refunds, currencies and the counting rule per project mode. - [CRM – leads into HubSpot or Pipedrive, revenue back into X3](https://api.x3growth.io/v1/docs/crm/overview.md): Connect your CRM once; X3 pushes every inquiry there (dedupe first, spam held back) and reads meetings and won deals back – status, revenue and the real ROAS of your campaigns. - [HubSpot](https://api.x3growth.io/v1/docs/crm/hubspot.md): Permissions, fields, notes, deals and meetings of the HubSpot connection. - [Pipedrive](https://api.x3growth.io/v1/docs/crm/pipedrive.md): API key, persons with several emails, custom fields, deals and activities of the Pipedrive connection. ## Optional - [Complete documentation](https://api.x3growth.io/llms-full.txt): every guide in one markdown file - [Self-hosting overview](https://api.x3growth.io/v1/docs/self-hosting.md): Run your own 3x deployment – components, hosting options, required secrets and what the operator is responsible for. - [Vercel + Neon](https://api.x3growth.io/v1/docs/self-hosting/vercel-neon.md): Deploy the 3x API and dashboard as two Vercel projects with a Neon Postgres database, cron, and the settings each Vercel plan needs. - [Standalone Node](https://api.x3growth.io/v1/docs/self-hosting/standalone.md): Run the 3x API as a plain Node 22 process with the in-process scheduler behind nginx, Caddy or Cloudflare, and the dashboard as a Next.js server. - [Environment reference](https://api.x3growth.io/v1/docs/self-hosting/environment.md): Every environment variable of the 3x API, dashboard and example app – required values, defaults, per-platform IP headers, cron budget, storage guard and Composio. - [Cron and background jobs](https://api.x3growth.io/v1/docs/self-hosting/cron.md): How the 3x scheduler runs retention, salts, rollups, conversion retries and ad syncs – on Vercel Cron, an external scheduler or in-process. - [Migrations](https://api.x3growth.io/v1/docs/self-hosting/migrations.md): How 3x's plain-SQL migrations are applied, checked and written – numbering ranges, transactions, checksums and the read-only SQL role. - [Upgrading](https://api.x3growth.io/v1/docs/self-hosting/upgrading.md): Upgrade a 3x deployment safely – order of API, migrations and dashboard, SDK versions on sites, and rollback.