What is DNS Setup?
DNS (Domain Name System) setup involves creating an A Record in your domain provider. For Northbeam, this means adding a subdomain—commonly namedi—that points to an address provided in your dashboard.
This simple step enables first-party tracking using your domain, unlocking advanced tracking capabilities while avoiding many of the limitations of third-party tracking.
Setting up your DNS
Having a dedicated DNS entry for Northbeam improves our ability to track your customers when they return to your website after their first visit. In your domain provider, you’ll need to create an A Record, namedi, pointing to a specific address you’ll find in your dashboard. This allows first-party tracking.
If the subdomain i is already mapped to something, please get in touch with us so we can help you pick a different subdomain name.
Examples
www.my-store.com- Top-level domain:
my-store.com - Create a DNS record for
i.my-store.com
- Top-level domain:
try.my-product.comandget.my-product.com- Top-level domain:
my-product.com - Create a DNS record for
i.my-product.com
- Top-level domain:
Instructions are available for multiple Domain providers
- Generic
- GoDaddy
- CloudFlare
- Google Domains
Following the onboarding flow here will lead you to success**
:tada:Instructions
Follow these steps to enable first-party tracking with Northbeam:-
Log In to Your Domain Provider
Access the DNS settings for the domain you want to use with Northbeam. -
Create an A Record
- Host Name: Use
i - Address: This is provided in your Northbeam dashboard. Copy and paste it exactly as shown.
- Examples of A-Record Entries
Here’s what your DNS setup might look like:i.northbeam.io-> The top-level domain here isnorthbeam.io.i.company-2.com-> The top-level domain here iscompany-2.com.
- Host Name: Use
-
Save Your Changes
Once saved, your DNS setup will enable first-party tracking through Northbeam.
⚠️ Additional Step for Domains Using DNSSEC
If your domain has DNSSEC (DNS Security Extensions) enabled, you’ll need to add a CAA record to allow certificate issuance by Let’s Encrypt. Without this step, your SSL certificate may fail to generate, resulting in issues like404 not found or certificate mismatch errors.