GO TO WAR
Military.com — Appendix D Audiences Signals
Source: appendix_d_audiences_signals.md

Appendix D — Audiences, Opportunity Score, Anomalies, Auction Benchmarks

Live API pull, June 4, 2026.

Custom Audiences inventory (38 total)

Active audiences (10)

# Name Subtype Size Status Created Notes
1 Lookalike (US, 5%) — Custom_Recruiting-Leads_08-05-2025 LOOKALIKE 8.5–10.1M ACTIVE Aug 27, 2025 Top of LAL ladder, properly sized
2 Lookalike (US, 3%) — Custom_Recruiting-Leads_08-25 LOOKALIKE 5.3–6.3M ACTIVE Aug 6, 2025 Mid LAL
3 Lookalike (US, 1%) — Custom Audience_08-05-2025 LOOKALIKE 1.9–2.2M ACTIVE Aug 6, 2025 Tight LAL
4 Custom_Recruiting-Leads_08-05-2025 CUSTOM 39,200–46,100 ACTIVE Aug 5, 2025 The seed for the LALs. "Recruiting Leads" naming — likely a sold-lead or registration export from 10 months ago. Refresh candidate.
5 All Site Visitors (180D) PLATFORM ~20 people ⚠️ ACTIVE May 5, 2025 CRITICALLY BROKEN — should be hundreds of thousands. Pixel not properly seeding this audience.
6 Visited Auto LP (180D) PLATFORM ~20 people ⚠️ ACTIVE May 5, 2025 SAME BROKEN STATE — Auto landing page audience essentially empty.
7 FB Mil.com Page Likers/Followers PLATFORM 999K–1.2M ACTIVE Apr 28, 2025 Healthy size — Military.com's FB page audience
8 FB Mil.com Page Engagers (365D) PLATFORM 341K–401K ACTIVE Apr 28, 2025 Healthy engagement audience
9 IG Mil.com Followers PLATFORM 30K–35K ACTIVE Apr 28, 2025 Small but legit
10 IG Mil.com Account Engagers (365D) PLATFORM 93.6K–110K ACTIVE Apr 28, 2025 Healthy IG engagement audience

Inactive audiences (~28 broken placeholder LALs)

ALL 28 inactive lookalikes are sized at exactly 1,000 people — Meta's signature for a "broken" / orphaned lookalike (seed audience deleted or invalid). Examples:

These map directly to Mo's 30-day plan B4 task: "Delete ~30 dead placeholder lookalikes"CONFIRMED. Slightly fewer than 30 (count is ~28) but the finding is exact.

Critical broken state — the retargeting layer doesn't exist

All Site Visitors (180D) = ~20 people. Visited Auto LP (180D) = ~20 people.

These are PLATFORM-subtype audiences (Pixel-seeded website audiences) that should contain everyone who has visited military.com or auto.military.com in the last 180 days. They are essentially empty (~20 people each).

Two interpretations:

  1. The Pixel isn't properly feeding these audiences. Likely cause: cross-domain tracking issue between military.com (the content site, Dataset 587241028099131) and the lead-gen funnel (Dataset 332555186604235). The Pixel that fires on auto.military.com is the lead-gen one, and its audience aggregation isn't writing back to these account-level audiences.

  2. SAC (Special Ad Category) is filtering them out. Financial Products SAC restricts Pixel-derived audiences for retargeting. This is the more likely explanation — under SAC, these audiences simply don't accumulate users because Meta filters them as not eligible.

Either way: this account effectively has NO retargeting layer. Mo's audit framework should be updated: under SAC, retargeting Pixel-seeded audiences may not be available at all. The page-engagement audiences (FB/IG, healthy at 30K–1.2M) ARE allowed under SAC, but website-Pixel-seeded ones are not.

This is critical context for the W4 Audiences workstream: under SAC, the legitimate audience seeds are: - ✅ Customer-list (advertiser-provided): the Recruiting-Leads seed and its LALs - ✅ FB/IG engagement (on-Meta surfaces): page likers, engagers, IG followers - ❌ Pixel-seeded website retargeting: blocked or broken under SAC

The "B1 — Define Engaged audience from FB/IG page engagers" task in Mo's 30-day plan is the right move because the engagement audiences (#7–#10 above) are healthy and usable.

The "Mil FB Customer Match 4.12.21" question

Mo's audit referenced "Mil FB Customer Match 4.12.21 (Full List) — last refreshed May 2025 (13+ months ago)". That specific name is NOT in the current audience inventory.

What's there instead: - Custom_Recruiting-Leads_08-05-2025 — created Aug 5, 2025 (~10 months old)

Possibilities: - The "4.12.21" list was archived/deleted and replaced by the "Recruiting-Leads_08-05-2025" list (this would be the "May 2025 refresh" Mo referenced, but dated Aug not May). - The "4.12.21" list is in a different ad account or business. - The audit conducted before today already led to its removal.

Recommend: confirm with Lauren which is the "live" customer-match list — the Recruiting-Leads_08-05-2025 (39K-46K seed) is the only Custom-subtype audience currently active in this account, and its 1%/3%/5% LALs are powering the ALC and Max Val campaigns.

Opportunity Score: 99/100 — CONFIRMED

Account-level Opportunity Score: 99 out of 100. EXACT MATCH to Mo's audit finding.

The single live recommendation

Field Value
Type offsite_conversion
Recommendation Maximize number of conversions performance goal
Lift estimate 17% lower cost per result
Opportunity score lift 1 point (would take 99 → 100)
Stage pre_create_guidance

Decode: Meta is suggesting a campaign-objective optimization tweak that would yield a 17% lift. The body text suggests it's pre-create guidance (not a recommendation against existing campaigns). Likely flagged because the account has multiple optimization goals across BAU/ALC/Max Val and Meta thinks consolidating around offsite_conversion goal would be cleaner.

