# Adapting Ben Heath's method to GCC, Saudi and Egypt clients

> **This file is our adaptation. Ben Heath did not say any of it.** He works mainly with UK,
> US, Canadian and Australian accounts. Each point below names the rule of his it builds on
> (`framework.md` section), then gives our local interpretation. Check platform features,
> regulations and integrations in the live account before relying on them.

## 1. Know the numbers, in local currency

- His small-budget line is under about $3,000 a month, and the tiny-budget line is under
  about $600 a month [§8].
  - **SAR** is pegged at 3.75 per USD, so these become about SAR 11,250 and SAR 2,250.
  - **AED** is about 3.67 per USD, so about AED 11,000 and AED 2,200.
  - **EGP floats.** Convert at the current rate on the day; don't hard-code it.
- **Cash on delivery (COD)** e-commerce, which is common in KSA and especially Egypt:
  - Meta's "purchase" event is an order, not collected revenue.
  - Calculate true CPA and ROAS on **delivered and paid** orders. Use the client's confirmation
    and delivery rates (refused and returned COD orders are often a large share).
  - The target ROAS on *reported* purchases has to be inflated accordingly. Example: with 70%
    delivery, a 3x true ROAS needs about 4.3x reported.
  - This is his "know your numbers / Meta can't see refunds" rule [§1, §5 value rules].
- **Use value rules for COD risk.** If delivery or refusal rates differ by region, city, device
  or OS, set bid rules from that data. Examples: lower bids on cities with high refusal rates;
  higher bids on iOS if iOS buyers refuse less. Measure the uplift first; he insists on real
  data, not Meta's +50% default [§5].
- **Feed confirmed outcomes back where possible.** Send confirmed or delivered orders as a
  separate CAPI event or offline event, or as purchase value adjustments. This applies his
  "fire the event only for the real outcome" logic [§3, §11]. Verify what the store platform
  (Salla, Zid, Shopify, WooCommerce) supports natively.

## 2. Tracking on regional platforms

- Rule: pixel plus CAPI, and Pixel Helper to check events don't fire on page load [§2].
- **Salla, Zid and similar platforms** have their own Meta pixel or CAPI integrations.
  Confirm three things for each store:
  - CAPI is actually enabled.
  - Event deduplication works (pixel and CAPI event IDs match).
  - Purchase fires on the thank-you page only, with value and currency (SAR, AED, EGP).
- **Compare Meta with the store backend** each month. COD and WhatsApp orders often bypass the
  pixel entirely.
- **WhatsApp-driven sales.** Where many orders close in WhatsApp chat, optimise for the deepest
  trackable event with enough volume [§3]:
  - Conversations or messaging leads, ideally with a qualifying question.
  - Or a website purchase where the checkout is the real close.
  - Don't optimise for clicks.

## 3. Structure

- **One campaign per market.** He treats location as the one valid split and tells you not to
  mix countries with very different CPMs [§4, §12].
  - KSA, UAE, Kuwait, Qatar and Egypt usually have very different CPMs and purchasing power.
  - Default: **separate campaigns per country**, especially Egypt vs GCC.
  - Inside a country, keep one campaign and one ad set per product range.
- **City splits** only when the business is genuinely local: a branch, a delivery radius,
  installation coverage.
- **Small Egyptian budgets** often fall in his "tiny" bracket. Apply the strict rules [§8]:
  - One offer, one campaign, one ad set.
  - Direct Sales or Leads only.
  - Patience measured in conversions.

## 4. Targeting and language

- Controls: location, language only when it matters, minimum age only when legally required
  [§5].
  - **Language** often matters in the GCC because of large expat populations.
    - Arabic-only creative: set the language control to Arabic, or test Arabic and English
      ad sets.
    - Bilingual offers: separate campaigns or ads per language.
    - This is a "real reason" deviation, done deliberately.
