Connecting Claude to the entire Meta business surface — Pixel, Catalog, Ads, Pages, Instagram, WhatsApp, Threads.

Pixel + Conversions API P1 · Ship first

Browser fbq events fire on the website; the same events also fire server‑side via Conversions API. Meta dedupes them on a shared event_id. Result: ad attribution that survives ATT, ad blockers, and cookieless browsers. Without this, every dollar Supernova spends is unattributed.

The dedup flow

Events to fire

CAPI request shape

curl -X POST "https://graph.facebook.com/v25.0/$PIXEL_ID/events" \
  -H "Content-Type: application/json" \
  -d '{
    "data":[{
      "event_name":"Purchase",
      "event_time": 1715000000,
      "event_id":"ord_2026_05_08_8347",
      "action_source":"website",
      "event_source_url":"https://www.kawader-cine.com/shop/confirmation",
      "user_data":{
        "em":["<sha256(email)>"],
        "ph":["<sha256(+970...)>"],
        "fbc":"fb.1.<ts>.<fbclid>",
        "fbp":"fb.1.<ts>.<random>",
        "client_user_agent":"...",
        "client_ip_address":"..."
      },
      "custom_data":{
        "value": 450.00, "currency":"ILS",
        "content_ids":["TEMPL_457"], "content_type":"product",
        "order_id":"S00857"
      }
    }],
    "test_event_code":"TEST12345"
  }' \
  -H "Authorization: Bearer $CAPI_TOKEN"

Commerce Catalog Feed P1 · High leverage

Push the 367 published, rentable Odoo products into a Meta Commerce Catalog. Once in, products tag in IG posts and Reels (Instagram Shopping), appear inside WhatsApp chats as carousels, and become eligible for Dynamic Product Ads — Meta auto‑generates ad creative per product based on user intent.

Two methods, both supported

Field mapping (Odoo → Meta Commerce)

Filter rule

Pull only rent_ok=True AND website_published=True. This mirrors the existing filter in tools/odoo/export_catalog_for_bot.py — reuse that XML‑RPC connection helper rather than reimplementing.

Organic Posting — FB Page + Instagram + Threads P3 · After App Review

Meta gives a uniform two‑step "container → publish" pattern across IG and Threads. Page posts are simpler (one POST). Once wired, every Sparkling Reel, Gear Insights digest, IBNS BTS clip, and Gear Talk teaser ships with a single Claude command.

Instagram publish flow

Variants supported

• Feed image / video — single asset.
• Reels — media_type=REELS + share_to_feed=true for double exposure.
• Carousel — N child containers (max 10) → one parent container with children=[c1,c2,...].
• Stories — needs business verification + Advanced access. Defer.

Rate limit

50 published posts per IG account per rolling 24h. Plenty for organic; keep ad‑creative pushes via Marketing API on the Ads track instead.

Threads — separate API, same shape

Threads runs at https://graph.threads.net/v1.0/ (NOT graph.facebook.com). Same container→publish dance. 250 posts per profile per 24h. Out of beta and publicly available since 2024. Useful for repurposing Gear Insights blurbs as text Threads, no extra creative cost.

Marketing API — Insights & Audiences P2 · After Pixel

