Connect Your Domain
Nearly everything Paminga puts in front of your visitors — the tracking beacon, your forms and CTAs, your landing pages, your PDFs and images — can be served from subdomains of your own domain.
That's not cosmetic. A URL on your own domain loads when a Paminga-owned one wouldn't: ad blockers and privacy-focused browsers treat third-party domains as second-class citizens, and increasingly just drop them. Serving from your domain is what keeps your tracking complete and your assets loading.
You do this in Domain Hosting. Each subdomain you add is provisioned automatically on AWS CloudFront, secured with an auto-issued SSL certificate, and live as soon as you point a single CNAME record at us via DNS.
What Runs on Your Domains
Domain Hosting supports five subdomain types. Add the ones you need. Paminga works out the dependencies between them and offers to create any missing prerequisites in the same step.
| Type | What it serves | Suggested subdomain |
|---|---|---|
| Paminga Tracking Beacon | The javascript that tracks your website visitors | ping.yourdomain.com |
| Asset Rendering | The renderer that turns embedded Forms and CTAs into the live elements visitors see | renderer.yourdomain.com |
| Landing Page Domains | Your published Landing Pages on as many subdomains as you need | content.yourdomain.com |
| File Hosting | Images, PDFs, and other files you upload to the File Manager | files.yourdomain.com |
| API Domain | The backend calls your forms, CTAs, and landing pages make for personalization and dynamic content | paminga-api.yourdomain.com |
You can host as many domains as you need, across as many root domains as you need.
What You Actually Need
Which types you set up depends on what you intend to do:
- Track visitors on your website — add a Paminga Tracking Beacon domain. Ad blockers will never block javascript loaded from your own domain.
- Embed Paminga Forms or CTAs on your website — add an Asset Rendering domain. It depends on an API Domain, and Paminga offers to create that for you in the same step.
- Publish Landing Pages — add any number of Landing Page Domains. It depends on both an API Domain and an Asset Rendering domain under the same root; again, Paminga offers to create them for you.
- Link to PDFs, images, or other files from emails and landing pages — add a File Hosting domain.
File Hosting and Landing Page Domains are trackable, so you'll be asked which Domain Group their traffic belongs to. Landing Page Domains also accept optional Google Analytics 4 and Google Tag Manager IDs.
Sending Email Is Separate
The DNS records that authorize Paminga to send email from your domain — SPF, DKIM, DMARC — are not part of Domain Hosting yet. Those are covered in Email Delivery, and your Customer Success rep works through them with you during onboarding.
Setting Up DNS
Add a domain, and Paminga starts provisioning immediately. Within a few seconds to a few minutes, the row's DNS Setup column shows Action Required — hover it to see the exact CNAME record you need.
There's a Copy DNS Instructions button that puts a fully-formatted block on your clipboard: record type, name, what it points to, the purpose of the record, and a note that SSL is issued automatically. Paste that straight into a ticket or an email to whoever runs your DNS.
Once your record resolves, Paminga issues the certificate, flips the domain to Active, and turns the DNS Setup column green. There's nothing to come back and click.
The full walkthrough — adding domains, dependency handling, statuses, editing, and deletion — lives in Domain Hosting.
If your account is hosted in the EU, the CNAME targets differ from the US ones. The DNS instructions Paminga generates are always correct for your account — use those rather than any target you've seen elsewhere.
Why CloudFront
Everything Paminga hosts for you — landing pages, files, the beacon, the renderers — is served through the Amazon CloudFront Content Delivery Network (CDN).
A CDN caches your content at edge locations around the world and serves each visitor from the one nearest them. A prospect in London gets your PDF from a European edge rather than a server in the US. Less latency, faster pages, better conversion rates — and no infrastructure for you to run.
Landing pages themselves are stored in a private Amazon S3 bucket and served through CloudFront. SSL certificates are issued and renewed automatically.
