An Experiment Ledger for ASA, Creators, and Community Partnerships

Signals to watch

• One app explicitly considers reducing ad-network spend while evaluating ASA, creators, or community partnerships
• The experiment needs channel hypotheses, an incrementality method, and seasonal counterevidence
• A broader channel shift would require independent projects with budget movement or test results

A market lead at a Mobile apps & gaming growth provider should not place one app’s consideration of lower ad-network spend and tests of ASA, creators, and community partnerships under “new market trend.” UA means user acquisition. ASA means Apple Search Ads, the search-ad product in Apple’s app marketplace. While a project is still discussing budget direction, it needs an experiment ledger—not a budget sheet that assumes reallocation has happened.

Record hypotheses before recording winners

Give each channel its own ledger page and keep the questions specific to this project:

• Traditional ad networks: Why is the team considering a reduction, and could it be limited to the current campaign?
• ASA: Under which market and app-type conditions would the project evaluate it?
• Creators: How would visits or conversions from a partnership be distinguished from other channels?
• Community partnerships: Which part of the user journey might be affected, and who would operate the test?

The available discussion provides no budget amount, reallocation share, or test result. Those fields stay open. “Considering a reduction” is not a completed reduction, and “evaluating new channels” is not budget approval.

Make incrementality answer “what happens without it?”

Incrementality is the additional outcome attributable to a channel that would not have occurred without it. Teams may use different validation methods, but the ledger must identify the comparison, observation conditions, and decision owner. Without them, incrementality is a research question rather than a result.

Seasonal campaign activity is active counterevidence. A temporary creator or community test may not persist into the next budget decision. The ledger should retain the before-and-after project state rather than only the moment when a channel was mentioned. It must also distinguish expansion, a test, and reallocation: a limited experiment does not prove that an incumbent channel will exit.

Turn discussion into material a budget owner can review

Within authorized Telegram groups that a user intentionally connects, TOP Prospect can deduplicate same-source forwards, retain the original message, source, time, app type, market, and campaign context, and surface a candidate Signal (an item awaiting human review) with a priority. It does not verify a budget shift, evaluate channel performance, or contact the poster automatically. The user checks the claim with the budget owner and adds experiment material before making a judgement.

If the poster’s role is unclear, the ledger cannot assume budget authority. Repeated opinions without test activity remain in research. A defined experiment shows that one project has entered evaluation; it still provides no winning channel.

Require another independent project before comparing a channel shift

One app’s ledger answers whether that project is ready to test. Another independent app needs its own market, app type, budget action, and incrementality question before the records are comparable. The projects may choose different channel mixes, and that variation is more useful than forcing both into a broad trend.

The market lead can summarize independent experiments before the next budget decision, but the conclusion should state which conditions recur and which may still be seasonal. Only actual budget movement or reviewable test results in independent projects justify raising the trend priority. Otherwise, the item remains one app’s channel experiment.

PRODUCT SCOPE

Market and risk discussion is supporting evidence

Top Prospect is primarily a Telegram lead-generation product. Market and risk discussion can add context to a candidate lead, but it does not become a verified incident, trend, or sales opportunity automatically.

Review the product workflow and boundaries →