dateReporting date in YYYY-MM-DD format
Check a compatible campaign CSV for missing values, invalid numbers, impossible relationships, duplicate reporting keys, and period warnings—then recalculate CTR, CPC, CVR, and CPA from totals.
This public page is a product guide, not an uploader. No visitor CSV is accepted or stored here.
One documented schema. One local review checkpoint.
RoutineCut validates one explicit CSV shape. Prepare the file before import instead of asking the checker to guess what each vendor column means.
date,client,channel,campaign,spend,impressions,clicks,conversionsdateReporting date in YYYY-MM-DD format
clientClient or brand name
channelChannel such as Search, Social, or Content
campaignCampaign or reporting-group name
spendMedia spend in one consistent currency
impressionsImpression count
clicksClick count
conversionsConversion count using one approved definition
Rows with critical conditions are excluded from KPI totals. Warnings require human source review before local sign-off.
Attribution definitions can create legitimate exceptions. The checker surfaces the relationship; a human resolves the meaning.
total clicks ÷ total impressions × 100total spend ÷ total clickstotal conversions ÷ total clicks × 100total spend ÷ total conversionsThese formulas use reconciled totals. They do not average row-level percentages.
The paid kit arrives as a ZIP. Extract it and open index.html in a current Chrome or Edge browser.
Use UTF-8, the exact eight required columns, one currency, no more than 5,000 rows, and a file up to 5 MB.
Critical rows are excluded from totals. Warnings remain visible until a person compares them with the source.
Mark the local review complete only after source reconciliation. Nothing is sent to a client automatically.
No. This public guide accepts and stores no files. The paid RoutineCut download opens locally in your browser and processes a compatible CSV in browser memory.
No. Your CSV must already use the eight documented columns. Custom transformation, API connections, and arbitrary vendor schemas are outside the product scope.
The included rule treats that relationship as critical. View-through, offline, or multi-event attribution can make it legitimate, so reconcile the approved definition and source before using the file.
No. The validator checks its documented fields and relationships. A responsible operator still needs to verify KPI definitions, source totals, context, and final delivery.
Download the offline workspace, start with the included synthetic sample, and keep final source verification under human control.