Landing pages
One product, one page, one decision to make
A storefront is built for browsing. An advertisement is not — it makes a promise about one specific thing, and the page it lands on should be about that thing and nothing else. An Akkad landing page is a single item, a single URL and a single call to action, built from the same catalogue and the same order pipeline as everything else you sell.
A landing page binds one item to one slug within your business. It is served at your subdomain followed by the page's own path, and it resolves on a custom domain too if you have attached one, so the address in an ad can be your own brand rather than a platform's.
Everything downstream is the ordinary machinery. An order placed on a landing page enters the same order list as a counter sale, deducts the same stock, obeys the same shipping and discount rules where you have scoped them to landing pages, and goes to the same courier. The page is a different front door, not a different business.
01
Why a separate surface at all
One product, one page, one URL
The temptation with paid traffic is to send it to the shop and hope. It rarely works, because a shop asks the visitor to make choices and an advertisement has already made one for them. A landing page removes the choices: no category rail to wander into, no cross-sell, no search. The item, the reasons to buy it, and the form.
Send ad traffic to a page that matches the ad
One page per offer means the headline, the photo and the price a visitor saw are the ones they arrive at. You can run several pages for several offers on the same catalogue, each with its own URL, and tell them apart afterwards.
Measure one thing at a time
Pixels are configured per page, so a campaign's numbers belong to that campaign rather than being averaged into everything happening on your storefront.
A shorter path to an order
The order form sits on the page itself. There is no cart step and no checkout step to lose people between — a visitor who is convinced can act where they are standing.
02
What you configure per page
Each landing page carries its own settings. Two pages for two campaigns can differ in language, layout, payment options and defaults without touching each other.
| Setting | What it controls |
|---|---|
| Template | Classic or Boost — the shape of the page. |
| Language | Any of the fourteen storefront languages, right-to-left included. |
| Logo style | Circle, rounded or wide, to suit how the mark was drawn. |
| Default order status | Whether an order from this page lands as pending or as processing. A page for cold ad traffic often wants a confirmation call first; a page for a warm audience does not. |
| Default payment method | Cash or card as the recorded method on the resulting order. |
| Online payment mode | Cash on delivery only, cash and online, or online only — resolved at serve time. |
| Success message | What the buyer reads after the form is submitted. |
| Meta and TikTok pixel IDs | Set per page, with their own event settings. |
| Promo code field | Shown or hidden on this page's form. |
| WhatsApp button | Shown or hidden. |
| Low-stock indicator | Shown or hidden. |
| Shipping cost | A delivery figure for this page. |
03
The order form, field by field
The form is built rather than fixed. Every one of the eight standard fields carries four independent settings: whether it appears, whether it is required, where it sits in the order, and what it is called on this particular page.
| Field | Typical treatment |
|---|---|
| Recipient name | Visible and required almost everywhere. |
| Primary phone | The field that matters most in a cash-on-delivery market — usually required. |
| Second phone | Often visible but optional; couriers use it when the first number fails. |
| City | Rendered as a free-text field or as a courier city picker, depending on the address mode. |
| Address line 1 | The street address. |
| Address line 2 | Landmark, floor, or a note for the driver. |
| Postal code | Commonly hidden where post codes are not used. |
| Commonly hidden; a phone number is what a courier actually calls. |
Every label is yours to rewrite. If your customers understand “nearest landmark” better than “address line 2”, say that instead. The storefront checkout uses the identical structure, so a form you have tuned on a landing page is not a different mental model from the one on your store.
The address picker follows your live courier, not a saved snapshot
How the address section behaves — a plain city field, or a picker populated from a courier's own city and region lists — is worked out at the moment the page is served, from the shipping integration your business currently has connected. Change couriers and the very next visitor gets the new courier's city list. A page that stored its address mode when it was created would keep serving the previous courier's cities until someone remembered to edit every landing page they had ever published, and the failures would arrive later, as addresses the new courier does not recognise.
04
Two templates
Two layouts, aimed at genuinely different jobs. One presents a product; the other argues for it.
| Template | Character |
|---|---|
| Classic | A store header, an image gallery, product information, a variant selector, the order form and a footer. Familiar and calm — the right shape when the visitor already knows who you are and simply needs to see the item and order it. |
| Boost | Direct response. No store header at all, a full-bleed gallery that advances on its own, and on mobile one continuous white sheet carrying the content blocks you have written. Nothing invites the visitor back out of the page; everything moves down it toward the form. |
05
The Boost content blocks
Boost pages carry merchant-written content between the photo and the form. Fill in the ones you have something real to say with, and leave the rest alone.
Badge
A short line of up to forty characters sitting over the photograph — the one claim you want read before anything else.
Announcement
A text strip with its own on-and-off switch, for the thing that is true this week rather than always.
Countdown
A deadline you set as a date and time, counting down on the page. Honest only if the deadline is, which is why it is a date rather than a rolling timer.
Stock meter
A visible indication of how much is left, drawn from the item's real stock rather than a number you invent.
Trust badges
A delivery line and a returns line, shown together. The two questions a cash-on-delivery buyer asks before they hand over money.
Details grid
Label-and-value pairs — dimensions, materials, contents, warranty. The specification a serious buyer scrolls looking for.
Testimonials
Name, location, text and a one-to-five rating per entry, written by you from what customers have told you.
FAQ
Question-and-answer pairs, answering the objections that would otherwise arrive as messages you have to reply to one at a time.
06
How a Boost page holds together
Content blocks usually go wrong the same way: a merchant fills in three of eight and the page renders five empty boxes. That does not happen here.
Empty blocks are absent, not blank
A block you have not filled in is simply not part of the page. A half-filled Boost page looks like a page someone designed, not a template someone abandoned — which means you can publish with three good blocks today and add the rest when you have something worth writing.
Write as much as the offer deserves
A simple product might need a badge and a details grid. A considered purchase might need testimonials, an FAQ and trust badges. The page grows and shrinks to the argument rather than forcing the argument into a fixed layout.
Nothing leads away from the form
Boost drops the store header on purpose. Every navigation element you add to a single-offer page is a way for paid traffic to leave without ordering.
The gallery does the work on its own
A full-bleed gallery advancing by itself shows a visitor the second and third photograph without asking them to discover a control — on mobile, where most ad traffic arrives, the discovery usually never happens.
07
Pixels and payment mode
The two settings that decide what a landing page reports and how it takes money.
A pixel per page
Meta and TikTok pixel IDs are set on the landing page itself, so each campaign reports against its own page rather than sharing a measurement surface with your storefront.
Paste the whole snippet
You can paste an entire base-code block, a no-script fallback URL, an Events Manager link, or a bare ID, and the real identifier is extracted from it. Something genuinely unrecognisable comes back as a clear error rather than being quietly dropped and discovered weeks later as missing data.
Cash on delivery, online, or both
Payment mode is per page. Cash on delivery is the default and hides every pay-online element. Online payment is a higher-tier capability, and where it is not available the page falls back to cash on delivery rather than showing an option that cannot complete.
08
Publishing, and what happens at the limit
A landing page is created unpublished and goes live when you say so. How many can be live at once depends on your plan.
- 1
Build it against a real item
Pick the item, the template, the language and the form. The page reads the item's live price, stock, images and variants, so there is nothing to copy across and nothing to keep in step afterwards.
- 2
Publish
The page records when it was published and the URL it was published at. Until then it is not reachable, so a half-written page cannot be found by anyone.
- 3
Point your advertising at it
The URL is your subdomain plus the page's own path, or your custom domain if you have attached one. Orders arrive tagged as landing-page orders and can be filtered as such in the orders list and in reporting.
- 4
If you exceed the limit or the plan lapses
Pages beyond your allowance serve a self-contained temporary-unavailable page rather than an error or a blank screen. Your published setting is untouched, so restoring the plan restores the page exactly as it was — the same template, blocks, form and pixels.
09
Questions
How is a landing page different from a storefront page for the same item?
A storefront item page sits inside a shop, surrounded by navigation and other products. A landing page is the whole page: one item, your own headline and content blocks, its own form, its own pixels, its own payment mode and its own URL. Use one when the traffic came from an ad about one specific offer.
Do I have to duplicate the product to build a page?
No. A landing page points at an item in your catalogue and reads its live price, stock, images and variants. Changing the item changes the page. Orders from the page deduct the same stock as any other sale.
What happens if I switch couriers after publishing?
Nothing on your side. The address section is derived at serve time from whichever shipping integration is currently connected, so the next visitor sees the new courier's city and region lists. There is no stale snapshot to go back and clear.
Can I run several landing pages at once?
Yes — one per offer, each with its own slug, template, language, form, pixels and payment mode. How many can be published simultaneously depends on your plan.
Do I have to fill in every Boost block?
No. Blocks you leave empty are omitted from the page entirely rather than rendering as empty space, so a page with three well-written blocks reads as deliberate.
Can a landing page take card payments?
Where online payment is available on your plan and connected, a page can be set to cash on delivery, online, or both. If that is not in place, the page resolves to cash on delivery rather than offering a payment path it cannot complete.
Related
Growth and marketing
Pixels, server-side conversion events, and why a cash-on-delivery market should not fire Purchase at checkout.
لەسەر کاتالۆگی خۆت تاقی بکەرەوە
بە پلانی گونجاو دەست پێبکە، کاڵاکانت لە فایلێکی ئێکسڵەوە بهێنە، و هەر لە هەمان ڕۆژدا فرۆشگا، کاشێر و دەفتەری داواکاریی کارات هەبێت.
پلانی بێبەرامبەر بەردەستە. بۆ تاقیکردنەوە پێویستی بە کارت نییە. هێنانی داتا لیستی کاڵای ئێستاکەت لەگەڵ خۆت دەهێنێت.