You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: fix discrepancies between docs and latest implementation (#81)
* docs: fix discrepancies between docs and implementation
Audit of docs against ../formono (features, API, MCP, CLI, SDK, data,
security, integrations) and fixes for inaccurate or missing content.
MCP
- Document Scale/Enterprise plan requirement + 403 troubleshooting
- Correct tool table to the real allow-list (drop wallet_profiles,
top_custom_events; rename top_sources_metrics -> top_sources; add
missing tools); group top_* tools together
- lifecycle/retention/frequency are first-class tools, not SQL-only
API
- Add Get Contract page (GET /v0/contracts/{chain}/{address}) + nav
Events / SDK
- Fix version "1" -> "0"; add transaction reverted status
- Restore flattened function args (function_args is emitted both nested
and flattened) + explain the behavior
- Move address/user_id to top level in connect/disconnect/chain/
signature/identify samples
- Add paid-attribution click IDs; fix mobile network_* context fields
- Remove non-existent signatureHash from web SDK example
- Refresh stale SDK versions; reframe page-event example to a DeFi flow
Features
- Reframe Funnels/Flows/Retention as chart types (not nav pages);
rename "User Flow" chart -> "Flow"
- "Ask AI" -> "Ask Formo" across features and guides
- Audience Insights / Segments live on the Users page
- Alerts: webhook/Slack only (no Telegram/Email); User alerts gated
- Remove fabricated behavioral wallet labels; use real label categories
- Holdings tab -> Apps/Tokens
Data / Chains / Security / Integrations
- Remove unimplemented linear (multi-touch) attribution
- Catalog: real columns/types, drop non-existent chains/pages tables,
add wallet_profiles_labels
- Enable contract events for Blast/Kaia/Mode/Mode Testnet/Monad Testnet;
add Katana
- Roles: add BI-token + audit-log permissions; SSO: any SAML 2.0 IdP;
add audit log mention
- Integrations: document Slack/webhook/email via Alerts
Web SDK examples: remove Blocknative/Porto/Farcaster cards; normalize
Crossmint/Openfort/Angular labels to with-N format
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* docs: fix broken links/anchors and typos
Broken links/anchors (verified all internal links + heading anchors now
resolve, 0 broken):
- intro: /guides/ -> /guides/onchain-attribution
- custom-events: /features/wallet-intelligence -> .../overview;
/sdks/web#custom-events -> #track-events
- sdks (web/server/mobile): /data/events#events-api ->
/data/events/overview#events-api
- sdks/web + install: fix #react--nextjs / #websites / #privy /
#react-&-next-js-without-wagmi anchors; install method links now point
to the real /sdks/web#... headings
- metrics: custom-events#tracking-revenue -> #step-3-...; track comma anchor
- wallet-intelligence/overview, security/overview: drop dead anchors
Typos:
- metrics: "leave" -> "leaves"; "a search engines" -> "a search engine"
- what-we-collect: "the their time zone" -> "their time zone"
- chains: "on Ethereum on all major EVM chains" -> "and all major EVM chains"
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
description: 'Fetch a single monitored smart contract by chain ID and address. Returns the contract address, chain ID, ABI, and event tracking configuration.'
Copy file name to clipboardExpand all lines: data/attribution.mdx
+6-8Lines changed: 6 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: 'Attribution'
3
3
icon: magnifying-glass-chart
4
-
description: 'Learn why onchain attribution matters for sustainable growth and how Formo calculates multi-touch attribution from first click to wallet transaction.'
4
+
description: 'Learn why onchain attribution matters for sustainable growth and how Formo attributes conversions from first click to wallet transaction.'
5
5
iconType: solid
6
6
---
7
7
@@ -39,11 +39,10 @@ Consider the following example user journey for a DEX called FooSwap with many t
39
39
- The user revisits the app from another channel on Farcaster (*"referrer"*)
40
40
- The user completes a swap transaction (*"conversion"*) emitting an onchain event
41
41
42
-
As you've seen in the above example, not everything you care about is onchain. In this example, two touchpoints contribute to the successful conversion: X and Farcaster. Using an [attribution model](/data/attribution#attribution-models), we can assign different weights to these touchpoints to determine their relative importance in the conversion:
42
+
As you've seen in the above example, not everything you care about is onchain. In this example, two touchpoints contribute to the successful conversion: X and Farcaster. Using an [attribution model](/data/attribution#attribution-models), we can determine which touchpoint to credit for the conversion:
43
43
44
-
- Using first touch model, the complete conversion can be attributed to X and the referral
45
-
- Using last touch model, the complete conversion can be attributed to Farcaster
46
-
- Using a linear attribution model, we could assign a weight of 0.5 to each touchpoint, meaning that both X and Farcaster contributed equally to the conversion
44
+
- Using the first-touch model, the complete conversion is attributed to X and the referral
45
+
- Using the last-touch model, the complete conversion is attributed to Farcaster
47
46
48
47
### How attribution works in Formo
49
48
@@ -105,13 +104,12 @@ Spend less time building analytics and leave the complex data engineering to us.
105
104
106
105
### Attribution models
107
106
108
-
Formo helps you understand the impact of each touchpoint in each user journey, whether with first or last touch (single-touch attribution) or across multiple touchpoints using multi-touch attribution.
107
+
Formo helps you understand the impact of touchpoints in each user journey using single-touch attribution, crediting either the first or the last touchpoint within the lookback window.
| User journey | Consists of touchpoints and the conversion event. It is possible for a conversion event to have no corresponding touchpoints (eg. utm parameters). In this case we consider it a 'direct' conversion |
123
-
| Conversion | The primary event you're interested in analyzing with multi-touch attribution models. Typically some final value generating interaction such as "Mint" or "Swap" or "Stake". |
121
+
| Conversion | The primary event you're interested in attributing. Typically a volume or revenue generating conversion event such as "Mint" or "Swap" or "Stake". |
124
122
| Touchpoint | Actions (events) a user's taken or exposed to along the journey before doing the conversion event. [Eg. does event A → B → C → D (conversion event) in a 7 day period; For a lookback window of 7 days, A, B, C are all considered touchpoints]|
125
123
| Lookback window | The time window where a user's events with this attribution property are counted towards the calculation. The window ends when the conversion metric happens. |
0 commit comments