Custom domain

Every brand already gets a free branded affiliate portal at yourbrand.rekomi.com on every plan, including Starter. Custom domain is the Growth-tier upgrade that puts that same portal (and your tracking script) on a domain you own (e.g. affiliates.brand.com) instead of the rekomi.com subdomain. It swaps api.rekomi.com for the domain you control in the tracking script URL. The browser then treats every tracking request as first-party from your site's perspective, which:

• Sidesteps ad blockers that match generic patterns on third-party tracking hosts.
• Avoids Safari ITP's third-party cookie partitioning.
• Avoids Chrome's storage partitioning for embedded scripts.

Realistic accuracy lift: ~3-5 percentage points on top of the default browser-pixel tracking. Combined with the browser pixel feature, brands using a custom domain see ~93-96% conversion attribution vs ~88-91% on the default api.rekomi.com host. This is one unified feature at Growth: portal white-label plus first-party tracking on a single host you own.

Prerequisites

• Growth plan (or higher).
• DNS administrative access for the domain you want to use (e.g. brand.com).
• About 5 minutes for the setup, plus 30-60 seconds for our system to provision a TLS certificate on the brand's subdomain.

Setup

1. Pick your subdomain

In Dashboard > Settings > Custom domain (Growth), enter a subdomain you control. Most brands use affiliates.<their-domain> or go.<their-domain>. You can use any subdomain you own. This one subdomain does both jobs: it loads your tracking script first-party and hosts your affiliate signup pages (your primary campaign at the root, each campaign at /<campaign>). There are no separate per-campaign domains to set up. One subdomain covers your whole program.

Common choices:

• affiliates.brand.com
• go.brand.com
• partners.brand.com
• track.brand.com

Pick one that doesn't already point at another service. We'll show you the exact CNAME record to add in the next step.

2. Add the CNAME record

After saving the subdomain, the dashboard displays one CNAME record:

affiliates.brand.com   CNAME   cname.rekomi.com

Add this at your DNS provider (Cloudflare, Namecheap, Route53, GoDaddy, Squarespace, or wherever you manage DNS for the parent domain). Save the record and wait for DNS propagation (usually under a minute, sometimes up to a few minutes).

If you use Cloudflare for your own DNS, set the record's proxy status to DNS only (gray cloud), not Proxied. Your subdomain needs to CNAME straight through to our edge (cname.rekomi.com); proxying it on your side puts another TLS layer in the way and breaks certificate issuance.

3. Verify

Click Verify in the dashboard. We do a DNS lookup on your subdomain and check that the CNAME chain resolves to cname.rekomi.com (or an equivalent Rekomi-controlled target).

If verification passes, we automatically:

• Register your subdomain on our Cloudflare-for-SaaS edge.
• Issue a TLS certificate for it automatically.
• Update your install snippet to use your subdomain instead of api.rekomi.com.

The dashboard shows a "Provisioning certificate" indicator while the cert is being issued (~30-60s typical). During this window your install snippet stays pointed at api.rekomi.com so your site keeps working uninterrupted. Once the cert is active, the snippet auto-switches.

4. Re-copy your install snippet

If you pasted the install snippet on your site before verifying your custom domain, copy it again now. The new snippet uses your subdomain. The conversion-firing snippet on your thank-you page (the window.Rekomi.q.push(["convert", ...]) block) does NOT need to change.

Affiliate signup on your custom domain

The same subdomain also serves your affiliate signup pages, so your whole program lives on one domain. There are no separate per-campaign domains to configure:

• https://affiliates.brand.com/ is your primary campaign's signup page.
• https://affiliates.brand.com/<campaign> is each campaign's own signup page.

Share these links with affiliates instead of the free yourbrand.rekomi.com versions. The page loads from your own domain, so it reinforces your brand and avoids the third-party look. Tracking and the signup pages share the one subdomain; nothing extra to set up per campaign.

How it works under the hood

1. Your visitor loads brand.com.
2. Your install snippet pulls affiliates.brand.com/api/v1/r/loader.js (or api.rekomi.com if you skipped the custom domain).
3. Browser resolves affiliates.brand.com via your DNS: affiliates.brand.com → CNAME → cname.rekomi.com → ultimately our hosting provider.
4. Request hits our routing layer. Our routing layer sees the Host: affiliates.brand.com header, matches it to your org (registered when you verified), and serves the loader script.
5. The loader script POSTs clicks + conversions to affiliates.brand.com/api/v1/r/c and affiliates.brand.com/api/r/e. From the browser's perspective these are first-party calls; cookies set by these responses are first-party to brand.com.

Because the script is loaded from your own subdomain, generic tracker filters (EasyPrivacy, uBlock standard lists) don't match the URL pattern, and the cookies set by click responses survive Safari ITP's third-party caps.

Failure states + recovery

The dashboard shows one of these statuses:

Disconnecting

To stop using a custom domain, open Settings > Custom domain and click Disconnect. You'll be asked to type a confirm phrase (defense against accidental clicks).

After disconnect:

• We remove the subdomain from our routing layer.
• Your install snippet reverts to api.rekomi.com.
• You should remove the CNAME from your DNS provider for hygiene.
• Re-copy the install snippet to your site.

In-flight tracking (clicks already attributed) is not affected. Future tracking falls back to the default host.

What this does NOT solve

• Cross-domain attribution (visitor clicks on phone, buys on desktop): custom domains don't help. Cross-device tracking requires login-bound attribution.
• Domain-level blocklists (api.rekomi.com explicitly added to a user's blocklist): if a user adds your subdomain to their blocklist too, this helps the average case but not the targeted case.
• Brand-paid Cloudflare for SaaS / Argo / strict Bot Fight Mode: complex CF setups in front of your domain can interfere with our cert provisioning. Use DNS-only mode on the tracking subdomain.
• Stripe-tracked conversions: those flow through Stripe's own webhook and aren't affected by tracking-host blocking. Custom domain only helps the browser-pixel + click-tracking paths.

Pricing

Growth plan ($39/mo or $390/yr).

Related

• Browser pixel tracking
• S2S tracking