Tracking & conversions
Pixel and Conversions API events, duplicate reporting and whether campaign goals match the actions that matter to your business.
You receive: Tracking findings and proposed corrections.
Meta Growth OS
Identify tracking issues, uncover performance gaps and prioritise improvements. Recurring checks flag changes that need your attention.
See what Meta Growth OS checks, automates and delivers.
Inside the PDF overview
Meta Growth OS
Check tracking
Find missing events, duplicate reporting and tracking gaps.
Identify performance gaps
See where ads, campaigns or the customer journey need attention.
Prioritise improvements
Get recommendations on what to fix, test or investigate next.
Monitor changes
Flag new issues and changes in performance through recurring checks.
Each stage builds on the evidence collected before it. Proposed changes come to you for approval.
Confirm your goals, customer journey and what a useful result is worth.
Identify the accounts, exports and records available for the review.
Check whether the agreed conversion actions are recorded correctly and flag gaps or duplicates.
Review tracking, creative, campaign structure, audiences, reporting and customer outcomes.
Connect related findings, investigate likely causes and identify what still needs evidence.
Decide what to fix, test, investigate or leave unchanged.
Draft recommendations, creative briefs and tracking specifications for approval.
Once approved changes are live, check that each one took effect, then record a baseline and an indicator to watch.
Repeat agreed checks, compare with the baseline and earlier results, and update the work plan.
Checks repeat on an agreed schedule. Business context is revisited when it changes.
Each area examines a different part of performance. The findings are reviewed together before changes are recommended.
Pixel and Conversions API events, duplicate reporting and whether campaign goals match the actions that matter to your business.
You receive: Tracking findings and proposed corrections.
How ads attract attention, generate responses and change over time, with possible fatigue investigated in context.
You receive: Ads to investigate, refresh or test, with draft briefs where needed.
Campaign organisation, delivery, learning status and how budget is distributed.
You receive: Structure and budget recommendations, with risks explained.
Audience settings, exclusions, saturation and potential overlap where the available data supports assessment.
You receive: Audience findings and proposed tests.
Whether reporting uses suitable metrics, comparable periods and consistent attribution settings.
You receive: Reporting gaps and a clearer basis for comparison.
What happens after an enquiry or purchase, using available CRM, store or exported records.
You receive: Funnel drop-offs and customer outcomes linked to campaigns where the records allow it.
Meta Growth OS is one system made of the components below. They run as part of the stages above, and if one is unavailable its stage runs at reduced depth and the report says so.
| Component | What it does | Needs |
|---|---|---|
| Coordinator | Runs the stages in order, keeps each stage’s record and stops for approval before anything changes. | All components below |
| Setup and readiness | Checks which connections are available, what each one allows and what is blocked without it. | Meta Ads access or exports; Google Drive |
| Account record | Keeps your business context, findings and decisions so a later review starts from what is known. | Google Drive |
| Benchmarks and targets | Works out targets from your own economics; published medians are shown with their source and confidence. | Your deal value or order value and margin |
| Account review | Runs the review phase by phase and pauses if tracking problems would make results unreliable. | Meta Ads access or exports |
| Tracking and conversions | Pixel, Conversions API, event deduplication, event match quality, attribution settings and optimisation events. | Meta Ads access; Events Manager for some checks |
| Creative | Attention and hold rates, results by ad, possible fatigue over time and creative briefs. | Ad-level data |
| Campaign structure and budgets | Campaign and ad set structure, learning status, budget split and pacing, and testing structure. | Campaign and ad set data |
| Audiences and delivery | Saturation and frequency, overlap between ad sets, placements, exclusions and targeting approach. | Ad set data; audience tools in Ads Manager for overlap |
| Customer journey | Landing pages, forms or checkout, and what happens after the click. | CRM, store or exported records |
| Reporting columns | Column presets and custom metrics in Ads Manager, checked against the live account. | Meta Ads access |
| Change monitoring | A check that each approved change took effect, a baseline once it has, then comparisons that flag faults straight away and hold back performance calls until there is enough data. | Earlier results from the account record |
| Reports | Founder, client or internal summaries and a dashboard, drawn only from the recorded findings. | The recorded findings |
Your goals and customer journey determine which results matter.
Follow enquiries through qualification, bookings and customers, using your own funnel stages.
Example: EnquiryQualified leadAppointmentCustomer
Output: Where your records allow it, understand which campaigns produce useful enquiries and where prospects drop off.
Review purchases alongside available revenue, margin, refunds and repeat-customer data.
Example: VisitPurchaseFulfilmentRepeat purchase
Output: Where your records allow it, understand campaign performance beyond the purchase count.
Your business context, findings and decisions are kept in an account record for future reviews.
Findings, priorities and a clear plan for what comes next. Depending on the agreed scope, your outputs can include:
Checks and findings
A record of the checks completed, findings and anything that could not be verified.
Issues to address
Affected campaigns, ad sets and ads, likely causes and the evidence behind each issue.
Priorities
Recommendations to act on, test or leave unchanged.
Work plan
Actions organised into now, next and later, with dependencies and potential disruption noted.
Creative briefs
Instructions an editor can work from: the hook, structure, timings and claims to verify.
Tracking specifications
Event and Conversions API changes written for your developer to review and test.
Change record
A dated record of approved changes, how each was verified, their baselines and unresolved issues.
Progress summary
Completed work, outstanding issues and decisions that need your input.
Connected account access or suitable exports, depending on the checks.
Your goals, customer journey and what a useful result is worth.
CRM or store data adds evidence about lead quality, sales and customer value.
Setup confirms the required tools, access and record storage, including the Google Drive folder that keeps the account record between reviews. Export-based reviews clearly identify checks that could not be verified.
Explore the questions Meta Growth OS can help you investigate.
I’ll confirm which accounts, tools and earlier results are needed during setup.
The review connects findings across tracking, creative, structure, audiences and reporting, then ranks them by likely impact, effort and the strength of the evidence. Your goals and what a useful result is worth decide what matters most.
The pixel, Conversions API and agreed conversion actions are checked for gaps and duplicates. Some checks need Events Manager access; anything that cannot be tested is reported as unverified.
Possible causes such as creative fatigue, learning resets, audience saturation, budget changes and tracking changes are investigated against the account’s history. The answer may be one cause, several, or that more data is needed first.
Campaigns are compared using outcomes from your CRM, store or exported records, not only the results Meta reports. Without those records, this question cannot be answered with confidence.
Results are compared week by week for each ad and against similar ads, to separate possible creative fatigue from audience or delivery changes.
The account is compared with its baseline. Faults such as delivery errors or tracking that stopped are flagged straight away; a drop in performance is called a problem only once learning status and sample size allow it.
Recommendations show what was observed, where it came from and what remains uncertain.
Tracking problems are identified before affected results are used to judge performance.
Your goals, funnel and definition of a useful result guide the review.
Performance recommendations account for learning status and sample size. Tracking faults and delivery problems are flagged when observed.
Proposed changes need your approval. Once live, each one is checked against its expected result, then recorded with a baseline and an indicator to watch.
Where the account supports it, new campaigns and ad sets are prepared paused, so nothing runs until you approve it.
See the checks, workflow and outputs in a five-page PDF overview.
Tell me what you’d like to automate. I’ll help you work out the checks, data and setup your account needs.
Need help with setup?Get the five-page PDF overview of Meta Growth OS, including the checks, automation and what you receive.
The PDF overview is on its way to . It arrives as a PDF attachment, so give it a moment. If it has not landed in a few minutes, check spam or tell me.