Formo Alternative: Pantheon vs Formo

Formo describes itself as an analytics and attribution platform for onchain apps, and its documentation supports that description in detail. The product analytics guide covers page visits, custom events, funnels, retention, contract events, charts, and alerts. A growth team can see whether an acquisition campaign brought people to an app, whether they connected wallets, and where they stopped before a transaction. For a DeFi product with anonymous visitors and onchain conversions, that is a concrete measurement problem.

Its attribution guide describes connecting offchain touchpoints such as referrals and UTM parameters to onchain conversions, with first-touch and last-touch models. The example journey moves from a social referral to a website visit, wallet connection, an abandoned swap, and a later completed swap. This is more than counting addresses: it is an attempt to make product and channel decisions from the full event path. A marketing lead can compare campaigns using the same conversion definition rather than attributing every deposit to the last link clicked.

Formo's wallet intelligence guide describes wallet profiles, audience insights, segmentation, labels, and lifecycle stages. It also says wallets sharing a session or common user ID can be grouped, and teams can export segments as CSV. That corrects a common oversimplification: Formo does have identity features, but their purpose is understanding app users and wallets. Its chains page lists Ethereum, major EVM networks, and Solana, with a feature matrix that varies by chain. If chain coverage is decisive, check the exact row for your chain and feature rather than assuming every capability applies everywhere.

Formo's product analytics documentation begins with instrumentation of visits and events, then funnels and retention reports. Its wallet guide shows a Users table of wallets that connected to the app, with metrics such as lifecycle stage and last seen. A profile can show activity, applications used, tokens, custom properties, and labels. A team can filter wallets into a segment and export that segment for a targeted campaign. Those are analytics objects: event, session, wallet, segment, and attributed conversion.

Picture a Tuesday for a DeFi growth manager. In the morning, they inspect yesterday's funnel from landing page to wallet connect to swap. They notice an illustrative drop-off at the approval step and check the attribution model to see whether a referral campaign is bringing users who reach the app but do not complete. At lunch, they open a wallet profile to see onchain activity and create a segment of returning users. In the afternoon, they review contract-event and chain support for a new market. Use your own funnel data to measure the real drop-off.

Formo's FAQ says it can run alongside existing analytics tools and recommends aligning event names, identity rules, time zones, attribution windows, and conversion definitions before comparing dashboards. That is sound advice for any buyer evaluating measurement. If the same person uses two wallets, Formo can group them when they share a session or user ID, according to its wallet guide. That still requires the team to know what an app session proves about a person and to avoid treating a wallet label as a verified real-world identity. This distinction matters when data later informs outreach.

Pantheon helps answer who is in a conversation, what was said, and what needs to happen next (Telegram CRM details). It describes supported Telegram conversations alongside contacts, companies, deals, notes, and WhatsApp, iMessage, and X/Twitter coverage. The operator can read captured history, search, and keep a next step near the contact (unified inbox). For this workflow, WhatsApp and iMessage run through the Mac app. Pantheon does not capture Instagram DMs. Pantheon is invite-only alpha.

Suppose a protocol's partnerships lead meets a market maker in a Telegram group. They discuss an integration in a DM, then continue over WhatsApp because a colleague joins the conversation. A wallet dashboard can show what a wallet did in the product. The operator still needs to find the human conversation about launch timing, inspect a suggested cross-channel match, approve it if the handles and number check out, and record the proposed next step. That is the job of the relationship record. It is not a claim that Pantheon automatically identifies a wallet holder or proves ownership of an address.

The products can inform each other through a human workflow. A Formo segment might show that a cohort of users is reaching a milestone or at risk of leaving. A BD lead might then review a specific partner relationship in Pantheon before deciding whether a personal follow-up makes sense. Do not paste anonymous wallet labels into a contact record as if they were verified identities. If a participant supplies a wallet address directly, record that provenance and consent in the team's own process. This keeps analytics and private correspondence useful without conflating two different evidence types.

As of November 2026, Formo's official pricing page displays Growth at $199 per month billed yearly and Scale at $399 per month billed yearly. Growth includes up to 5,000 monthly active users and core web, product, wallet, and token-gated form features. Scale lists up to 10,000 monthly active users and adds API and MCP access, wallet imports, and contract events. Enterprise is custom. The page advertises a seven-day trial and a monthly or annual toggle; the readable figures here are specifically the yearly-billed monthly equivalents, not a confirmed month-to-month quote.

