Overview
This FAQ explains how to correctly configure DNS records, domains, subdomains, and SSL certificates for Mapp Fashion across production, test, and multi-environment setups. Proper configuration ensures reliable tracking, cookie handling, and smooth development.
When should DNS records and certificates be set up?
As early as possible. Having DNS records and SSL certificates in place upfront helps avoid delays later in the development and testing process.
I have multiple test or development environments — how should these be configured?
Each environment should have its own namespace and domain. This separation ensures that test data does not affect the quality of recommendations. All environments can use the same IP addresses provided.
I use multiple TLDs for different countries (e.g., example-clothing.co.uk, example-clothing.com). How should this be set up?
Each domain (TLD) should be delegated and configured separately. Create a dedicated subdomain for Mapp Fashion under each domain, for example:
mappfashion-production.example-clothing.co.ukmappfashion-production.example-clothing.com
Configure each of these domains individually using modern DNS delegation practices (rather than sharing or reusing a single A record configuration), and repeat this setup for every TLD in use.
What about certificates for test environments?
We can generate and provide SSL certificates for test environments using Let’s Encrypt, so you don’t need to manage these yourself.
Why are subdomains required?
Using a dedicated subdomain and CNAME helps prevent third-party cookie restrictions. This setup allows Mapp Fashion to set first-party cookies that your application can reliably access.
Can we test tracking before DNS records and HTTPS are configured?
No. End-to-end tracking requires both DNS configuration and valid HTTPS certificates. Without these, full tracking functionality cannot be tested.