Two halves: read (Insights — what's happening with Supernova's spend) and write (Custom Audiences — push Kawader's customer list back into Meta for retargeting + lookalikes). Insights is read‑only and trivial. Custom Audiences requires care because it's PII.

Insights — async report pattern

# 1. Submit
POST /v25.0/act_$AD_ACCOUNT_ID/insights
  fields=campaign_name,spend,impressions,clicks,ctr,actions,cost_per_action_type
  level=campaign
  time_range={"since":"2026-04-22","until":"2026-05-08"}
# → returns {report_run_id}

# 2. Poll
GET /v25.0/$REPORT_RUN_ID
# → {async_status: "Job Completed"}

# 3. Fetch
GET /v25.0/$REPORT_RUN_ID/insights

Custom Audiences — hashed contact upload

Kawader has a customer list in Odoo (res.partner). Hash emails (lowercase, trim, SHA‑256) and phones (E.164, SHA‑256), then push:

POST /v25.0/$CUSTOM_AUDIENCE_ID/users
{
  "schema": ["EMAIL_SHA256", "PHONE_SHA256"],
  "data": [
    ["abc123...", "def456..."],
    ["xyz789...", "uvw012..."]
  ]
}

Then Lookalike from that audience: POST /act_$ID/customaudiences {subtype:"LOOKALIKE", lookalike_spec:{ratio:0.01,country:"PS"}}. 1% lookalike = closest match. Useful for Supernova's targeting brief.

WhatsApp Cloud API + Flows + Click‑to‑WhatsApp P1 · Biggest unlock

Today Baileys handles Ameer's personal inbox brilliantly with Gemini 2.5 Pro for Arabic, Odoo catalog awareness, and a 30‑turn memory. What Baileys cannot do: send approved templates without ban risk, serve in‑chat catalog cards, receive Click‑to‑WhatsApp ad attribution, run Flows (multi‑screen forms inside chat). Cloud API does all four.

The recommended split

How they coexist: register a second Kawader business number in WABA for Cloud API. Baileys keeps Ameer's personal number. They never share a number. Routing logic in tools/whatsapp-bot/index.js already namespaces by JID, so the bot can stay phone‑number‑agnostic.

Send template message — basic shape

POST https://graph.facebook.com/v25.0/$PHONE_NUMBER_ID/messages
{
  "messaging_product": "whatsapp",
  "to": "970599xxxxxxx",
  "type": "template",
  "template": {
    "name": "rental_quote_ready",
    "language": {"code": "ar"},
    "components": [
      {"type":"body","parameters":[
        {"type":"text","text":"أمير"},
        {"type":"text","text":"سوني FX3"},
        {"type":"text","text":"٤٥٠ شيقل / يوم"}
      ]}
    ]
  }
}

WhatsApp Flows — the killer feature

Flows are server‑driven multi‑screen forms inside the chat. Imagine: customer taps a CTWA ad → drops into chat → bot sends a Flow with screens for "Pick your rental dates · Choose kit · Confirm address". Customer fills it out without ever leaving WhatsApp. No website redirect. Submission lands as a structured webhook payload Kawader can route into Odoo as a quote draft.

Flow templates Kawader should ship in v1:

• Rental Quote Builder — date range + kit selection + delivery → Odoo sale.order draft.
• Production Inquiry — project type, budget range, timeline → Notion task in HQ DB.
• IBNS Casting Form — for episode‑specific casting calls.

Lead Ads → Custom Audience Loop P2 · Compounds with Pillar 4

Supernova runs Lead Ads (in‑Meta forms users fill without leaving the app). Today those leads arrive in Naeem's inbox, get forwarded, and drop. With the API: webhook fires → Kawader fetches full lead → routes to Odoo as a res.partner + a Notion task for follow‑up + adds them to a "Recent Leads" Custom Audience for retargeting + triggers a WhatsApp template within 1 hour.

Ad Library — Competitive Intelligence P4 · Ongoing

Meta's Ad Library is fully public — every active and historical ad globally, queryable by API. Free.

For Kawader: weekly cron via Claude that pulls ads from competing rental houses (Cinerent, Camera House, Stash, etc.) + competing production companies, summarizes hooks/offers/creative trends, and posts a digest into Notion. Same script could compare Supernova's creative posture against the field.

GET /v25.0/ads_archive
  ?search_terms=cinema+rental
  &ad_reached_countries=['PS','JO','EG']
  &ad_active_status=ALL
  &fields=ad_creative_bodies,ad_creative_link_titles,page_name,ad_delivery_start_time,ad_snapshot_url