Domain Hosting
Domain Hosting is where you tell Paminga which of your branded domains and subdomains should serve the things Paminga produces — landing pages, forms, CTAs, the tracking beacon, hosted assets, and the API your published pages talk to.
Each hosted domain is provisioned automatically on AWS CloudFront, secured with an auto-issued SSL certificate, and — once you point a single CNAME record at us — ready to serve traffic on your brand.
You can host as many domains as you need, across as many root domains as you need, with one row per purpose.
Domain Hosting Types
Paminga supports hosting five subdomain types. Each type plays a specific role, and several depend on others — Paminga handles the dependency chain for you when you add a new domain.
Paminga Tracking Beacon
Hosting Paminga's Tracking Beacon from your own domain means ad blockers will never block your tracking beacon.
Did you know that tracking beacons from many marketing automation platforms are blocked by popular ad blockers?
A blocked tracking beacon means no tracking of page views for those visitors, and can mean missing UTMs and other on-site engagement.
This is why getting started with Paminga includes adding a subdomain from which to host our tracking beacon.
Ad blockers will never block javascript loaded from your own domain. 🙂
Add a domain of type "Paminga Tracking Beacon". We suggest something like ping.yourdomain.com.
This will allow Paminga to serve our javaScript tracking beacon from your own subdomain instead of a Paminga-owned domain.
This makes your tracking beacon unblockable, ensuring all website events are tracked, and that every event/visit happens within the context of a Marketing Channel and Source – which are key for attributing conversions to their proper sources.
API Domain
Paminga's renderers for Landing Pages, Forms, and CTAs all make calls to Paminga's backend for personalization and dynamic content.
Setting up a subdomain within your own domain ensures that those calls will never be blocked by popular ad blockers.
An API Domain is a prerequisite for Landing Page and CTA, and Form rendering under the same root domain. If you don't already have one when you add either of those types, Paminga offers to create it for you in the same step.
File Hosting / File Manager
Serves images, PDFs, and other files you upload to Paminga's File Manager from your branded subdomain (e.g. files.yourdomain.com).
This type is trackable — link clicks resolve to a Domain Group so visitor activity attributes correctly. You'll be asked to pick the Domain Group when you add the domain.
Landing Page Domains
Hosts your published Landing Pages on your branded subdomain (e.g. events.yourdomain.com, try.yourdomain.com).
You can add as many Landing Page Domains as you like, and each one can sit under a different root domain.
Landing Page Domains are trackable and support optional Google Analytics 4 and Google Tag Manager IDs. If you provide them, Paminga injects the corresponding tags into pages published on that domain.
Asset Rendering (Forms, Landing Pages, CTAs)
Your subdomain for Asset Rendering serves the appropriate asset renderer that turns embedded Paminga Forms and CTAs – as well as Landing Pages – into the live, dynamic, and personalized elements your visitors see.
Hosting asset rendering on your own subdomain (e.g. renderer.yourdomain.com) preserves the first-party experience that script-blocking policies and privacy-conscious browsers increasingly require.
The Renderer is a prerequisite for Landing Page Domains under the same root, and depends on the API Domain. As with the API Domain, Paminga will offer to create it for you when needed.
Adding a Domain
Go to Domain Hosting and click Add Domain.
Pick the Hosting Type and enter the Domain you want to use. Paminga validates the format as you type.
Automatic Dependency Creation
If the type you selected requires other types — for example, a Landing Page Domain requires an API Domain and a Renderer Domain under the same root — and Paminga doesn't already have those for the root domain you entered, you'll see a checkbox offering to create them in the same step.
The default subdomains are pre-filled (paminga-api.yourdomain.com, renderer.yourdomain.com). You can edit them if your DNS scheme uses different prefixes.
Leave the box checked and click Add Domain. Paminga creates the dependencies first, then the domain you actually wanted. If anything fails partway through, the dependency domains that were already created are rolled back automatically — you won't end up with orphaned half-setups.
Domain Group
For trackable types (File Hosting and Landing Page Domains), you'll be asked to pick a Domain Group. Your default group is selected automatically.
Google Analytics & Google Tag Manager
Landing Page Domains expose two optional fields:
- Google Tag Manager ID — must be in the form
GTM-XXXXXXX - Google Analytics ID — must be a GA4 ID in the form
G-XXXXXXXXXX
Either, neither, or both is fine. If you enable both, Paminga warns you that this can cause duplicate tracking unless you've configured GTM carefully — most teams that use GTM manage GA tags through it and don't need the GA4 ID set separately on the domain.
Duplicate Warning
For most hosting types Paminga expects one domain per root — one beacon, one API, one renderer, one file host. If you try to add a second of the same type for a root that already has one, you'll see a warning. This is a soft warning, not a block: you can proceed if you have a reason to.
Landing Page Domains are the exception — multiple Landing Page Domains under the same root are perfectly normal, and no warning is shown.
DNS Setup
After you add a domain, Paminga begins provisioning it on AWS CloudFront. This takes anywhere from a few seconds to a few minutes. You're free to navigate away — provisioning continues in the background.
Once the underlying infrastructure is ready, the row's DNS Setup column shows Action Required with an orange warning icon.
Hover (or click) Action Required to see the exact CNAME record(s) you need to add at your DNS provider.
Copy DNS Instructions
Click Copy DNS Instructions to put a fully-formatted block on your clipboard. You can paste this straight into an email, Slack message, or ticket for whoever runs your DNS — it includes the record type, the name, what it should point to, the purpose of the record, and a note that the SSL certificate will be issued automatically once the record resolves.
Automatic SSL & Verification
Paminga checks DNS resolution on a continuous schedule. As soon as your records resolve correctly:
- An SSL certificate is provisioned automatically (no action required from you).
- The domain's status moves to Active.
- The DNS Setup column flips from "Action Required" to a green check.
There's no need to come back and click anything.
Statuses
The Status column reflects where each domain sits in its lifecycle:
| Status | Meaning |
|---|---|
| Provisioning... | AWS infrastructure is being created. Usually clears within a few minutes. |
| Waiting for DNS | Infrastructure is ready; Paminga is waiting for your CNAME to resolve. |
| Active | DNS resolves, certificate is issued, domain is live and serving. |
| Failed - contact support | Something went wrong during provisioning. Reach out to Customer Success. |
| Deleting... | Teardown is in progress. The row disappears once teardown completes. |
The DNS Setup column is independent of the status column — it reflects a live check against your authoritative DNS, not the cached state.
Filtering and Refreshing
Use the Hosting Type filter at the top right of the table to focus on one type at a time. Click Refresh to re-pull the table — useful while you're watching a freshly-added domain move through provisioning.
Edit a Domain
For Landing Page Domains and File Hosting domains, an Edit action is available in the row's Actions menu. Editing lets you change the Domain Group (and, for Landing Page Domains, the GA4 / GTM IDs) without re-provisioning.
The other types — Beacon, API, and Renderer — have nothing to edit, so they don't expose an Edit action.
The domain itself and its hosting type can't be changed after creation. To switch a domain to a different name, delete it and add a new one.
Delete a Domain
The Actions menu on each row offers Delete.
Dependency-Aware Deletion
If you try to delete a domain that other domains depend on — for example, deleting the only API Domain for a root that has a Landing Page Domain under it — Paminga blocks the deletion and tells you exactly which dependent domains are in the way. Delete those first, then come back to the parent.
If you have another domain of the same type under the same root that can pick up the dependency, deletion proceeds normally — Paminga only blocks when removing the domain would actually orphan something.
Soft Teardown
Deletion isn't instant. The row enters Deleting... while AWS resources are torn down in the background, and disappears from the table once teardown completes.
Your ability to access account settings may depend on the permissions setup by your organization.