The plan matrix also lists one year of data retention on Growth and two years on Scale and Enterprise. That is a material analytical horizon for cohort comparison, and it belongs beside the price. A team should estimate current monthly active users, expected event usage, whether contract events are required, and how long it needs to compare retention. Ask about the definition of monthly active user and any usage-based exceptions before committing. A $199 label alone does not tell you if your deployment fits the tier.

Pantheon does not publish a price; access is by invitation during the alpha. For a side-by-side budget, avoid treating the products as substitutes at equal units. Formo is priced around an analytics deployment and user volume; Pantheon should be evaluated around the operator's supported accounts and relationship workflow. Ask each vendor for current terms and keep the two budget lines separate if both jobs matter.

Formo lists annual-billing figures for Growth and Scale. Reopen Formo's pricing page at purchase, because a toggle can change the displayed rate and the annual commitment matters.

Formo's data collection documentation explains what its SDK gathers and the role of first-party identifiers. Its FAQ says it does not use third-party tracking cookies or device fingerprinting, and does not automatically collect email addresses, phone numbers, or private social profiles. A growth team can still send custom properties and identify users, so the team's own implementation choices matter. Do not interpret a privacy-friendly default as permission to put personal messaging content into event properties.

The security page states that connections use TLS 1.2+ and labels SOC 2 as in progress. That wording should not be reported as a completed certification. Formo's privacy policy addresses service data and personal information, and its pricing matrix lists data retention by tier. A buyer should ask which analytics events are retained, which identity fields it sends through the SDK, and whether exported segments carry personal identifiers. The wallet guide says segments can be exported as CSV and profiles can be queried through an API, so access to those exports deserves its own review.

Pantheon keeps captured private messages with the relationship record (unified inbox). A buyer should ask a different set of questions: which conversations should be imported, who may see them, and what consent is appropriate for group chats? When an X handle, WhatsApp number, and Telegram account look related, the operator reviews and approves the suggested match. That is safer than treating a shared display name as proof. For either product, use a small trial with data you are authorized to process, then inspect the actual records and exports rather than extrapolating from a feature page.

These are different data surfaces. Formo's event tracking can be broad but pseudonymous by default; Pantheon's correspondence is directly tied to identifiable people. The relevant privacy control is the one that fits the data you plan to put in each system.

They can run side by side without forcing a direct integration. Formo's FAQ explicitly discusses parallel analytics deployments and recommends aligning event names, identity rules, time zones, and attribution windows. Pantheon keeps relationships and conversation history together (Telegram CRM details). If a growth analyst spots a wallet cohort, the team can discuss a campaign in the analytics workspace; an operator can separately review a known partner's contact record before following up. One system measures behavior; the other holds the relationship conversation.

For a pilot, choose one launch or acquisition campaign and one named partner relationship. Instrument the launch in Formo and verify a page visit, wallet connect, and conversion event against your own app logs. Check the chain and feature matrix in the chains docs. In Pantheon, verify an older Telegram conversation, the partner's other supported channel, and a note or deal. Approve any identity suggestion only when you can confirm it. The success measures differ: consistent funnel counts for Formo, and retrievable context with correct identity for Pantheon.

If switching analytics tools, Formo documents segment CSV export and API access. Ask whether the exact historical events, attribution rules, and cohort definitions you need can leave under your plan. Rebuild a small report in the destination and compare counts using the same time zone and conversion definition. If switching relationship CRMs, list contact fields, notes, deals, and source conversations separately. Formo and Pantheon have no one-click sync, and their records do not map one-to-one. Plan a reviewed handoff rather than an implied migration path.

Choose Formo when the budget owner needs to understand acquisition, wallet behavior, and conversion for an onchain app. Its analytics guide, attribution guide, and wallet profiles provide the mechanisms. A product manager deciding where users abandon a swap, or a growth lead comparing referral campaigns, should trial those reports with known events. Confirm the supported chains and plan limits first.

Choose Pantheon when a founder, investor, or BD operator is losing context about known people across the supported messaging channels. Pantheon assembles a contact record from conversations, with notes, companies, deals, and search (CRM details). That person may care about a wallet's activity, but their immediate task is recalling who promised what and following up with the right human. Pantheon's alpha status and supported-device limits mean the operator should test actual threads, not buy from an abstract channel list.

Choose both when product analytics and relationship management have distinct owners. Let Formo's data answer which cohorts or campaigns need attention; let a person decide whether an individual relationship warrants outreach and review the actual conversation in Pantheon. Do not promise automatic wallet-to-person identification from this pairing. For the Telegram side of the decision, see the Telegram CRM page, best Telegram CRM guide, and what is a Telegram CRM. Formo's job remains analytics even when the same web3 team needs both tools.