From 630c5f79f87afcc6209edf3d04d3db31c2da49d7 Mon Sep 17 00:00:00 2001
From: Jazma Foskin <82051355+jfoskin@users.noreply.github.com>
Date: Mon, 30 Sep 2024 16:29:46 -0400
Subject: [PATCH] Update custom-domain.md

---
 src/connections/sources/custom-domain.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/src/connections/sources/custom-domain.md b/src/connections/sources/custom-domain.md
index a4a265190d..ab78a0c972 100644
--- a/src/connections/sources/custom-domain.md
+++ b/src/connections/sources/custom-domain.md
@@ -98,3 +98,5 @@ Customers who have access to the Custom Domain feature can rename analytics to `
 ### What happens to the Analytics.js cookies already set on the user's browser prior to a Custom Domain implementation?
 Analytics.js cookies are not lost in the transition to Custom Domain. When users revisit your website, the previous Analytics.js cookies continue to be fetched and added to events, if available.
 
+### Custom domain for a new AJS source within the same workspace
+Custom domain is enabled for all AJS sources during the initial setup. If you plan to use an existing domain, you need to update the source settings with the custom domains.