From a8982bf730d3a530a10b04f9ff3bb7d165f713c2 Mon Sep 17 00:00:00 2001
From: forstisabella <92472883+forstisabella@users.noreply.github.com>
Date: Wed, 30 Jul 2025 15:23:22 -0400
Subject: [PATCH 1/4] Update user-deletion-and-suppression.md

---
 src/privacy/user-deletion-and-suppression.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/privacy/user-deletion-and-suppression.md b/src/privacy/user-deletion-and-suppression.md
index 6f056051c0..40861daf5b 100644
--- a/src/privacy/user-deletion-and-suppression.md
+++ b/src/privacy/user-deletion-and-suppression.md
@@ -59,7 +59,7 @@ Warehouse deletions occur using a DML run against your cluster or instance. Segm
 
 ### Deletion requests tab
 
-The deletion requests tab shows a 30-day overview of your deletions pipeline, including a Regulations usage tracker and a deletion requests status table. 
+The deletion requests tab shows a 30-day overview of your deletions pipeline, including a Regulations usage tracker and a deletion requests status table. The deletion requests summary tab shows the status of all your deletion requests from the last 30-day and might not accurately reflect your current deletion request limits.
 
 To navigate to the deletion requests tab, open the Segment app and navigate to **Privacy > Deletion and Suppression > Deletion**.
 

From c8081f0bacd6e45a82f132801c89b3ee735bad6c Mon Sep 17 00:00:00 2001
From: Joe Ayoub <joe.ayoub@segment.com>
Date: Tue, 5 Aug 2025 16:03:13 +0100
Subject: [PATCH 2/4] New Destination - Nextdoor

---
 .../catalog/actions-nextdoor-capi/index.md    | 26 +++++++++++++++++++
 1 file changed, 26 insertions(+)
 create mode 100644 src/connections/destinations/catalog/actions-nextdoor-capi/index.md

diff --git a/src/connections/destinations/catalog/actions-nextdoor-capi/index.md b/src/connections/destinations/catalog/actions-nextdoor-capi/index.md
new file mode 100644
index 0000000000..9996dbaf67
--- /dev/null
+++ b/src/connections/destinations/catalog/actions-nextdoor-capi/index.md
@@ -0,0 +1,26 @@
+---
+title: Nextdoor Conversions API Destination
+---
+
+{% include content/plan-grid.md name="actions" %}
+
+[Nextdoor Conversion API](https://yourintegration.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank”} allows advertisers to track and send conversion events directly to the platform. This API provides a programmatic way to record and attribute conversions, enabling advertisers to measure the effectiveness of their advertising campaigns.
+
+This destination is maintained by Nextdoor. For any issues with the destination, [contact their Support team](mailto:ads-api@nextdoor.com).
+
+## Getting started
+
+1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank”} search for "Nextdoor".
+2. Select Nextdoor Conversions API and click **Add Destination**.
+3. Select an existing Source to connect to Nextdoor Conversions API.
+4. Go to the [Nextdoor Ads Manager](https://ads.nextdoor.com/v2/manage/api){:target="_blank"}, then find and copy the **API key**, **Nextdoor Advertiser ID** and **Nextdoor Pixel Id** values. If these values are not visible in the Ads Manager, you may need to contact your Nextdoor Account Manager to ensure that your Nextdoor account has been whitelisted for the (Ads API) functionality. 
+5. Enter the **API key**, **Nextdoor Advertiser ID** and **Nextdoor Pixel Id** values in the Nextdoor Conversions API destination settings in Segment.
+6. In the Mappings tab, configure the Actions to send data to Nextdoor Conversions API. 
+7. Enable the Destination and Actions. 
+8. See [Nextdoor's documentation](https://developer.nextdoor.com/reference/conversion-api){:target="_blank”} for additional instructions.   
+
+{% include components/actions-fields.html %}
+
+## Nextdoor Browser Plugin Action
+When the **Nextdoor Conversions API** destination receives website data from a Segment JavaScript source, the **Nextdoor Browser Plugin** automatically grabs the **Nextdoor click ID** / **ndclid** from the querystirng in the page URL, and passes it to the **Send Conversion** Action. Supplying the **ndclid** boosts attribution accuracy and is strongly recommended for website tracking. The plugin is enabled by default as soon as the destination is created.
+

From e45a7a9d2e593113c1f87e275eb348a0184703c3 Mon Sep 17 00:00:00 2001
From: forstisabella <92472883+forstisabella@users.noreply.github.com>
Date: Wed, 6 Aug 2025 09:33:28 -0400
Subject: [PATCH 3/4] Update src/privacy/user-deletion-and-suppression.md

Co-authored-by: Sharon Adewusi <sadewusi@twilio.com>
---
 src/privacy/user-deletion-and-suppression.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/privacy/user-deletion-and-suppression.md b/src/privacy/user-deletion-and-suppression.md
index 40861daf5b..34d756a846 100644
--- a/src/privacy/user-deletion-and-suppression.md
+++ b/src/privacy/user-deletion-and-suppression.md
@@ -59,7 +59,7 @@ Warehouse deletions occur using a DML run against your cluster or instance. Segm
 
 ### Deletion requests tab
 
-The deletion requests tab shows a 30-day overview of your deletions pipeline, including a Regulations usage tracker and a deletion requests status table. The deletion requests summary tab shows the status of all your deletion requests from the last 30-day and might not accurately reflect your current deletion request limits.
+The deletion requests tab shows a 30-day overview of your deletions pipeline, including a Regulations usage tracker and a deletion requests status table. The deletion requests summary tab shows the status of all your deletion requests from the last 30 days and might not accurately reflect your current deletion request limits.
 
 To navigate to the deletion requests tab, open the Segment app and navigate to **Privacy > Deletion and Suppression > Deletion**.
 

From 5f5666dba9e792c610d1ef9abe96c395981b1db2 Mon Sep 17 00:00:00 2001
From: pwseg <86626706+pwseg@users.noreply.github.com>
Date: Wed, 6 Aug 2025 21:37:44 -0700
Subject: [PATCH 4/4] update front matter

---
 .../destinations/catalog/actions-nextdoor-capi/index.md        | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/src/connections/destinations/catalog/actions-nextdoor-capi/index.md b/src/connections/destinations/catalog/actions-nextdoor-capi/index.md
index 9996dbaf67..6d0fe4b922 100644
--- a/src/connections/destinations/catalog/actions-nextdoor-capi/index.md
+++ b/src/connections/destinations/catalog/actions-nextdoor-capi/index.md
@@ -1,5 +1,7 @@
 ---
 title: Nextdoor Conversions API Destination
+id: 66cc76e29693c9e5591bf029
+beta: true
 ---
 
 {% include content/plan-grid.md name="actions" %}
@@ -23,4 +25,3 @@ This destination is maintained by Nextdoor. For any issues with the destination,
 
 ## Nextdoor Browser Plugin Action
 When the **Nextdoor Conversions API** destination receives website data from a Segment JavaScript source, the **Nextdoor Browser Plugin** automatically grabs the **Nextdoor click ID** / **ndclid** from the querystirng in the page URL, and passes it to the **Send Conversion** Action. Supplying the **ndclid** boosts attribution accuracy and is strongly recommended for website tracking. The plugin is enabled by default as soon as the destination is created.
-
