Reporting during your pilot

By default, pilot results come from your ad platforms (Google Ads, Search Ads 360 or Meta) together with Scowtt's own reporting. If your primary KPI lives in your own systems, such as your CRM, a BI tool or internal finance data, we can use your reporting too, as long as it's set up before launch.

Default: ad platform and Scowtt reporting

Consistent and timely. Both teams can see the same numbers without manual handoffs.
No reconciliation between systems. One shared source avoids disputes over whose numbers are right.
Detailed enough to run the pilot. It supports the campaign-level and day-level analysis needed while the pilot is running.

Also supported: your own reporting

We can build your reporting into the pilot when:

Requirement	Why
It's agreed before launch. Format, fields and definitions are set at kickoff, not at the readout	So both teams read results the same way
It arrives daily. For example an automated export, a shared sheet, a data share or a CRM connection	So we can monitor the pilot, catch issues early and optimize while it runs, not just evaluate at the end
It can be tied to campaigns. Each record carries a link back to its campaign or test arm, such as a click ID, UTM or campaign ID	So Scowtt and BAU results can be separated
Its definitions match the agreed KPIs. Stage definitions in your report match the ones in your success criteria	So the readout answers the question you agreed on

Steps

You and Scowtt: Choose the source of truth

At kickoff, agree whether results are read from ad platform and Scowtt reporting, or from your own reporting as well.
You: Share your report format

If you're using your own reporting, share its format, fields, definitions and attribution model before launch.
You: Set up a daily feed

Set up a daily export, shared sheet, data share or CRM connection, with a campaign link on every record.
Scowtt: Monitor and report

Scowtt monitors the pilot daily, flags anything unusual, and reads results with you at each check-in.