Faurya is a privacy-focused web analytics platform that helps you understand your website visitors, track marketing performance, and grow your revenue without compromising user privacy.

Is Faurya GDPR compliant?

Faurya is designed for privacy-aware analytics workflows. Customers should review the Privacy Policy and Data Processing Agreement and apply consent and notice controls required for their jurisdiction.

How is Faurya different from Google Analytics?

Faurya focuses on practical growth reporting with source, funnel, journey, and outcome context in one workflow. Teams should compare tools based on implementation needs, reporting depth, and policy requirements.

Funnels tools

Name: Faurya
Availability: InStock
Rating: 4.9 (120 reviews)
Author: Faurya

The funnels feature includes read and write tools. Read access can analyze unsaved funnels and inspect saved funnels. Write access can create, update, and permanently delete saved funnels.

Supported access levels

Access	Supported	Allows
Read	Yes	`faurya_analyze_funnel`, `faurya_list_funnels`, `faurya_get_funnel`.
Write	Yes	`faurya_create_funnel`, `faurya_update_funnel`, `faurya_delete_funnel`. Write implies read.

Role requirements and site scoping

Funnels tools require the matching funnels:read or funnels:write scope for the selected site. Supply siteId for multi-site connections.

Funnel step model

faurya_analyze_funnel accepts unsaved analysis steps with type (page, event, goal) and value, up to 10 steps. Saved funnel tools accept 1-8 ordered steps. A full page step can use:

{
  "order": 1,
  "id": "step_1",
  "name": "Visits pricing",
  "type": "page",
  "condition": "Equals",
  "value": "/pricing"
}

Saved page conditions are Equals, Contains, Starts With, Ends With, Does not equal, Does not contain, and Wildcard pattern. Goal step conditions are Completes and Does not completes. Page paths are normalized to a single leading slash.

Tool summary

Tool	Access	Purpose
`faurya_analyze_funnel`	Read	Analyzes an unsaved page, event, or goal funnel.
`faurya_list_funnels`	Read	Lists saved funnels with cursor pagination.
`faurya_get_funnel`	Read	Reads one saved funnel and ordered steps.
`faurya_create_funnel`	Write	Creates a saved dashboard funnel.
`faurya_update_funnel`	Write	Updates funnel name or steps.
`faurya_delete_funnel`	Write	Permanently deletes a saved funnel.

Analyze a funnel from /pricing to signup over the last 30 days.

Input

Parameter	Type	Required	Description
`period`	object	No	`start`, `end`, `timezone`.
`steps`	array	Yes	1-10 steps; each has optional `type` (`page`, `event`, `goal`) and `value` max 512 chars.
`dimensions`	string[]	No	Up to 2 public dimensions.
`limit`	integer	No	Max `200`.
`siteId`	string	Conditional	Required for multi-site connections.

Example MCP input

{
  "siteId": "site_example",
  "period": { "start": "2026-07-01", "end": "2026-07-18" },
  "steps": [
    { "type": "page", "value": "/pricing" },
    { "type": "goal", "value": "signup" }
  ]
}

Output

data contains conversion counts, drop-off, rates, and optional breakdown rows.

Example output

{
  "success": true,
  "requestId": "req_example",
  "data": {
    "steps": [
      { "name": "/pricing", "visitors": 120 },
      { "name": "signup", "visitors": 24 }
    ],
    "conversionRate": 0.2
  },
  "meta": {
    "warnings": [],
    "pagination": { "nextCursor": null, "hasMore": false }
  }
}

List my saved funnels.

Input

Parameter	Type	Required	Description
`limit`	integer	No	Positive integer, max `100`.
`cursor`	string	No	Cursor max 512 chars.
`siteId`	string	Conditional	Required for multi-site connections.

Example MCP input

{ "siteId": "site_example", "limit": 20 }

Output

data contains saved funnels and optional nextCursor.

Example output

{
  "success": true,
  "requestId": "req_example",
  "data": {
    "funnels": [
      { "id": "funnel_example", "name": "Pricing to signup", "steps": 2 }
    ],
    "nextCursor": null
  },
  "meta": {
    "warnings": [],
    "pagination": { "nextCursor": null, "hasMore": false }
  }
}

Show the saved funnel funnel_example.

Input

Parameter	Type	Required	Description
`funnelId`	string	Yes	1-256 chars.
`siteId`	string	Conditional	Required for multi-site connections.

Example MCP input

{ "siteId": "site_example", "funnelId": "funnel_example" }

Output

data contains the funnel ID, name, and ordered steps.

Example output

{
  "success": true,
  "requestId": "req_example",
  "data": {
    "id": "funnel_example",
    "name": "Pricing to signup",
    "steps": [
      {
        "order": 1,
        "id": "step_1",
        "name": "Visits pricing",
        "type": "page",
        "condition": "Equals",
        "value": "/pricing"
      }
    ]
  },
  "meta": {
    "warnings": [],
    "pagination": { "nextCursor": null, "hasMore": false }
  }
}

Create a saved funnel named Pricing to signup with pricing and signup steps.

Input

Parameter	Type	Required	Description
`name`	string	Yes	1-160 chars.
`steps`	array	Yes	1-8 simple or dashboard steps.
`siteId`	string	Conditional	Required for multi-site connections.

Example MCP input

{
  "siteId": "site_example",
  "name": "Pricing to signup",
  "steps": [
    {
      "order": 1,
      "id": "step_1",
      "name": "Visits pricing",
      "type": "page",
      "condition": "Equals",
      "value": "/pricing"
    },
    {
      "order": 2,
      "id": "step_2",
      "name": "Completes signup",
      "type": "goal",
      "condition": "Completes",
      "value": "signup"
    }
  ]
}

Output

data contains the created funnel.

Example output

{
  "success": true,
  "requestId": "req_example",
  "data": { "id": "funnel_example", "name": "Pricing to signup", "steps": 2 },
  "meta": {
    "warnings": [],
    "pagination": { "nextCursor": null, "hasMore": false }
  }
}

Rename funnel_example and add a docs page step.

Input

Parameter	Type	Required	Description
`funnelId`	string	Yes	1-256 chars.
`name`	string	Conditional	1-160 chars. Required if `steps` is omitted.
`steps`	array	Conditional	1-8 steps. Required if `name` is omitted.
`siteId`	string	Conditional	Required for multi-site connections.

Example MCP input

{
  "siteId": "site_example",
  "funnelId": "funnel_example",
  "name": "Pricing to signup v2"
}

Output

data contains the updated funnel.

Example output

{
  "success": true,
  "requestId": "req_example",
  "data": { "id": "funnel_example", "name": "Pricing to signup v2" },
  "meta": {
    "warnings": [],
    "pagination": { "nextCursor": null, "hasMore": false }
  }
}

Delete funnel_example after I confirm it is no longer needed.

Input

Parameter	Type	Required	Description
`funnelId`	string	Yes	1-256 chars.
`siteId`	string	Conditional	Required for multi-site connections.

Example MCP input

{ "siteId": "site_example", "funnelId": "funnel_example" }

Output

data confirms deletion.

Example output

{
  "success": true,
  "requestId": "req_example",
  "data": { "deleted": true, "funnelId": "funnel_example" },
  "meta": {
    "warnings": [],
    "pagination": { "nextCursor": null, "hasMore": false }
  }
}

Common errors

NOT_FOUND, INSUFFICIENT_SCOPE, VALIDATION_ERROR.

Notes

Destructive: deletion is permanent in the MCP handler description. Require explicit confirmation.

Funnels

On this page