{{item.label}}{% if item.required == true %}
(required){%endif%} |
-{{item.type}}{% if item.defaultValue != null and item.defaultValue != "" and item.defaultValue != '{}'%}, defaults to {%if item.type == "array" %}{{item.defaultValue | join: ", " }}{%elsif item.type == "string"%}{{item.defaultValue}} {%elsif item.type == "boolean" %} {{item.defaultValue | upcase }} {%else%} {{item.defaultValue}}{%endif%}.
{%else%}. {% endif %}{{item.description}} |
+{{ item.type }}{% unless item.defaultValue != nil and item.defaultValue != "" and item.defaultValue.size != 0 %}, has no default value.
{% else %}, defaults to {% if item.type == "array" %}{{ item.defaultValue | join: ", " }}{% elsif item.type == "string" %}{{ item.defaultValue }}{% elsif item.type == "boolean" %}{{ item.defaultValue | upcase }}{% endif %}.
{% endunless %}{{ item.description }} |
diff --git a/src/connections/auto-instrumentation/configuration.md b/src/connections/auto-instrumentation/configuration.md
index 1f5af89c19..3c04586a4c 100644
--- a/src/connections/auto-instrumentation/configuration.md
+++ b/src/connections/auto-instrumentation/configuration.md
@@ -23,15 +23,30 @@ After you set up the Signals SDK to capture the signals you want to target, you
### Getting started with rule creation
-1. In your Segment workspace, go to to **Connections > Auto-Instrumentation** and click on a source.
-2. Click **Create Rules**.
+1. In your Segment workspace, go to **Sources** and select a source.
+2. Open the **Event Builder**, then click **Create Rules**.
> info "Where's the Event Builder tab?"
> The Event Builder tab only appears after you've installed the Auto-Instrumentation snippet in your site or app. If you don’t see the tab, double check your implementation or reach out to your Segment CSM.
### Using the Rules Editor
-The Rules Editor is where you define rules that transform raw signal data into analytics events. In the editor, you write functions that convert signals into events and then call them in the `processSignal()` function.
+The Rules Editor is where you define rules that transform raw signal data into analytics events. Using the dropdown-based editor, you can:
+
+- Combine multiple signals into a single event (for example, a click followed by a navigation)
+- Set conditions to control when events should be triggered
+- Assign custom event names
+
+#### Adding event properties
+
+You can enrich your events by adding properties based on signal metadata. For example:
+
+- Capture `product.price` in your **Add to Cart** event
+- Add a boolean field like `couponApplied` to your **Order Completed** event
+
+These properties are sent alongside your event, giving your team deeper insights without requiring any manual instrumentation.
+
+
+
+
## Example rule implementations
-You can use the Signals data definitions on this page to create tracking rules.
+You can use Signals to create tracking rules using the event builder.
### Example: Identify users
+The following screenshot shows an Identify event rule that combines a button click with a successful network response to extract user data and trigger an identify call.
+
+
+
+
+
+
### Example: Track `Add to Cart` events
-This rule shows how you could implement the core ordering events from [the e-commerce Spec](/docs/connections/spec/ecommerce/v2/#core-ordering-overview):
+This rule implements a core ordering event from [the e-commerce Spec](/docs/connections/spec/ecommerce/v2/#core-ordering-overview). It shows a Track event triggered by a button click and a network response, with product details from the response mapped to event properties.
+
+
+
+
\ No newline at end of file
diff --git a/src/connections/auto-instrumentation/images/signals_identify_event.png b/src/connections/auto-instrumentation/images/signals_identify_event.png
new file mode 100644
index 0000000000..43dd9a163b
Binary files /dev/null and b/src/connections/auto-instrumentation/images/signals_identify_event.png differ
diff --git a/src/connections/auto-instrumentation/images/signals_track_event.png b/src/connections/auto-instrumentation/images/signals_track_event.png
new file mode 100644
index 0000000000..58c1f69ccf
Binary files /dev/null and b/src/connections/auto-instrumentation/images/signals_track_event.png differ
diff --git a/src/connections/destinations/actions.md b/src/connections/destinations/actions.md
index 207bcc18f7..8132257e7c 100644
--- a/src/connections/destinations/actions.md
+++ b/src/connections/destinations/actions.md
@@ -350,7 +350,7 @@ This example converts an email address to lowercase and removes extra whitespace
{% endraw %}
```
-Input: `event.properties.email` = "user@example.com"
+Input: `event.properties.email` = " User@Example.com "
Output: user@example.com
@@ -378,9 +378,9 @@ This example formats a phone number by removing non-digit characters, adding a c
{% endraw %}
```
-Input: `event.properties.phone` = "(123) 456-7890"
+Input: `event.properties.phone` = "(234) 567-8901"
-Output: +11234567890
+Output: +12345678901
Explanation:
* The `assign` tag stores the cleaned phone number after applying `strip` and `remove` filters to eliminate whitespace and non-digit characters (for example, `-`, `(`, `)`).
diff --git a/src/connections/destinations/catalog/actions-facebook-custom-audiences/index.md b/src/connections/destinations/catalog/actions-facebook-custom-audiences/index.md
index 5fbf9c529f..204e20c776 100644
--- a/src/connections/destinations/catalog/actions-facebook-custom-audiences/index.md
+++ b/src/connections/destinations/catalog/actions-facebook-custom-audiences/index.md
@@ -16,22 +16,23 @@ hide_action:
Deliver effective Facebook Ads campaigns by defining and syncing [custom audiences](https://developers.facebook.com/docs/marketing-api/audiences/guides/custom-audiences){:target="_blank”} to power ad suppression, acquisition (using lookalikes), retargeting, and more.
-This destination sends audiences, or lists of users, from your data warehouse to Facebook Custom Audiences using Reverse ETL. Syncs can add or remove users from your Facebook Custom Audiences as records are created, updated, or deleted in your warehouse.
-
-> info "This destination only supports Reverse ETL sources"
-> This destination only supports [Reverse ETL sources](/docs/connections/reverse-etl/#what-warehouse-data-sources-does-segment-support). To connect Facebook Custom Audiences to Twilio Engage, use the [Facebook Custom Audiences](/docs/connections/destinations/catalog/personas-facebook-custom-audiences/) destination.
+This destination sends audiences, or lists of users, to Facebook Custom Audiences. You can connect this destination to Reverse ETL sources to sync data from your warehouse, or to Engage Audiences to sync computed audiences.
## Getting started
### Prerequisites
-- A Reverse ETL source already set up. If you don't yet have a Reverse ETL source, follow the instructions in Segment's [Reverse ETL documentation](/docs/connections/reverse-etl/#getting-started). Segment recommends setting an [External ID](#sync-audience) as the primary key for your Reverse ETL model, as you'll need an External ID to remove users from your custom audiences.
+
+- A source already set up.
+ - For Reverse ETL: If you don't yet have a Reverse ETL source, follow the instructions in Segment's [Reverse ETL documentation](/docs/connections/reverse-etl/#getting-started). Segment recommends setting an [External ID](#sync-audience) as the primary key for your Reverse ETL model, as you'll need an External ID to remove users from your custom audiences.
+ - For Engage Audiences: An [Engage Audience](/docs/engage/audiences/) that you can connect to this destination.
- A Facebook account with [ads_management](https://developers.facebook.com/docs/permissions#ads_management){:target="_blank”} permissions for the target Facebook Ad Account(s). The Facebook Ad Account(s) must also be associated with a [Facebook Business Account](https://www.facebook.com/business/help/407323696966570?id=649869995454285){:target="_blank”}.
- Ensure that the user connecting to the destination using OAuth has at least an *Advertiser* or *Admin* role on the ad account. To manage permissions and roles for an ad account, reference [Facebook's documentation](https://www.facebook.com/business/help/186007118118684?id=829106167281625){:target="_blank"}.
### Connect to Facebook Custom Audiences
+
1. From your Segment app, navigate to **Catalog > Destinations** and search for "Facebook Custom Audiences (Actions)".
2. Select the Facebook Custom Audiences (Actions) destination and click **Add destination**.
-3. Select the Reverse ETL source you'd like to connect to your Facebook Custom Audiences (Actions) Destination and click **Next**.
+3. Select the source you'd like to connect to your Facebook Custom Audiences (Actions) Destination and click **Next**.
4. Enter a name for your destination and click **Create destination**.
5. Navigate to your destination's settings page and click **Connect to...** to authenticate with Facebook.
6. Return to the Segment app and enter your Advertiser Account ID. See Facebook's [Find your Facebook ad account ID number](https://www.facebook.com/business/help/1492627900875762){:target="_blank”} documentation for more information.
@@ -123,6 +124,10 @@ Segment automatically hashes any of the following fields that are not already SH
* Gender
+## Additional trait matching
+
+Segment [Trait Enrichment](/docs/engage/trait-activation/trait-enrichment/) allows you to send an expanded list of identifiers or traits to Facebook so that Facebook can try to use these additional data points to match to their user profiles. If you have this feature enabled and implemented any of these traits in your Segment tracking, the Facebook Custom Audiences (Actions) destination can send this data to Facebook. Segment can now also sync multiple emails if the profile contains more than one. Additionally as part of this feature, Segment hashes fields before sending them downstream to Facebook as described in the [Hashing](#hashing) section.
+
## FAQs and troubleshooting
### Audience not creating and/or existing audience list not populating
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..6d0fe4b922
--- /dev/null
+++ b/src/connections/destinations/catalog/actions-nextdoor-capi/index.md
@@ -0,0 +1,27 @@
+---
+title: Nextdoor Conversions API Destination
+id: 66cc76e29693c9e5591bf029
+beta: true
+---
+
+{% 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.
diff --git a/src/connections/destinations/catalog/actions-twilio-messaging/index.md b/src/connections/destinations/catalog/actions-twilio-messaging/index.md
index 53f111b07a..282a97366d 100644
--- a/src/connections/destinations/catalog/actions-twilio-messaging/index.md
+++ b/src/connections/destinations/catalog/actions-twilio-messaging/index.md
@@ -93,7 +93,7 @@ To configure the mapping:
| Field | Description | Notes |
| ------------------------- | --------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Channel** | Choose which channel to send the message on. | Options: SMS, MMS, and WhatsApp. |
+| **Channel** | Choose which channel to send the message on. | Options: SMS, MMS, WhatsApp, and RCS. If selecting RCS, ensure that RCS is enabled in your Twilio account. |
| **Sender Type** | Pick how you want to send the message. | Options: Phone number or Messaging Service. Phone numbers must be approved in Twilio. |
| **Content Template Type** | Select the type of content template. | Options include Inline or templates you’ve built in Twilio. Segment only shows templates that match your selected Channel and Template Type. |
| **To Phone Number** | Enter the recipient’s phone number. | Must be in [E.164 format](https://www.twilio.com/docs/glossary/what-e164){:target="_blank"}. |
@@ -182,4 +182,4 @@ Here are a few things to keep in mind when using the Twilio Messaging destinatio
- **Phone numbers must be approved**. Any phone number you use to send messages must be approved in your Twilio account and support the channel you’re sending on.
- **Message logs and errors**. If a message fails to send, you can view details in your Twilio Console message logs. Common issues include invalid phone number formats or missing required template fields.
-Understanding these details will help you set up your messaging flows smoothly and avoid unexpected errors.
\ No newline at end of file
+Understanding these details will help you set up your messaging flows smoothly and avoid unexpected errors.
diff --git a/src/connections/destinations/catalog/optimizely-web/index.md b/src/connections/destinations/catalog/optimizely-web/index.md
index db6ffc7eef..c203028a89 100644
--- a/src/connections/destinations/catalog/optimizely-web/index.md
+++ b/src/connections/destinations/catalog/optimizely-web/index.md
@@ -64,13 +64,14 @@ Segment also handles the following mapping:
### Page
-Segment maps `page` calls to its own `track` events. For example, invoking `analytics.page('Page Viewed')` using Segment's API maps the event to a `analytics.track('Page Viewed')` event. Segment maps the `track` event to other downstream destinations like a regular Segment `track` event.
+Segment maps Page calls to its `track` events. When you call `analytics.page('