Weekly CTV and In-App Campaign Review: A Practical Template

Before moving budget between CTV and in-app campaigns, check that you are comparing results on the same basis. A newer group of players may have had less time to purchase. Two reports may count revenue differently. Either can make one channel look stronger than it is.
Use this worksheet to decide what to keep, change or investigate at your next campaign review. It is written for mobile game and app acquisition teams using their existing reports. A weekly meeting does not mean every result will be ready within seven days.
Start with the decision you need to make
Choose one question: should we keep the current budget split, test different creative, or wait for more purchase data?
Then agree which result will guide that decision. A game with in-app purchases might look at the share of acquired players who purchase, revenue from those players and acquisition cost. Keep the number of paying players separate from the number of purchases: one player can buy several times.
Confirm what the campaign can use as a target and how media will be billed. Choosing purchases as your success measure does not settle either point.
Compare players over the same period
A cohort is a group of users with a shared starting point, such as their install date. Its revenue is different from all revenue received during a calendar week, which may include purchases by long-standing players. Singular's reporting distinguishes cohort results from its “Actual” view of events on the date they happened. Singular cohort documentation.
For each group, record the install dates, how long you will observe results and when you pulled the report. Check whether the tool counts calendar days or rolling hours, and whether a number is a running total or just one day's result. AppsFlyer's cohort dashboard includes controls for partial versus complete periods and cumulative versus single-period data. AppsFlyer cohort documentation.
Keep two timing settings separate. The attribution window determines which earlier ad interaction can receive credit. The revenue observation period determines how much spending after the install you include. A D7 revenue report does not mean the campaign has a seven-day attribution window. Our CTV-to-mobile attribution article explains the crediting question; use your provider's documentation to confirm the settings.
Copy the weekly review worksheet
Complete one record for each comparison. Only use breakdowns that your reports support. For example, Singular's CTV documentation says network-side data has no mobile OS information, and a report combining ad views and app installs cannot be split by platform. Do not create an iOS-versus-Android cost comparison when the source cannot support it. Singular CTV reporting limitations.
Decision and owner
The question to answer and the person making the decision
Campaigns being compared
App, market, campaign and OS where available; which results are acquisition, retargeting or organic
Users included
Who belongs in each group; which users form the base for each percentage
Dates and data readiness
Install dates, observation period, report date/timezone, incomplete periods and expected reporting delays
Report settings
Attribution method/window, cohort calculation, filters and running-total versus single-period values
Cost and revenue definitions
Spend source and inclusions, currency, purchase/ad revenue separately, gross/net revenue and refund treatment
Results
Spend, attributed installs, selected events and revenue; counts alongside percentages
Sources and gaps
Saved report/export, data owner, missing fields and differences still to explain
Other changes
Creative versions, product releases, promotions and tracking changes during the period
Next action
Keep/change/investigate, reason, what is still uncertain, owner and next review date; what would change the decision
Mark missing data as “unknown” or “incomplete.” A missing cost report is different from zero spend. Save the report and its settings so someone else can check the comparison.
Review each channel before combining the totals
Look at CTV and in-app separately first. Add a combined view only when you can explain which channels and organic results it includes, and how it handles overlapping users or events. Adding rows that credit the same purchase twice will inflate the total.
Keep acquisition and retargeting definitions visible. If two reports do not agree, assign someone to explain the difference before ranking channels against each other.
For cost per install (CPI), record which costs and attributed installs are included. For return on ad spend (ROAS), record the revenue and cost definitions. Purchase revenue, ad revenue and their combined total answer different questions. Singular lists these as distinct measures; check the definitions in each tool you use. Singular metric definitions.
Example: wait until both groups have enough time
Imagine a fictional game team meeting every Monday. It has chosen to review seven complete calendar days after the install date, excluding that date, then allow one more full day for reporting. This is an example rule, not a recommended window for every game.
At the November 16 meeting, its November 2 CTV group is ready. Its November 12 in-app group is not. For that newer group, the seven days run from November 13 to 19; November 20 is the reporting allowance. The team schedules the comparison for November 21.
It can investigate delivery or missing data now, but waits before declaring a channel winner. The record names who will check the report and what would justify changing the budget. This example contains no Edge226 or customer performance results.
Finish with an action and a review date
Look at the counts behind each percentage before acting. Agree what evidence your app's economics and test plan require; there is no universal ROAS threshold in this template.
Check what else changed. A promotion, onboarding update or new creative may affect the same period. Record creative versions and the question each tests; our CTV creative production checklist covers that preparation.
Your reports show which results were credited to advertising. Establishing how many extra purchases the advertising caused is a separate question, usually called incrementality. A higher attributed ROAS alone does not answer it. AppsFlyer on attribution and contribution.
End with the decision, any unanswered question, the owner and the next review date. That gives the next meeting a clear starting point.
Discuss your acquisition plan
Explore Edge226's CTV and in-app acquisition offerings. Contact the team with your app, target markets, campaign goal, measurement setup and an example report to discuss your plan.
