Case Study · Client Project · Ad Analytics & AI Advisory

SalamaSons — Ad Intelligence & AI Recommendation Loop

A home-appliances retailer in Mauritania was spending on social ads and reading the results by scrolling. I built the measurement loop: automated collection of post and ad performance into a warehouse sheet every four hours, and an AI layer that reads it and sends a recommendation per ad straight to the owner's Telegram.

Ads without measurement is spending. Measurement without a recommendation is reporting. This closes the loop from spend → data → decision.
Ad Analyticsn8nMeta Graph API Google SheetsOpenAITelegram
case scorecard — structural factsrunning
4h
refresh cycle — data updated six times a day
2
chained workflows — collection, then advisory
1
recommendation per ad, delivered to Telegram
0
manual steps between spend and advice

Client confidentiality: no spend figures, revenue, or account identifiers appear in this case study. The build is the story.

01The Business Problem

A single-owner retail operation running paid social in a market where every ad decision is made by feel: open the ads manager, scroll the posts, remember roughly which one "did well last week," and adjust. The performance data existed — it was just locked inside platform screens, unaggregated, never compared, and never written down. So nothing accumulated: last month's lesson was gone by this month.

The owner didn't need another dashboard to log into. He needed the answer to arrive where he already was — and to say what to do, not just what happened.

02My Role

Built and deployed independently: the data-collection workflows against the social platform, the sheet schema that acts as the warehouse, the scheduling and chaining, the prompt design for the advisory layer, and the Telegram delivery. Design, build, and ongoing operation.

03The Loop

Published posts & live ads
social platform
Workflow 1 — Collection
every 4 hours · impressions + full ad detail
Google Sheets warehouse
append + update · one row per post / per ad
Workflow 2 — Advisory
reads the sheet · OpenAI · per-ad recommendation
Owner's Telegram
one message, per ad, ready to act on
SCREENSHOT SLOT
the two chained workflows on the n8n canvas
(blur credentials & account IDs)assets/salamasons-workflows.png

04What I Built

Post-performance collection

A scheduled workflow pulls the published posts and their impressions, writing each into a Google Sheet — so reach stops being a number you glance at and becomes a series you can compare across weeks.

Full ad-detail extraction

The same pass collects the complete detail behind every running ad and lands it in the sheet alongside performance — creative, targeting and delivery attributes sitting in the same row as the result they produced.

A four-hour heartbeat

The cycle runs every four hours rather than daily: fast enough to catch an ad going wrong the same day it does, slow enough that the numbers have settled and the owner isn't buried in noise.

Chained AI advisory

A second workflow fires after collection completes, reads the accumulated data, and passes it to OpenAI for a per-ad recommendation — then delivers it to the owner's Telegram. The advice arrives in the app he already checks, not in a dashboard he has to remember to open.

05Engineering Decisions

The sheet is the warehouse, deliberately: the client reads and edits spreadsheets fluently and reads nothing else. Putting the data where he can audit it himself made the AI layer trustworthy instead of magical — he can always check the row the recommendation came from.
Collection and advice are separate workflows: chained, not merged. If the platform API misbehaves, collection fails alone and the alert is specific; the advisory layer simply doesn't run on stale data rather than confidently advising on it.
Per-ad granularity, not a summary: a weekly digest averages away the one ad that's burning budget. One recommendation per ad keeps the unit of decision the same as the unit of spend.
Delivery beats dashboards: for a single-owner operation, a Telegram message that arrives is worth more than a perfect dashboard that goes unopened. The interface is the messaging app he was already in.
Accumulating history: because every cycle appends, the sheet became a growing performance record — the thing the operation never had, and the reason each month can now be compared to the last.

06How This Differs From the Al-Raky Build

Both are commerce automation, but they solve opposite halves of the same business. Al-Raky is a pre-sale production system: it takes a photo and a price and manufactures everything needed to sell — content, media, listings, sales agents. SalamaSons is a post-publication measurement system: it takes what's already running and turns its results into advice. One creates the ads; this one judges them.

Different category (home appliances vs cosmetics), different market (Mauritania vs Egypt), different problem (production vs measurement) — built as two projects, not one product deployed twice.

07Skills Demonstrated

Marketing analyticsAPI data extraction Scheduled pipelinesWorkflow chaining Prompt engineeringLLM-assisted analysis Sheets as a data layerAlert & delivery design