# Zijra — expanded public reference

> Privacy-first web analytics with revenue tracking through Stripe. Canonical website: https://zijra.com. This is public product documentation, not access to a customer's reports.

## Core reporting

Zijra measures observed visitors or anonymous sessions, pageviews, referrers, UTM campaigns, pages, countries, browsers, devices and hostnames. Reports support website-local dates, filters, saved goals, ordered funnels, CSV exports and revenue attribution. Prior-period comparisons retain actual prior dates. Daily/weekly channel stacks use measured pageviews; hourly heatmaps preserve actual timestamps and repeated/skipped local hours. Missing historical facts remain unavailable rather than becoming invented zeros or distributions.

Private Online country activity uses a five-minute observation window and complete authorized aggregates. Bounded activity replay shows up to eight hours of fifteen-minute country activity frames intersecting the selected period. It does not record page contents or reconstruct historical presence from today's last-seen value. Public realtime widgets separately use a thirty-minute window; those totals are not interchangeable with private Online.

Personal pinned periods and website ordering are scoped to the signed-in user. Public shared reports use deliberately issued expiring, revocable links and controlled iframe origins. They expose the selected aggregate projection, not private visitor identities or raw event histories.

## Installation

1. Sign in at [Zijra](https://zijra.com/login) and save a website with its real domain and reporting timezone.
2. Open Installation for that website. Copy its generated snippet with the actual public website ID, collector origin and saved privacy settings.
3. Add the tracker once and publish the website. The browser tracker is served from https://zijra.com/tracker.js.
4. Start a fresh verification attempt and load the published website. A historical visit alone does not prove the current installation; collection may be paused by website settings or the workspace event allowance.

The following HTML shape is illustrative. Replace the placeholder with the saved website's public ID and use the generated snippet for its exact settings:

```html
<script defer src="https://zijra.com/tracker.js"
  data-site-id="YOUR_PUBLIC_WEBSITE_ID"
  data-ignore-query="true"
  data-ignore-hash="true"
  data-respect-privacy="true"
  data-collection-mode="aggregate"></script>
```

See [Installation](https://zijra.com/docs/installation), [custom events and goals](https://zijra.com/docs/events), [funnels](https://zijra.com/docs/funnels) and [privacy](https://zijra.com/docs/privacy). Browser events do not create merchant payment revenue. Attribution-mode identity needs an explicit consent decision.

## Stripe revenue

Stripe is the released merchant revenue integration. Follow [Stripe setup](https://zijra.com/docs/stripe) to connect and verify the intended account, permissions and environment. Captured payments and refunds feed observed revenue; browser activity and trusted payment receipts remain separate sources. Live and test payments are kept separate. A payment without a matching consented visitor/session stays unattributed rather than creating a fabricated marketing journey.

## Plans and limits

| Plan | Monthly USD | Annual USD | Events per month | Websites | Team members |
| --- | ---: | ---: | ---: | --- | --- |
| Free | $0 | $0 | 10,000 | 1 website | 1 |
| Founder | $5 | $50 | 100,000 | 10 websites | 3 |
| Growth | $15 | $159 | 500,000 | Unlimited websites | 10 |
| Studio | $24 | $265 | 1,000,000 | Unlimited websites | Unlimited |
| Scale | $99 | $1,150 | 5,000,000 | Unlimited websites | Unlimited |

Annual prices are the full yearly payment, not a monthly equivalent. Event allowances reset monthly, including on annual subscriptions. All plans include Stripe revenue attribution.

Free includes 3 saved goals, 1 saved funnel and 6 months of full-detail history. Individual visitor histories and journeys, API access and MCP are paid-plan features starting with Founder. Free cannot create or use developer credentials. Current effective workspace entitlements, including valid promotional grants and eligible recorded legacy contracts, determine access; a saved plan preference or token never bypasses those checks. Credential listing/revocation and owner privacy exports remain available.

Paid plans retain 13 months of detail, then daily totals within 3 years on Founder or 5 years on Growth, Studio and Scale. A shorter website privacy/retention preference still applies. Free pauses at its included event allowance. Paid extra events cost $18 per 1M within a customer-set spending limit, default $0. Extra-event billing is not open yet; collection pauses at your included allowance.

Paid plans use Stripe. Start free with 10,000 events per month; paid plans start at $5 per month. Zijra subscription billing is separate from a website's merchant revenue connection. Billing settings report current checkout availability; an account's subscription is established by verified billing state, not by this reference.

## API, MCP and command-line access

API and MCP are paid-plan features starting with Founder. Scoped developer credentials require current effective entitlements and website permissions. A token's permissions cannot expand its website allowlist or bypass current issuer membership, expiry, revocation or private-data consent requirements. Configure credentials in the client or local environment; do not place real secrets in URLs or public examples.

- [API guide](https://zijra.com/docs/api): Versioned analytics, breakdowns, measured goal/funnel reports and other permission-scoped resources.
- [MCP guide](https://zijra.com/docs/mcp): Website-scoped HTTP tools and the configured OAuth connection flow.
- [CLI guide](https://zijra.com/docs/cli): Downloadable Node.js helper and supported commands. It is not a published npm package.

REST analytics endpoint shape: `https://zijra.com/api/v2/websites/YOUR_WEBSITE_ID/analytics`.
MCP endpoint shape: `https://zijra.com/api/mcp/v2/YOUR_WEBSITE_ID`.
Use the real internal website ID and an authorized scoped client; these shapes are not public report URLs. API examples use `Authorization: Bearer YOUR_SCOPED_TOKEN`. Exact resource scopes, write confirmation and client approval requirements are described in the guides. Do not assume another analytics product's endpoint, CLI package, credential prefix or authentication flow applies to Zijra.

## Documentation directory

- [Get started in 4 steps](https://zijra.com/docs/getting-started): Save a website, install the tracker, receive a visit and explore your report.
- [Install Zijra](https://zijra.com/docs/installation): Use your website’s actual public ID and collector origin.
- [Custom events and goals](https://zijra.com/docs/events): Record actions and define goals. Free includes 3 saved goals.
- [Conversion funnels](https://zijra.com/docs/funnels): Measure ordered page or goal steps. Free includes 1 saved funnel; journeys require a paid plan.
- [Dates, filters and exports](https://zijra.com/docs/filters): Explore the same selection across the chart, breakdowns and CSV.
- [Privacy and visitor identity](https://zijra.com/docs/privacy): Anonymous sessions are the default. Persistent identity needs explicit consent.
- [Stripe](https://zijra.com/docs/stripe): Connect an approved account, sync captured payments and keep refunds and test data separate.
- [Lemon Squeezy](https://zijra.com/docs/lemon-squeezy): Coming soon: planned store orders, refunds and checkout metadata.
- [Polar](https://zijra.com/docs/polar): Coming soon: planned organization orders and checkout metadata.
- [Paddle](https://zijra.com/docs/paddle): Coming soon: planned transaction notifications and reconciliation.
- [Other payment providers](https://zijra.com/docs/other-payments): Coming soon: planned payment providers. Stripe is available today.
- [Server Payment API](https://zijra.com/docs/payment-api): Coming soon: a separate trusted-server receipt and refund connection.
- [Google Search Console](https://zijra.com/docs/google-search-console): Coming soon: planned search queries and verified property access.
- [GitHub](https://zijra.com/docs/github): Coming soon: planned repository commit annotations.
- [Import historical data](https://zijra.com/docs/import): Privately upload native Plausible ZIPs or daily CSV totals, then preview, commit and roll back.
- [Widgets and shared reports](https://zijra.com/docs/widgets): Share selected aggregates with expiring links and controlled iframe embeds.
- [Reports, alerts and invitations](https://zijra.com/docs/notifications): Set alert thresholds and invite teammates. Scheduled email reports are coming soon.
- [Report API](https://zijra.com/docs/api): Paid plans: read reports, dimensions, goals, event counts and funnels with a website-scoped token.
- [Connect an MCP client](https://zijra.com/docs/mcp): Paid plans: use permission-scoped tools or an owner-configured OAuth connection.
- [Zijra CLI](https://zijra.com/docs/cli): Download the command-line client and use your website-scoped permissions.
- [Feature availability](https://zijra.com/docs/status): See which flows collect real data and which still need a provider connection.
- [Meta Ads](https://zijra.com/docs/meta-ads): Coming soon: planned ad-account campaign spend and visit comparisons.
- [X mentions and attribution](https://zijra.com/docs/x): Coming soon: planned link mentions with separately labelled post authors.
- [Verified AI crawlers](https://zijra.com/docs/ai-crawlers): Coming soon: planned verified server crawler observations, separate from human visits.
- [Dodo Payments](https://zijra.com/docs/dodo): Coming soon: planned payments, refunds and subscription updates.
- [Shopify](https://zijra.com/docs/shopify): Coming soon: planned store orders, refunds and signed updates.
- [WooCommerce](https://zijra.com/docs/woocommerce): Coming soon: planned store order and refund reconciliation.
- [Easytool and external feeds](https://zijra.com/docs/easytool): Coming soon: planned merchant-controlled payment feeds.
- [Proxy installation](https://zijra.com/docs/proxy): Forward exact tracker and collector routes without exposing server credentials.
- [Plans, usage and subscription billing](https://zijra.com/docs/billing): Compare Free, Founder, Growth, Studio and Scale; understand event limits, spending caps and billing availability.
- [Account security and deletion](https://zijra.com/docs/account-security): Manage sessions, authenticator verification and private account deletion.

## Availability and privacy

Stripe is the released revenue integration. A customer still needs to connect and verify their own merchant account. Paddle, Lemon Squeezy, Polar, Shopify, WooCommerce, Dodo, Search Console, GitHub and the other catalog connections are coming soon. A provider logo, adapter or demo result is not evidence of a connected account. Consult [Feature availability](https://zijra.com/docs/status) for current boundaries.

Cookieless aggregate collection is the default. Persistent visitor identity and attributed profiles require explicit consent and the relevant permissions. Anonymous artwork is local decorative illustration, not an inferred name or profile photograph. The browser collector filters recognized bot user agents before storage and usage accounting; unknown or spoofed agents may still pass. This does not block crawlers from a customer's website.

Coarse country activity replay uses aggregate time frames; it is not a session recording, GPS location or travel path. Session replay, A/B testing and scheduled email reports are not available. Historical daily totals cannot reconstruct individual identities, channel distributions or hourly activity; unavailable details remain gaps.

Private reports and account tools require authorization, current workspace access and appropriate plan permissions. Test payments stay separate from live revenue; unmatched payments remain unattributed. Deployment configuration and successful provider sync determine actual connection/delivery availability. Available code paths do not establish full DataFast feature parity or live provider approval.

English and Arabic interface labels are available, with right-to-left Arabic layouts. Authored documentation and long-form product copy remain in English. Changing the interface language does not change a website's saved reporting timezone or payment currency. These public references remain in English and contain no account-specific data.

## Canonical public resources

- [AI-readable index](https://zijra.com/llms.txt)
- [Expanded reference](https://zijra.com/llms-full.txt)
- [Pricing](https://zijra.com/pricing)
- [Documentation](https://zijra.com/docs)
- [Privacy](https://zijra.com/privacy)
- [Terms](https://zijra.com/terms)
- [Data processing](https://zijra.com/dpa)