Set up the DNS record
Create the DNS record that points your subdomain at OmniLab, and get the certificate issued.
Point your chosen subdomain at OmniLab. This is a single DNS change; the rest is waiting and verifying. Whoever manages your DNS does this — often IT rather than marketing.
Before you begin
- Agree the exact subdomain, for example
experience.yourbrand.com. - Get the target value from your OmniLab Customer Success Manager.
- Confirm who can edit DNS for the domain, and how long a change usually takes to approve internally. This is the step that delays launches, not the technology.
Steps
Lower the record's time-to-live first
If a record already exists at that name, reduce its TTL to 300–600 seconds and wait for the old value to expire before changing it. This means a rollback takes minutes rather than a day.
Create the record
| Type | Name | Value |
|---|---|---|
| CNAME | Your chosen subdomain, for example experience | The target provided by OmniLab |
Use a subdomain, not your root domain. Most DNS providers cannot host a CNAME at the root, and pointing your main website at OmniLab is not what you want.
Wait for it to propagate
Changes usually appear within minutes but can take up to 48 hours depending on your provider and the previous TTL. Check with any public DNS lookup tool rather than only your own browser, which caches aggressively.
Let the certificate issue
OmniLab requests the security certificate automatically once it can see the record. Allow 15–30 minutes after propagation. During that window a browser may warn about the certificate — that is expected and resolves itself.
Test the address
Open a published campaign on the new address in a normal browser. Check the padlock, then run the full journey through to a reward.
If something's blocked
- The certificate warning does not clear after an hour. The record is probably not visible yet, or points somewhere else. Re-check it with a public lookup tool before contacting support.
- The address works for you but not for a colleague. Their network is still holding the old value. Wait out the original TTL.
- Your provider will not accept a CNAME at that name. Some providers block a CNAME where other records already exist at the same name. Use a different subdomain, or ask your provider about their equivalent record type.