← Research programCB06 · Ecosystem measurement

Cross-Channel Growth & Referrals

Study whether channel activity brings attributable visits and meaningful participation across the business and community ecosystem.

Creator program · BhavCzar website · Czulture / Clout

Planned — baseline collection not startedScope v1.0 · October 22, 2026

Download full project brief See the method

Business objective

What this study needs to answer.

Learn which documented referral paths support relevant business interest and real product participation, without inflating reach or assuming identity across platforms.

Which placements bring recorded visits and subsequent qualified actions?
Do attributable new participants return in a comparable observation window?
Where does the path break between a post, link, landing page and meaningful action?

Hypotheses · untested

Starting ideas, not conclusions.

A relevant destination and specific CTA may improve meaningful participation per attributable visit.
High total reach may not correspond to qualified business inquiries or active community participation.

Method and scope

Compare carefully. Record the exceptions.

Create one source/campaign/placement ID per link placement and keep a destination-event dictionary. Compare relevant CTA and landing-page variants within similar source/format/cohort; log concurrent changes. Use consent-compatible session or account identifiers only where actually available. Report link clicks, observed arrivals and recorded conversions separately; use a stated attribution window and do not infer individual journeys from aggregate platform traffic.

Included

Source-tagged links for approved channels and placements, landing-page visits and observable destination actions.
Qualified service inquiries, real account activation, first independent community participation and return when destination evidence is available.
Art acquisition cross-links without publishing unrelated identities or private customer data.

Outside the scope

Treating link clicks as confirmed visits or visits as referrals that converted.
Adding platform unique-viewer counts into a crossplatform unique-audience total.
Using synthetic demo traffic, staff tests or assisted votes as real independent activation.

Measures, denominators and observation windows

Observed arrival ratio: Source-tagged landing sessions / recorded outbound link-click events for the same placement and window, where both are available. This is a reconciliation indicator, not a unique-person conversion rate; blocked tracking and repeat sessions affect it.
Activation rate: Distinct eligible destination accounts completing the defined first meaningful action within 7 days / eligible new accounts created in the source-attributed cohort. Account creation alone is not participation.
Return rate: Activated accounts with another meaningful action on a different day within 7 days of activation / activated accounts with a complete 7-day follow-up. Keep incomplete cohorts pending.
Qualified referral rate: Distinct source-attributed qualified business inquiries / recorded source-tagged sessions, with a stated 30-day inquiry follow-up; same qualification rules as CB01.
Referral effort efficiency: Recorded eligible activations or qualified inquiries / hours spent on that referral placement, reported separately by action type rather than pooled into one success score.

Platform measures use matched 24-hour and seven-day snapshots where available. Report format, duration, snapshot age and missing fields. Zero denominators are undefined; inaccessible metrics are unavailable.

Baseline, costs and decision criteria

Baseline collection plan

Audit what destination events and exports actually exist before creating links. Collect a pre-pilot source snapshot if available. Confirm an exclusion flag for owner/self/demo activity, retain an unattributed bucket and document unavailable analytics. Do not assume the current site has complete referral-event instrumentation or cross-site consent/identity tracking.

Time, costs and revenue

Allocate source-asset production cost once; use placement IDs for distribution time and avoid charging the same shared asset in full to every channel. Record landing-page/measurement work, paid campaigns and processor/hosting fees separately from any attributed gross revenue or actual receipts.

Decisions after baseline

Set worthwhile activation or inquiry improvements after the baseline and tracking audit. Continue paths that yield recorded, relevant actions at an acceptable measured effort. Change the destination or CTA when observed visits do not progress. If arrivals or conversions cannot be linked, fix measurement or report only the observable stage; do not invent an end-to-end funnel.

Data access, confounders and limitations

Tracking loss, consent choice, link availability, self-reported attribution bias, repeated sessions, cross-device use, overlapping audiences, paid traffic, site outages, concurrent product changes and delayed conversions.

Use owner-accessible native reports and private operating records where available. No API credentials, monetization or complete tracking are assumed. Comparisons are observational unless a stronger design is actually established; crossposts are not independent evidence. Public reporting excludes private customer details.

Planned activity

Targets stay separate from actual output.

Measurement follows the approved channel targets: at least one daily video each on BhavCzar, Skits and Reacts; HeJustGotLucky target 12–24 daily. No additional publishing commitment. Streams exists (@BhavCzarStreams), but Streams, game and music studies remain backlog with no approved cadence.

Initial four-week pilot

October 26–November 22, 2026, with weekly reviews on November 2, 9, 16 and 23. Final seven-day content snapshots mature November 29; order and inquiry windows may close later.

Provisional 90-day horizon through January 23, 2027. Actual launch and baseline collection remain unconfirmed.

Planned outputs

Useful evidence. Documented decisions.

Source-link register, event dictionary and attribution-gap audit.
Cohort-based referral/activation/return report with separate unattributed and test traffic.
A destination/CTA recommendation linked to the underlying evidence.

Next milestone

Audit existing website/product events, define meaningful actions and test tagged links with clearly excluded self-test traffic before public launch.

The shared protocol defines source records, consistent windows, private-data boundaries and weekly continue/change/pause reviews.

Read the shared protocol →

Results · not collected

No findings to report yet.

This page is a project scope, not a completed case study. Future results will be added only with dated evidence, denominators, observation windows and limitations.

All seven studies Existing portfolio