- **Gender** is now suggestion-only, and his workaround is a −90% value rule [§5]. Use it for
  clearly single-gender offers (abayas, men's grooming, women-only gyms or clinics). Keep
  gendered messaging and imagery culturally appropriate.
- **Age:** respect local legal limits for regulated categories.
- **Leave everything else broad.** Don't recreate the old interest-stack habits common in the
  region; he says interests are suggestions you "can't really get wrong" [§5].

## 5. Creative for Arabic audiences

- His core rules hold: native look, one angle per ad, proof in every ad, a hook in the first
  3 seconds, and a mix of statics and video [creative.md].
- **Dialect matters, and it is an angle and avatar lever.**
  - Saudi or Khaleeji dialect for KSA and Gulf.
  - Egyptian dialect for Egypt.
  - MSA (Modern Standard Arabic) for formal or regulated categories.
  - Test dialect vs MSA as a style or angle variable, using a batch of ads, not a single ad.
- **RTL layout.** Check text overlays, price banners and the CTA position on right-to-left
  layouts.
  - Meta's automatic **creative enhancements** (text overlays, AI image variations, cropping)
    can break Arabic text or produce culturally off images. Audit them after every edit; he
    warns they re-enable when you edit or duplicate [§14].
  - Turn off **"optimize text per person"** if Meta mixes languages, or for regulated claims.
- **Local proof works best.** Use Saudi or Gulf customer testimonials, reviews in Arabic, and
  local delivery promises ("delivery in 24 hours in Riyadh"). Use local trust signals such as
  Maroof, licences or CR numbers where relevant. This is his "proof raises perceived
  likelihood" applied locally.
- **Guarantees and urgency** fit regional buying behaviour [§13]:
  - Free returns, pay on delivery, delivery-time guarantees.
  - "Limited quantity"; offers tied to Ramadan, Eid, White Friday, National Day or salary day.
- **Creators.** His "partnership ads are the cheat code" advice translates well; Saudi and
  Gulf micro-influencer culture is strong.
  - Use 2–4 micro-creators.
  - Always get ad or boost rights.
  - Brief: CTA, two benefits, one credibility point, and multiple hooks.
  - Creator Marketplace availability and creator density in MENA may be limited; verify.
  - Local influencer advertising rules apply (for example licensing or disclosure
    requirements in KSA and UAE). Check them.
- **Modest, compliant imagery.** Meta's policies plus local norms. Health, beauty and food
  claims may also fall under local regulators (for example Saudi FDA rules for health
  claims). Check before you scale.
- **AI-looking statics underperform** (his Oct 2026 finding). This is especially true when AI
  renders Arabic text badly. Use real product photos and composite AI only around them.

## 6. Lead generation (services, real estate, clinics, education, B2B)

- His 2026 defaults [§11]:
  - Higher intent form, SMS OTP, autofill off, mandatory phone.
  - Conditional qualifying questions with an end page for non-leads.
  - Optimise for qualified leads.
- **Local notes:**
  - SMS OTP generally works in KSA, UAE and Egypt. Test it on older audiences, which he
    flags as a risk.
  - Lead quality is a common complaint in Egypt and KSA real-estate and clinic campaigns,
    which is exactly his case for paying 50–80% more per lead when most leads are junk.
  - Qualifier ideas: budget band in SAR or EGP, city or district, timeline, cash vs
    instalment, nationality or residency where the offer depends on it (only where legal
    and non-discriminatory).
  - **WhatsApp** is the default contact channel. Use the WhatsApp additional action or chat
    follow-up he describes [0Ji-AhLkR8w], and route leads to WhatsApp within minutes
    (speed to lead).
  - **Working-week timing:** Sunday–Thursday in KSA and much of the GCC (UAE uses
    Monday–Friday), Friday prayer, and Ramadan's late-night activity. If you use his
    B2B-hours ad scheduling idea (lifetime budget), set it to local working hours, or
    don't use it at all for B2C.

## 7. Seasonality and scaling

- His rule: spend more in strong periods and less in weak ones, and compare year on year
  [§8, §10].
- **Strong periods:**
  - Ramadan (shopping peaks before Eid, late-night browsing).
  - Eid al-Fitr and Eid al-Adha.
  - White Friday / Black Friday, 11.11, Saudi National Day (23 Sep), UAE National Day (2 Dec).
  - Back to school.
  - Salary days (in KSA, salaries commonly land around the 27th).
- **Weak or odd periods:** Eid holiday days themselves for some B2B; summer travel months in
  the GCC.
- **One-off promos:** don't force creative tests during short sales; let Meta pick quickly
  [§7].
- **Scaling:** use his stepped or 3% rules [§9].
  - Ramp budgets **before** peak days; Meta needs learning time.
  - CPMs rise sharply in Ramadan and Q4. Judge on ROAS or CPA, not CPM.

## 8. Omnipresent content (high-ticket regional businesses)

- It fits his criteria (LTV around $1,000+, expertise-based) for real-estate developers,
  clinics (cosmetic, dental, IVF), private education, consultancies and B2B agencies.
- Use the same mechanics [§12]: 14 ad sets, a cap of 1 impression per 7 days, Maximize reach,
  CBO off.
- Build it per country and per language.
- Run it alongside the lead campaign.

## 9. What not to change

- Consolidated structure, the performance goal, offer-first thinking, patience measured in
  conversions, no duplicate-campaign scaling, and judging on ROAS or CPA all apply unchanged.
- Local agency habits to unlearn using his rules:
  - Many interest ad sets
  - Engagement campaigns "for reach"
  - Boosted posts
  - Daily budget tinkering
