PUBLIC REPORT · PRODUCT ACTIVITY
Local business product trends: an evidence gap and reporting framework.
This is a transparent report framework, not a market-size study or a set of performance findings. It describes what DaGiftFoundation product activity could support once records, coverage, and privacy checks are validated.
Evidence gap · no trend figures published
No privacy-reviewed period extract accompanies this report.
The current schema defines first-party product events, but the event taxonomy is not a verified completeness audit. No counts or rates are shown until a complete period extract is reconciled to those sources and passes the cohort rules below.
SOURCE COVERAGE
What the current product events cover
The first-party FunnelEvent taxonomy covers these DaGiftFoundation product interactions:
- Template views — template_viewed
- Authentication starts and workspace generation — auth_initiated, workspace_generated
- First actions and teammate invitations — first_action_created, teammate_invited
- Paywall and subscription activity — paywall_hit, subscription_started
- AI add-on activity — ai_addon_considered, ai_addon_generation_requested, ai_addon_generation_completed, ai_addon_checkout_started, ai_addon_subscription_verified
This is product-use evidence, not a representative sample of local businesses. It cannot establish how the local-business market performs or how merchants’ revenue, conversion, customer retention, or gift sales change. Static template copy is not usage data. A PostHog HTTP-accepted receipt confirms transport acceptance only; it does not prove that an event was captured or qualify it for this report.
LABELED REPORT FRAMEWORK
Questions, definitions, and evidence still needed
The proposed starting method is one rolling 90-day window, fixed before extraction. Each future metric must state its period, cohort, meaning, calculation, source-event coverage, update date, and exclusions next to the result.
| Question | Proposed measure and source coverage |
|---|---|
| Do template visitors create a planning workspace? | For the proposed rolling 90-day event window, numerator = distinct participant identities with both template_viewed and workspace_generated; denominator = distinct eligible identities with template_viewed. Join by validated visitor/account identity and report unlinked-view coverage separately. FunnelEvent records template_viewed, auth_initiated, and workspace_generated. A complete event extract and identity-linkage coverage check are still required. |
| How often does a new workspace reach a first action? | For workspaces generated in the window, numerator = distinct identities with first_action_created in the same window; denominator = distinct identities with workspace_generated. If timing is reported later, summarize non-null time_since_signup values only and state their sample coverage. FunnelEvent records first_action_created and time_since_signup. No rate or timing summary is published without a validated period extract. |
| What collaboration activity is visible? | For workspaces generated in the window, numerator = distinct identities with at least one teammate_invited event; denominator = distinct identities with workspace_generated. Count each identity once and do not interpret an invitation as acceptance, retention, or business impact. FunnelEvent records teammate_invited. Invitation acceptance and downstream team outcomes are not part of this report’s event taxonomy. |
| What do gift-pass and wallet trends show? | No calculation is defined until gift-pass checkout, issuance, delivery, and redemption exist and generate verified first-party records. No gift-pass, Apple/Google Wallet, or redemption event appears in the current product event taxonomy or customer commerce flow. |
| Do review cycles or enterprise deployments change local-business outcomes? | This requires new event definitions plus permissioned merchant-side outcome data. Product activity alone cannot establish revenue, conversion, or retention effects. Review-cycle completion and enterprise website deployment events are not in the current FunnelEvent taxonomy; merchant outcome data is not a source here. |
PRIVACY AND PUBLICATION RULES
Small groups and identifying detail stay out of public results.
- Publish aggregate counts or rates only after source reconciliation and a minimum of 10 distinct participants in every reported cell.
- Suppress below-threshold groups, complementary totals, and another cohort when a total could reveal the withheld value by subtraction.
- Do not expose names, contact details, business or account identifiers, visitor IDs, raw event rows, or public filters that let readers combine small cohorts.
- Keep data definitions and exclusions attached to each metric. Do not use product engagement as evidence of merchant outcomes.
Known exclusions for this framework: no gift-pass checkout, wallet delivery, or redemption activity; no review-cycle completion or enterprise deployment events in the current event taxonomy; no market-wide comparison source; no verified merchant revenue or conversion outcome source; and no completeness-checked reporting-period extract.
INTERPRETATION
Product activity is not a merchant result.
A template view or workspace event can describe interaction with DaGiftFoundation. It does not show that a local business won customers, increased revenue, improved conversion, or sold or redeemed a gift card. Those claims require separate, permissioned merchant records and a validated analysis. This page will remain an evidence-gap report until those checks support a privacy-safe publication.
Return to DaGiftFoundation