Your own domain: when it is worth it and how to connect it

A training manager opens your proposal and scrolls to the last page, where the link to the program sits. The link reads dwrrah.com/your-name. Nobody will mention it in the meeting. But the proposal next to yours carried a link with the institute's own name on it, and that difference gets read even when it is never said.

And yet, if you are selling one course to an audience that already follows you, buying a domain in your first week is money spent in the wrong place. A domain is not an upgrade you buy early to feel serious; it is a decision with a moment. This article is about that moment, and about how the connection works once it arrives.

You already have an identity. What is missing is the address bar

The first confusion is treating the domain as the identity. It is not. Your academy on the academy site gets an address at dwrrah.com/{slug} from day one, and every page, course and session lives underneath it. Colours, logo and cover images are available on every plan and apply across your site and your catalog without configuring each page.

So a visitor already sees your identity in almost everything: the colour, the logo, the imagery, the shape of the page. The one exception is the strip of text at the top of the browser. The right question is not "how do I look like a brand". It is: what does it cost me to keep the platform's name in the address bar? That answer differs by situation.

Where the address is read, and who needs a domain now

Think about how your learners reach you. Most arrive from a link you sent: a message in a group, a button in an email, a line in your bio. On none of those paths does anyone read the address. People tap and look at whatever opens.

But there are places where the address is read, and judged:

• A written proposal to a company or a public body. It circulates among three people who do not know you, and the link is part of their impression.
• A name you dictate on a call or from a stage. A long compound address does not survive being spoken aloud.
• A landing page behind paid ads. The visitor is cold, and every signal counts.
• A search result, or a screenshot passed around. The address sits right next to the content.
• Correspondence that passes through an IT department. Someone will ask which domain this runs on.

The practical test is simple: how many of those happened to you last quarter? If the answer is zero or one, postpone the domain and spend the time on your course page instead. If the answer is ten, you are already paying for the delay without seeing the invoice.

Turning that test into concrete situations shortens the decision:

Your situation	Domain now?	Do this first
No first course published yet	No	Publish something worth visiting
One or two courses, your own audience	No rush	A course page that explains and convinces
An institute pitching to companies and bodies	Yes, from the first proposal	One name across every document you send
An employer training its own people	Yes	Pages that explain the programs and policies
An established brand with a domain people know	Yes	Do not open a third address for one audience
You run paid advertising	Yes, with tracking pixels	Know what converts before raising the budget

Four of those rows have nothing to do with looking pretty. An institute working with organisations has to present as one entity at every point of contact, and an employer training its staff needs people to feel they are in their own house, not at an intermediary. A practical call, not a cosmetic one.

There is a third consideration the table does not show: the address you print on your materials, put in your bios and spend money driving traffic to is the one thing that stays with you. Your pages and your learner lists live in your academy either way, but a link written in a hundred places cannot be recalled once it is written. That is not a reason to buy a domain today. It is a reason to buy it before your address is printed in a hundred places.

How the connection actually works

The procedure is shorter than most people imagine. The intimidation comes from the letters DNS, not from the work.

1. Buy the domain from whichever registrar you prefer. You do not buy it from Dwrrah and you do not need to. The domain is yours and stays yours.
2. Add it from your academy settings. From inside your own dashboard, with no support ticket and nobody to email.
3. Place the DNS records shown to you at your registrar. The platform shows exactly which records are needed; you copy them into your registrar's panel.
4. Verify from the same screen. Verification happens where you added the domain, not in some external tool.
5. Watch the status once it is live. The status stays visible, so you know it is working instead of hearing otherwise from a learner.

Underneath this runs Cloudflare for SaaS, a detail you do not need to understand to succeed. Two things are worth knowing. DNS records do not take effect the instant you save them, so do not panic if the domain is not live immediately: that is the internet behaving normally, not the platform failing. And the records must be placed by whoever controls the domain's panel, so if it is registered to someone else, or managed by the agency that built your old site, sort that out before you start. That is what actually stalls people, not the steps themselves.

There is a way back, too. The platform address stays live after you connect a domain, and you can remove the domain whenever you want and fall back to it with nothing lost. That alone makes the experiment low risk.

The domain does not arrive alone on Pro

If the domain is the only thing you switch on from the Pro plan, you are running one of three tools that together build the picture a visitor sees. The other two serve exactly the same purpose, and leaving them off is waste for no reason.

Hiding the platform attribution. A made-with-Dwrrah line appears by default on your public pages, and Pro lets you turn it off. That matters in exactly the situations the domain matters: a proposal to an organisation expecting a single identity, or a brand you are building that would rather not carry another name beside it.

Tracking pixels. You connect measurement tools to your academy's public pages, with nine providers supported: GA4, Google Tag, Google Tag Manager, Google Ads, Meta, TikTok, Snap, Microsoft Clarity and PostHog. You connect them from Settings («الإعدادات»), under Integration and tracking («التكامل والتتبع»). If you spend on advertising, this is the piece that turns spending into a loop you can measure, especially alongside your academy analytics.

One detail worth stating plainly: these pixels are injected on your public pages only, meaning what a visitor sees before signing in. They do not follow a learner inside their account or track their movement through their content. That limit is deliberate, and it favours your learners.

What a custom domain will not do for you

This is the part that stays quiet when somebody sells you a domain as a solution.

• It does not bring traffic. A new domain does not mean a ranking. Rankings come from pages that answer something people search for. The domain is only the address those pages live at.
• It does not give you email on that name. A mailbox on your domain is a separate service you buy from an email provider, and connecting the domain to your academy is a different thing. Platform emails still reach your learners under your academy's name in the sender field, but they are sent from the platform's verified sending domain, not from yours.
• It does not hide everything from everyone. Anyone who digs will work out that a platform sits behind your site. The goal is consistency for an ordinary visitor, not concealment from an investigator.
• It does not protect your content. A domain is an address, not a guard. Someone opening your course on your domain opens it with exactly the permissions they would have on the platform address, and content protection is a separate subject with its own tools.
• It does not renew itself. Renewal happens at your registrar: a new annual commitment you took on when you bought it.

Four mistakes that keep repeating

One: buying the domain before there is anything to put on it. I have seen people own a valuable domain and a single half-written page. The order is backwards. Publish, then connect.

Two: choosing a long domain because it was available. Your name gets dictated on calls and printed on covers. If it takes three attempts to spell out loud, you have lost the reason you bought it.

Three: opening a third address for one audience. If you already have a domain your audience knows, the decision is not to buy a new one for the academy. It is to decide which address the academy should carry, at the provider where you already manage your records.

Four: connecting the domain and leaving the rest of the plan idle. If you moved to Pro for the domain and then left the attribution showing and no pixel connected, you bought three capabilities and switched on one.

The order I would follow pulls all of that together. Start with what costs you no plan at all: your colour, your logo and your cover images, because they are on every plan and create most of the difference a visitor perceives. Then build your pages until the site is worth visiting. Then watch for the first of the reading moments listed above: a first proposal to an organisation, or a first paid campaign. That is when you connect the domain.

The full detail of what is included sits on the branding and custom domain page. The custom domain, the hidden attribution and the tracking pixels start on the Pro plan at 199 SAR a month, while colours and logo are on every plan, starting from 99.

Before paying for anything, try it: the 14-day free trial needs no card and includes Pro features, so you can set the domain up and see your pages without the attribution first. The decision is then about something you have seen, not something you imagined.