Meta Ad Spend & Alan Reconciliation

Billing period May 2026 · 6 Meta invoices dated 02-Jun-2026 · all billed to Studio 1 (539 W Commerce St, Dallas) · NET 30

1 · How the 6 bills join up

The 6 invoices are 6 separate Meta ad accounts, but they collapse into 3 campaign families. Every family runs on a primary account plus a smaller secondary ("spillover / backup") account — this is why one month of Alan ads produces six bills instead of three. Add both accounts in a family to get that family's true spend.

2 · Where the money went — spend, leads & cost per lead by city

Same spend, re-cut by city (from the campaign-code prefix) and split Facebook vs Instagram, then set against the fresh leads each city delivered (CRM, non-recycled) to give a real cost per lead. Orlando is kept separate (Meta bills it separately). The "Women" campaign is spread across its city ad sets — see the split below — so every dollar now sits under a city.

3 · Does it line up with Alan's leads?

For each Meta campaign code: the actual Meta charge (what Studio 1 pays Meta) next to the leads it actually delivered — counted from the CRM, where every lead is tagged with an ad-level code (e.g. ORL4IG31F, ORL4IG32M) that rolls up under the Meta campaign code by prefix. Fresh = new leads (excludes recycled …R re-works, which this spend didn't generate). Real CPL = Meta $ ÷ fresh leads — the true cost per lead. Orlando is counted separately (Meta bills it separately), and the "Women" spend now sits inside the city FB3 codes.

4 · What still needs a note

• "Women" campaign is now split by city. Meta bills it as one $5,767.95 line, but it's one ad set per city (NY / Nashville / Chicago / Dallas / Boston / Florida). We spread its spend across those cities by each ad set's reported spend (§2 table), so it's no longer an orphan line and its leads (already tagged with city codes) line up.
• Recycled leads are excluded from CPL. 1,180 leads on these codes carry the …R (re-work) suffix — they weren't generated by this fresh ad spend, so counting them would understate the true cost per lead.
• Alan's cost sheet folds Orlando into Florida. His weekly sheet has only FL4IG3 / FLFB3 — no Orlando row — even though Meta bills ORL4IG3 / ORLFB3 separately ($23,848.55 combined). This report reads leads from the CRM instead, so Orlando is counted correctly here.
• These 6 invoices aren't all of Alan. Alan's May sheet also spends $75,606.89 across 13 campaigns (mostly *3CX / *4AB, 4,725 leads) that appear on none of these 6 invoices — they run on other ad accounts not in this ZIP. Get those invoices to see total Alan Meta spend.
• Timing. Meta bills the calendar month (1–31 May); CRM lead dates are the same window, so the match is clean — but Alan's own weekly sheet runs Friday–Thursday, so his numbers won't tie to the day.

5 · Alan campaigns NOT on these 6 invoices

These have leads & spend in Alan's May cost sheet but no line on any of the 6 Meta invoices above — they run on other ad accounts. Get those invoices to close the loop on total Alan spend.