Domain Hosting: Your Brand, Paminga's Infrastructure
Domain Hosting is where you tell Paminga which of your branded subdomains should serve everything Paminga produces — the tracking beacon, the API your assets call, the asset renderer, your file uploads, and your landing pages.
Each hosted domain is provisioned automatically on AWS CloudFront, secured with an auto-issued SSL certificate, and — once you point a single CNAME at us — ready to serve traffic on your brand.
Host as many domains as you need, across as many root domains as you need, one row per purpose.
The Five Hosting Types
Each type plays a specific role. Several depend on others — Paminga handles the dependency chain for you when you add a new domain.
Paminga Tracking Beacon
Hosting the tracking beacon from your own subdomain means ad blockers will never block it.
Many MAPs' tracking beacons are blocked by popular ad blockers. A blocked beacon means no tracking of page views for those visitors and can mean missing UTMs, missing engagement, and missing attribution.
Ad blockers will never block javascript loaded from your own domain. 🙂
Suggestion: ping.yourdomain.com.
API Domain
Paminga's renderers for Landing Pages, Forms, and CTAs all make calls back to Paminga's backend for personalization and dynamic content. Hosting the API domain on your root keeps those calls unblockable too.
The API Domain is a prerequisite for Asset Rendering — Paminga will offer to create it for you if you add a domain that depends on it.
File Hosting / File Manager
Serves images, PDFs, and other files you upload to the File Manager from your branded subdomain.
This type is trackable — link clicks resolve to a Domain Group, so visitor activity attributes correctly.
Landing Page Domains
Hosts your published Landing Pages on your branded subdomain — events.yourdomain.com, try.yourdomain.com, whatever you want.
Add as many Landing Page Domains as you like, each under a different root if needed. They're trackable, and they support optional Google Analytics 4 and Google Tag Manager IDs.
Asset Rendering (Forms, Landing Pages, CTAs)
Serves the renderer that turns embedded Paminga Forms and CTAs — plus your hosted Landing Pages — into the live, dynamic, personalized assets your visitors see.
Like the API Domain, this is a prerequisite for Landing Page Domains under the same root. Paminga offers to create it for you when needed.
What Happens When You Add a Domain
- Pick a Hosting Type and enter the domain. Paminga validates the format as you type.
- If the type depends on others — for example, a Landing Page Domain needs an API Domain and a Renderer Domain — and Paminga doesn't already have them, you'll see a checkbox offering to create them in the same step.
- Paminga provisions on AWS CloudFront. This takes seconds to a few minutes. You can navigate away.
- Once infrastructure is ready, the row shows Action Required with the exact CNAME record(s) you need to add at your DNS provider.
There's a Copy DNS Instructions button that puts a fully-formatted block on your clipboard — record type, name, target, purpose, and a note about the auto-issued SSL. Paste that into a ticket for whoever runs your DNS.
- Once your records resolve, Paminga issues the SSL certificate automatically, flips the status to Active, and the green check shows up on DNS Setup.
No coming back to click anything.
Statuses, Briefly
| Status | Meaning |
|---|---|
| Provisioning... | AWS infrastructure is being created |
| Waiting for DNS | Infrastructure ready, waiting on your CNAME |
| Active | DNS resolves, certificate issued, live |
| Failed - contact support | Reach out to Customer Success |
| Deleting... | Teardown in progress |
Dependency-Aware Deletion
You can't accidentally orphan a Landing Page Domain by deleting its API Domain. If a delete would break a dependent domain, Paminga blocks the delete and tells you exactly which dependents to handle first.
If you have another domain of the same type that can pick up the dependency, deletion proceeds normally — Paminga only blocks when removing the domain would actually orphan something.
Why This Matters
Modern privacy-focused browsers and ad blockers treat third-party scripts and third-party domains as second-class citizens — at best. The fix is to make Paminga's infrastructure look like your own. Domain Hosting does that, end-to-end, with automatic provisioning, automatic SSL, and dependency-aware setup.
❌ Don't run your MAP off *.paminga.com for everything and wonder why your tracking is patchy.
✅ Do host the beacon, API, renderer, files, and landing pages on your own branded subdomains. Same Paminga infrastructure, your brand on every URL.
Get Started
- Open Account Settings → Domain Hosting
- Click Add Domain, pick a Hosting Type, enter your subdomain
- Let Paminga create any dependent domains in the same step if prompted
- Copy the DNS Instructions and send to whoever runs your DNS
- Watch the status flip to Active and the green check appear
Read the Domain Hosting docs to dig in.