The fact that the only outstanding recommendation is a 1-point lift means structural levers are exhausted. Mo's audit conclusion holds: "leverage is in measurement plumbing, creative, and the success metric — not structure."

Anomaly Signals: NONE FLAGGED

API returned: "No anomaly signal data available for the given criteria."

This is interesting. Mo's audit cited "2 narrow Custom ad sets flagged by Meta anomaly detector." Possibilities:

  1. Those anomalies have cleared since Mo's pull (the ad sets are still active with the same ~Custom names but no longer flagged).
  2. The anomaly endpoint surfaces a narrower set than the in-product detector.
  3. Meta resolved the flags after seeing performance.

Recommended check: Tuesday Open Ads Manager → Campaign view → look for any in-UI anomaly badges on Custom (Auto BAU) (120240808864440498) and Custom (Home BAU) (120227142278180498). If clean, the issue is resolved. If still flagged, the API just isn't exposing them — Mo can address via the UI.

Auction Ranking Benchmarks (last 30d)

Optimization cohort: OFFSITE_CONVERSIONS + complete_registration + prospecting (new customers).

One ad surfaced with diagnostics:

Ad TYFYS_Video_M_Animation_Swipe_03/09/26 (120241039108910498)
Quality Ranking Average
Engagement Rate Ranking Below Average (Bottom 35% of ads)
Conversion Rate Ranking Above Average
Diagnosis "This ad is not spurring interest."

Key insight: TYFYS has good conversion rate (above average) but weak engagement (bottom 35%). The ad earns the click-throughs that lead to conversion — but most users scroll past it. This is the profile of a niche/identity creative that converts well within a small interested segment but won't scale broadly.

Recommended action: keep TYFYS at BAU low spend (where it works) but do NOT scale it into Max Val or broad audiences. This is exactly what Mo's v3 audit concluded — keep it in BAU only.

Other ads not surfaced by the auction-ranking endpoint:

The endpoint only flagged TYFYS_03/09 — the other top spenders (Odometer, Lower-Your-Auto, Lower-Your-Home) aren't surfaced as having auction-ranking issues. This suggests they're all operating in the "expected" auction quality range, even Odometer despite its high CPL ($38.85 in Max Val). The reason Odometer is expensive isn't auction quality — it's the broken value signal in Max Val campaigns optimizing for ROAS against malformed Purchase value data.

Auction overlap diagnosis (the cannibalization question)

The auction-ranking endpoint did NOT surface significant cross-campaign overlap. No "merge campaigns" or "consolidate ad sets" recommendations were returned.

This validates Mo's Integrated Audit finding: the BAU/ALC/MaxVal trio is intentional and not cannibalizing. The media buyer's structural design is sound.

Mapping to Mo's 30-day plan audience workstream

Mo's task Live status Recommended action
B1: Define Engaged audience from FB/IG page engagers Audiences EXIST (#7–#10, sized 30K–1M). Not currently used as ad-set targeting based on ad-set names (only Broad and interest-named sets are visible) Build new ad set: targeting FB Page Engagers + IG Engagers (suppression-excluded). Could be the warm/retargeting layer.
B2: Replace stale 2021 customer-match list with 180d sold-leads Current live list is "Custom_Recruiting-Leads_08-05-2025" (39K-46K), 10 months old, NOT 13. Still stale; needs Lauren's fresh export of sold-leads from last 180d. Get fresh sold-lead CSV from Lauren → rebuild Custom audience → rebuild 1%/3%/5% LALs
B3: Build suppression/exclusion audiences All Site Visitors and Visited Auto LP are broken (~20 people each), so suppression-by-pixel isn't viable. Suppression must be customer-list based (uploaded sold-leads → exclude from prospecting) Use the Recruiting-Leads CUSTOM audience as a suppression list on prospecting campaigns
B4: Delete ~30 dead placeholder lookalikes ~28 confirmed broken (all 1,000 size, INACTIVE) One-shot cleanup task. Low risk.

What's worth flagging now

  1. The retargeting layer doesn't functionally exist. All-Site-Visitors and Visited-Auto-LP audiences are essentially empty (~20 people). Under SAC, the Pixel-seeded website retargeting may not be allowed. Account effectively has only customer-list LALs + page-engagement audiences. No warm-website retargeting layer.

  2. The "Custom_Recruiting-Leads" seed is 10 months old. Refreshing it with last-180-day sold leads (per B2) is high-leverage because: - All three active LALs (1%, 3%, 5%) are downstream of this seed - A 10-month-old seed underweights recent buying behavior - Lauren has the fresh data; this is a 1-day task

  3. The 28 broken placeholder LALs are a cleanup-only task — no positive impact from leaving them, no risk from deleting them. Inactive state is safe to delete.

  4. The page-engagement audiences are an under-used warm layer. FB Page Likers (1M), Page Engagers (341–401K), IG followers (30K), IG engagers (93–110K) — all healthy sizes, all SAC-compliant. None visible as targeted audiences in current ad sets. Building an ALC or ad set targeting these = real warm-audience layer the account currently lacks.

  5. TYFYS is correctly tagged by Meta as low-engagement, high-conversion. Confirms keeping it in BAU low-spend (where it works) and NOT scaling it into Max Val. v3 audit conclusion intact.

  6. Opportunity Score is 99/100. Confirms Mo's "no structural fixes; leverage is in measurement, creative, metric" thesis. The 1-point recommendation is a minor objective tweak.

  7. No active anomaly flags. The "2 narrow Custom ad sets flagged" issue from Mo's earlier audit has cleared.

← Back