Module 3 - Turn ad analytics into an automated workflow

Module contents

• What you will create
• Before you start
• The big picture
• Step 1: Ask Life OS where this belongs
• Step 2: Set up the decision framework
• Step 3: Download your VSL Meta ads exports
• Step 4: Create a simple per-ad report
• Step 5: Run future reports
• Later: Automate CSV exports
• Module 3 win

What you will create

By the end of this module, you will have created an automated ad analytics workflow Life OS can help run.

The example is VSL (Video Sales Letter) funnel Meta ad review: should this ad stay, stop, scale, or be checked?

Core idea:

Your best thinking can become a repeatable workflow.

Before you start

You need a VSL Meta ads account or recent Meta ads exports you can use for practice.

You do not need perfect data. You only need enough information for Life OS to learn the shape of the review workflow.

The big picture

One ad decision can be made manually. A repeated ad review needs a clear workflow.

This module turns your review criteria into something Life OS can help run again.

Campaigns spend money. Ads need regular review. The question is not:

Am I good at ads?

The better question is:

Do I have a clear decision process?

For this module, the decision question is:

Should this ad stay, stop, scale, or be checked?

The verdicts are:

This workflow protects you from making emotional or inconsistent ad decisions.

Important:

• A Stay ad is not always a good ad. Sometimes it stays because there is not enough data yet.
• Scale should be treated carefully. A tiny amount of data is not enough to make a confident scaling decision.
• The AI report should show enough logic that you can see how it reached the verdict.
• If you walked the ad through the flow yourself, you should arrive at the same answer.

Step 1: Ask Life OS where this belongs

VSL funnel Meta ad analytics might be a Project, an Area, or something else in your Life OS.

This matters because you may have other ad analytics later. This workflow is specifically for VSL funnel ads.

Ask Life OS to recommend the home, then check the recommendation before approving it.

A training reminder: If something unexpected happens, treat it as a training moment. You can pause and correct Life OS at any time. See the If your Life OS goes off track section near the start of this manual for the reset prompt.

Copy this prompt and paste it into your AI tool:

I want Life OS to help me make better decisions about my VSL Meta ads without me starting from scratch each time.

Please look at my Life OS and recommend the simplest home for this ongoing ad review work.

I want this area to help me keep the decision rules, ad exports, and simple reports in one useful place.

Before you create anything, tell me:
- Where you think this belongs
- What you would call it
- What small folder or file structure you recommend
- Why this setup will make future ad reviews easier

Keep it simple and wait for my approval.

Check the recommendation.

If Life OS suggests an Area and that feels right, say:

Yes, that makes sense. This is ongoing business care, not a one-off project. Please create the simple Area you recommended.

If Life OS suggests a Project but you think it should be an Area, say:

I think this belongs in Areas because it is something I will review regularly, not something with a finish line.

Please revise your recommendation with that in mind and explain the simpler Area setup you would use.

A simple structure is enough. Life OS may suggest names and homes for:

• An overview.
• A log.
• The decision framework document.
• Source material.
• Ad exports.
• Reports.

Do not overbuild it. This part of the Life OS only needs somewhere to keep the source criteria, the documented rules, the data exports, and the reports.

Step 2: Set up the decision framework

Add the decision framework to the place Life OS created.

Your trainer will provide the decision criteria for this workflow as a PDF.

Get the PDF here: Google Drive - Decision Criteria

Save the PDF into your Life OS’s Inbox (00 Inbox), then use this prompt:

I have a PDF with the decision rules for reviewing my VSL Meta ads.

[give the PDF file path here]

Please turn it into a practical decision guide Life OS can use whenever I need to review ads.

The outcome I want is simple: for each ad, Life OS should be able to recommend Stay, Stop, Scale, or Check and explain why in plain English.

Before writing anything, show me the decision logic you understood, where you would save it, and why it belongs there.

Wait for my approval before creating or editing files.

Check the extracted framework before approving it.

You are asking Life OS to understand your business judgment and make it reusable.

Step 3: Download your VSL Meta ads exports

Manual exports are the first path.

In Meta Ads Manager:

• Go to Ads Manager.
• Choose the campaign you want to review.
• Set the date range.
• Export the CSV files you need for review.
• Save the CSV exports into Inbox first.
• Ask Life OS to move them into the right place and name them clearly for future exports.

Inbox is the best place for loose exports while Life OS learns where they belong.

Use this prompt:

I put my latest Meta ads CSV exports in Inbox.

Please help me turn these loose exports into useful Life OS context for my VSL Meta Ad Analytics.

Find the relevant files, ignore anything unrelated, suggest clear names, and recommend where they should live so future reports are easy to run.

Before moving or renaming anything, show me what you found, what you recommend, and why.

Wait for my approval before changing files.

Step 4: Create a simple per-ad report

Use this prompt to generate a per-ad report from your decision framework and CSV exports:

Please use my VSL Meta Ad Analytics setup to tell me what to do with each ad.

Use the decision framework and the relevant Meta ads exports already saved in Life OS.

For each ad, give me a clear Stay, Stop, Scale, or Check recommendation, the reason, and what I should watch next.

Make the report simple enough that I can act on it without being an ads expert.

Before creating the report, tell me where you will save it and why that is the right place.

Wait for my approval before creating or editing files.

When you read the report, check:

• Can I see why each verdict was chosen?
• Does the report show the step that triggered the verdict?
• Is anything marked Check because the data is missing or unclear?
• Would I reach the same answer if I walked through the framework myself?

Step 5: Run future reports

You have now walked through the workflow once: create the home, document the framework, place the exports, run the report.

Next time you have fresh CSV exports, save them in Inbox and use this prompt:

I have new Meta ads exports in Inbox and want an updated VSL Meta Ad Analytics report.

Please use the workflow we already set up.

First, sort out the new exports: tell me which files are relevant, where they should go, and whether anything looks duplicated or unclear.

After I approve that, create a fresh plain-English report that tells me which ads should Stay, Stop, Scale, or be Checked, and why.

Wait for my approval before creating or editing files.

The framework and home already exist. You are only placing new data and generating a new report.

Later: Automate CSV exports

In the current workflow, you manually export CSV files from Meta Ads Manager and place them in Inbox.

That is enough while you are learning.

If you want to experiment later, you can automate the export process.

To do that, you would connect Life OS to Meta Ads Manager using a Meta Ads MCP, such as pipeboard-co/meta-ads-mcp, similar to how you connected Gmail and Google Calendar earlier.

Once the MCP is connected and authenticated correctly, you can ask Life OS to extract the Meta ads exports automatically for you.

That setup is not in scope for this module. It is something to experiment with later if this workflow becomes useful enough to repeat.

Module 3 win

Ask Life OS:

Based on what you now understand about my Life OS, where else am I making repeated decisions that could become a simple workflow?