Launch campaigns that are tagged correctly, tracked properly and ready to convert.
Before you spend, Advertising Intelligence checks the landing page, the UTM structure and the conversion event. After launch, it reads results from your own tracking.
Campaign Signal Flow
- Flow
- Broken / missing
| Entity | Type | Related to | Relationship |
|---|---|---|---|
| Spring Sale campaign | Campaign | utm_source=spring/paid | Flow |
| utm_source=spring/paid | URL | Landing: /spring-sale | Flow |
| Landing: /spring-sale | Page | purchase event | Flow |
| purchase event | Engagement / event | Conversion recorded | Flow |
| purchase event | Engagement / event | Missing: thank-you event | Broken / missing |
Scope, stated plainly. Results come from your first-party tracking (UTM-tagged visits and conversions). The platform does not import spend or impressions from ad platforms, so cost metrics are not computed automatically. The free ROAS and CAC calculators take your own inputs.
Most campaign waste is set up before the first click.
A campaign that lands on a slow page, uses inconsistent UTMs, or points at a conversion that never fires cannot be judged fairly.
Naming drift is the quiet one: “Facebook”, “facebook” and “fb” become three sources in every report.
Broken pages and events
A missing conversion event turns a good campaign into an apparent failure.
Inconsistent naming
Collisions fragment reports and make channels incomparable.
Judging too early
Without a baseline and a sample-size rule, small changes get called wins.
From pre-flight check to measured result.
Run a readiness check
The landing page is analysed against a rule set and scored.
Generate compliant UTMs
Build URLs from your governance taxonomy instead of typing them.
Validate the conversion event
The Conversion Debugger checks that the event fires as defined.
Track results
Visits, conversions and journeys are read from your own tracking.
Measure the change
Baselines let later changes be compared conservatively.
Signals it reads
- Landing-page rules and validators
- Page content and CTA clarity
- UTM policies and allowed values
- Spelling collisions and missing parameters
- Event firing and definition validation
- Conversions per campaign
Intelligence you can act on, with the evidence attached.
Intelligence produced
- A readiness score with failed and passed checks
- Governance findings on your UTM taxonomy
- Conversion debugger results per definition
- Campaign views built from tracked visits and conversions
Recommended actions
- Fix failed checks before launch
- Standardise the source names flagged as collisions
- Repair the conversion event, then re-run the check
- Share a readiness report with a client or teammate
What changes for the team.
Cleaner reporting
One name per source means channels compare like for like.
Fewer wasted launches
Pre-flight catches the failures that invalidate results.
Trustworthy conversion counts
Definitions are validated, not assumed.
Shareable proof
Readiness reports can be shared by link.
Who reaches for it, and why.
Performance marketers
Gate every launch behind a readiness check.
Agencies
Enforce one UTM standard across client accounts.
Ecommerce teams
Confirm the purchase event fires before a sale starts.
Related capabilities, tools and reading.
Questions people ask first.
Does it connect to Google Ads or Meta?
No ad-platform import is included. Results come from your own UTM-tagged tracking.
What does the readiness check look at?
Landing page loading and content rules, UTM validity and conversion setup, scored against a rule set.
Can I share a readiness result?
Yes. Results can be shared by link.
See what is moving your numbers.
Install one tracking snippet and start reading your own data. Or ask for a walkthrough first.