Skip to main content

Landing-page playbook

This is the blueprint Algerian merchants use to consistently hit 3–8 % conversion rate from cold paid traffic. Use it as a starting template, then iterate.

Landing pages vs. product pages​

DZBuild has both. They serve different purposes:

Use a product page when…Use a landing page when…
You're selling a catalogYou're running paid ads to one product
Customers browse multiple productsEach campaign is one product, one offer
You rely on category pagesYou want full creative control over the layout
SEO traffic mattersAds are the only source

You can run both in parallel — landing pages for paid, product/category pages for SEO and direct traffic.

Plan limits​

Landing pages are gated by plan:

PlanLanding pages includedNotes
Free0You can buy individual pages for 1,000 DZD lifetime each — no recurring fee.
Pro3Three published landing pages in your subscription.
UnlimitedunlimitedSpin up as many as you need.
EnterpriseunlimitedSame as Unlimited.

If a paid plan expires, existing landing pages remain in /dashboard/landing-pages but stop publishing on the storefront — re-subscribe to restore them, or pay 1,000 DZD per page to keep specific ones live. Renewal: /dashboard/subscribe → ▶ How to renew in-app guide, or DZBuild YouTube.

Setting up a landing page​

  1. Open /dashboard/landing-pages → Create landing page.

  2. Pick the product the page sells.

    CRITICAL: Set the product_id correctly. If product_id is left null, shipping calculations don't know which product is in the cart and the storefront silently undercharges shipping. Always select a real product.

  3. Pick a template — single-product layouts with hero / benefits / reviews / FAQ / order form built in.

  4. Customize copy, photos, colors.

  5. Set the Pixel override (optional but recommended for campaign-level attribution).

  6. Publish.

The landing page lives at /landing/{slug} on your storefront domain (note: /landing/, not /lp/).

The 7-block structure​

1. Hero (above the fold)​

  • Big product photo — real, not stock. Mobile-first.
  • One-sentence headline with benefit + price ("X premium bag for 1900 DZD only — delivered everywhere").
  • CTA button — scrolls to order form. Color contrasts with the background.

2. Benefits (3–5 bullets)​

Three to five benefit lines max. Use icons:

  • 🚚 Cash on delivery, all 58 wilayas
  • ⭐ 4.7/5 from 200+ customers
  • 🔄 Easy returns within 7 days

3. Product showcase​

  • 4–6 lifestyle photos
  • 1 short video if you have one (15s autoplay loop, no sound)

4. How it works / What's in the box​

  • 3 steps for "how it works" products
  • A list of contents for "what's in the box"

5. Reviews / testimonials​

  • 3–5 reviews with photos
  • Real names + locations ("Sarah, Algiers")
  • Mix of 4 and 5 stars (all-5 looks fake)
  • Source from real reviews captured by Product Reviews

6. FAQ​

  • 5–8 questions, expandable accordions
  • Cover: shipping cost per wilaya, return policy, delivery time, COD, sizing, warranty

7. Order form​

  • The CTA buttons throughout the page scroll here
  • Required: name, phone, wilaya, qty
  • Optional: variant pickers (color/size — use the Offer Variant Popup add-on for multi-piece offers)
  • Submit order button — large, prominent
  • COD trust badge below

Copy guidelines​

  • Arabic — warm, friendly, conversational. Avoid formal Modern Standard Arabic for casual products; mix in colloquial Darija for relatability.
  • French — clear and direct. Don't translate Arabic literally; rewrite for French sensibility.
  • Avoid superlatives — "the best ever", "world-class". Algerian buyers are sophisticated; superlatives signal "marketing speak."

Pricing tactics​

TacticWhen to use
Strikethrough was/nowHigh-perceived-value items
Bundle pricingCross-sell ("Buy 2 + 1 free")
Free shipping for offers ≥ X DZDHigh-AOV products
Plain pricePremium products, simplicity

Pixel + tracking​

  • Install Facebook Pixel + CAPI
  • Fire Lead on form-fill, Purchase on confirmed order
  • Once you have 50+ purchases, switch your campaign to Optimize for Purchase — Meta moves the algorithm to optimize for buyers, not lookers

A/B testing variants​

If you A/B test (Pro plan), use a clean naming convention:

  • LP-X-control — original
  • LP-X-test1 — testing one change
  • LP-X-test2 — testing another change

Don't change two things at once — you won't know which won.

Speed​

Mobile load time is the conversion killer:

  • ≤ 1 s = ideal
  • 1–2 s = ok
  • 2–3 s = losing 30 %+ of visits before they see the page
  • 3 s+ = mostly wasted ad spend

Compress hero images aggressively (WebP, ≤ 200 KB). Lazy-load below-fold. The Image Cadre add-on helps frame photos correctly while imgproxy serves WebP automatically.

Audience matching​

A landing page is only as good as the traffic. Match the audience to the offer:

  • Wide audience for low-price impulse products (perfumes, accessories)
  • Narrow lookalike for higher-price considered products (electronics, fashion)
  • Retargeting for cart abandoners — see Abandoned cart strategy

When to clone vs. build new​

  • Clone an existing high-converter when adapting to a new product in the same category.
  • Build new when changing market segment or core messaging.

Common mistakes​

  • Linking to your storefront from the landing page — sends customers down a rabbit hole. Don't.
  • Multiple CTAs going to different places — one CTA, one destination (the order form).
  • Tons of text — most readers scan, not read. Keep block copy short.
  • No variant pickers — if your product has variants, the customer needs to choose them on the page.
  • product_id left null — silently undercharges shipping. Always pick a real product.
  • Wrong Pixel override — campaigns then attribute to the store-level Pixel instead of the campaign Pixel; spend gets mis-attributed.