Channel efficiency / SELF-GUIDED

Investigate a weak channel

Trace weak returns through reporting, creative renewal, delivery and cohort economics.

Start the first check Discuss a difficult question

Use a non-sensitive summary. Notes stay in this tab; Save keeps a temporary copy for reloads in this tab. Nothing is sent until you confirm a consultation request.

Your question

What do you want to understand?Which result matters?

CHECK 1 / 3

Define weak performance precisely

Choose the business metric, target, completed cohort age and period. Separate a persistent problem from a recent change.

Check your interpretation. Forecast revenue, immature outcomes and attributed ROAS answer different questions.

What is weak, relative to which target and horizon?Where are you with this check?

If you cannot resolve this check

Reconcile measurement if the apparent weakness depends on which report you open.

CHECK 2 / 3

Trace the system of attempts

Compare creative search, setup, delivery, scaling and stops. Group attempts by launch period and comparable conditions.

Check your interpretation. A low aggregate may contain different mechanisms; frequent creative renewal changes the baseline.

Where are capital and time being spent without a useful next result?Where are you with this check?

If you cannot resolve this check

If attempt history is missing, build that registry before declaring a part of the system broken.

CHECK 3 / 3

Select one next check

Choose the smallest change or comparison that separates two explanations. Define the result to protect and a checkpoint.

Check your interpretation. A weak reported average alone does not identify removable spend or prove that a cut improves profit.

What will you test, protect and revisit?Where are you with this check?

If you cannot resolve this check

Discuss the case when effects span multiple branches or a proposed change risks successful combinations.

What would help you move forward?

You can continue with partial observations. Recording a check does not verify its conclusion.

Work with your data

Carry your question and observations into Project Studio. Refine the scope, then use Builder and CSV Analyzer. Sign-in is required.

Keep the next check

Save your observations here or download them for your own work. No CSV rows are attached.

A QUESTION WORTH DISCUSSING

Bring the part you could not resolve.

Describe the difficult part in your notes above. You can ask for a review before finishing every check.

The next page lets you review a free first-consultation request. After sign-in, your notes fill the request; you can edit them before sending. Scope and timing are agreed after review.