Release 24.30.2

docker-compose.yml

@@ -5,8 +5,17 @@ services:
     command: make dev
     image: jekyll/jekyll:latest
     volumes:
-      - '.:/srv/jekyll'
-      - './vendor/bundle:/usr/local/bundle'
+    - '.:/srv/jekyll'
+    - './vendor/bundle:/usr/local/bundle'
     ports:
-      - 4000:4000
+    - 4000:4000
     container_name: jekyll
+    # If you are on arm64 and experiencing issues with the tests (hangs,
+    # connection reset) then try the following in order:
+
+    # - stopping and removing all downloaded container images
+    # - ensuring you have the latest Docker Desktop version
+    # - factory reset your Docker Desktop settings
+
+    # If you are still running into issues please post in #help-infra-seg.
+    platform: linux/amd64

src/_data/catalog/destination_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination categories last updated 2024-07-23 
+# destination categories last updated 2024-07-25 
 items:
 - display_name: A/B Testing
   slug: a-b-testing

src/_data/catalog/destinations.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination data last updated 2024-07-23 
+# destination data last updated 2024-07-25 
 items:
 - id: 637e8d185e2dec264895ea89
   display_name: 1Flow
@@ -6141,7 +6141,7 @@ items:
   previous_names:
   - Amazon AMC (Actions)
   - Amazon Ads DSP and AMC
-  website: http://www.segment.com
+  website: https://advertising.amazon.com/
   status: PUBLIC_BETA
   categories:
   - Advertising
@@ -25711,7 +25711,7 @@ items:
   previous_names:
   - Display and Video 360 (Actions)
   website: http://www.segment.com
-  status: PUBLIC_BETA
+  status: PUBLIC
   categories:
   - Advertising
   logo:
@@ -63222,7 +63222,7 @@ items:
   previous_names:
   - LinkedIn Conversions API
   website: http://www.segment.com
-  status: PUBLIC_BETA
+  status: PUBLIC
   categories: []
   logo:
     url: https://cdn-devcenter.segment.com/0015b1e2-b3c3-4077-8859-abf25f91b91c.svg
@@ -65818,7 +65818,7 @@ items:
   previous_names:
   - Marketo Static Lists (Actions)
   website: http://www.segment.com
-  status: PUBLIC_BETA
+  status: PUBLIC
   categories: []
   logo:
     url: https://cdn-devcenter.segment.com/baea98c1-5b3c-4b60-99aa-a40f22095f7b.svg

src/_data/catalog/destinations_private.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination data last updated 2024-07-23 
+# destination data last updated 2024-07-25 
 items:
   - id: 54521fd925e721e32a72eee1
     display_name: Pardot

src/_data/catalog/slugs.yml

@@ -225,4 +225,6 @@ destinations:
     override: "actions-xtremepush"
   - original: "metricstory"
     override: "convertly"
+  - original: "amazon-ads-dsp-and-amc"
+    override: "actions-amazon-amc"
 

src/_data/catalog/source_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# source categories last updated 2024-07-23 
+# source categories last updated 2024-07-25 
 items:
   - display_name: A/B Testing
     slug: a-b-testing

src/_data/catalog/sources.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# sources last updated 2024-07-23 
+# sources last updated 2024-07-25 
 items:
   - id: 8HWbgPTt3k
     display_name: .NET
@@ -1205,9 +1205,8 @@ items:
       - us
     source_type: cloud-app
     description: >-
-      This source is in beta! Looker is a business intelligence software
-      platform that helps you explore, analyze and share real-time business
-      insights easily.
+      Looker is a business intelligence software platform that helps you
+      explore, analyze and share real-time business insights easily.
     logo:
       url: https://cdn.filepicker.io/api/file/q8M1ezNVQJiDtZJWoHHn
     categories:

src/_data/products.yml

@@ -186,6 +186,15 @@ items:
 - product_display_name: OAuth 2.0
   slug: oauth-2
   plan-note: "OAuth 2.0 is available to customers on Business tier plans."
+  plans:
+    free: false
+    team: false
+    business: true
+    add-on: false
+
+- product_display_name: Custom Domain
+  slug: custom-domain
+  plan-note: "Custom Domain is available to customers on Business tier plans."
   plans:
     free: false
     team: false

src/_data/sidenav/main.yml

@@ -150,8 +150,10 @@ sections:
       title: Cloud Sources
     - path: /connections/sources/debugger
       title: Source Debugger
-    - path: /connections/sources/custom-domains
-      title: Set Up a Custom Domain Proxy in Segment
+    - path: /connections/sources/custom-domain
+      title: Segment-Managed Custom Domain
+    - path: /connections/sources/catalog/libraries/website/javascript/custom-proxy
+      title: Self-Managed Custom Proxy
     - path: /connections/sources/visual-tagger
       title: Visual Tagger
     - section_title: Schema

src/_data/sidenav/strat.yml

@@ -109,7 +109,7 @@ sections:
   - path: /connections/sources/catalog/libraries/website/javascript/quickstart
     title: Quickstart tutorial
   - path: /connections/sources/catalog/libraries/website/javascript/custom-proxy
-    title: Custom proxy for Analytics.js
+    title: Self-Managed Custom Proxy
   - path: /connections/sources/catalog/libraries/website/javascript/persistence
     title: Client-side persistence in Analytics.js
   - path: /connections/sources/catalog/libraries/website/javascript/single-page-apps

src/_includes/content/domain-delegation-solutions.md

@@ -0,0 +1,11 @@
+## Segment's domain delegation solutions
+
+Segment offers two domain delegation solutions: [Custom Proxy](/docs/connections/sources/catalog/libraries/website/javascript/custom-proxy) and [Custom Domain](/docs/connections/sources/custom-domain). If you use Custom Domain, you can choose to use either DNS delegation or a Cannonical Name (CNAME). Segment recommends using Custom Domain with DNS delegation, which leads to easy setup, maintenance, and monitoring. 
+
+| Service | How it works | Infrastructure management | Availability |
+| ------- | ------------ | ------------------------- | ------------ |
+| Custom Domain with DNS Delegation | A Segment service that allows your website to use your own subdomain to load Analytics.js securely over HTTPS and send event data. It is not limited to Analytics.js and is also compatible with server libraries. It uses a DNS subdomain that you delegate to Segment.<sup>*</sup> | **Segment manages all related infrastructure**, including applying security updates, managing the SSL certificate lifecycle, and monitoring. | Business Tier <br><br> Recommended for reliable data collection. |
+| Custom Domain with CNAME | This approach uses a Canonical Name (CNAME) to map an alias name on your domain name to Analytics.js. It is not limited to Analytics.js and is also compatible with server libraries. | Customers are responsible for maintaining CNAME. | Business Tier <br><br> Not recommended due to evolving and persistent browser privacy measures. |  
+| Custom Proxy | This approach uses a proxy or wrapper where all data is first collected by a proxy on your domain and then forwarded to Segment. | Customers are responsible for maintaining their own proxy infrastructure. | Available to all Segment users. <br><br> Not recommended because it adds a point of failure, but remains an option if Custom Domain with sub-domain delegation is unavailable to you. | 
+
+<sup>*</sup>_If it's not possible for you to delegate subdomains to Segment, you can use a CNAME instead. Segment encourages users to delegate a DNS subdomain rather than use use CNAME aliasing due to the evolving privacy standards in browsers, but CNAME aliasing remains an option for users not interested in using nameservers._

src/connections/aws-privatelink.md

@@ -19,7 +19,7 @@ Before you can configure AWS PrivateLink for Databricks, complete the following
 - Databricks account must be on the [Enterprise pricing tier](https://www.databricks.com/product/pricing/platform-addons){:target="_blank”} and use the [E2 version](https://docs.databricks.com/en/archive/aws/end-of-life-legacy-workspaces.html#e2-architecture){:target="_blank”} of the platform. 
 - Databricks workspace must use a [Customer-managed VPC](https://docs.databricks.com/en/security/network/classic/customer-managed-vpc.html){:target="_blank”} and [Secure cluster connectivity](https://docs.databricks.com/en/security/network/classic/secure-cluster-connectivity.html){:target="_blank”}.
   - Configure your [VPC](https://docs.databricks.com/en/security/network/classic/customer-managed-vpc.html){:target="_blank”} with DNS hostnames and DNS resolution
-  - Configure a [security group](https://docs.databricks.com/en/security/network/classic/customer-managed-vpc.html#security-groups){:target="_blank”} with bidirectional access to 0.0.0/0 and ports 443, 3306, 6666, 2443, and 8443-8451. 
+  - Configure a [security group](https://docs.databricks.com/en/security/network/classic/customer-managed-vpc.html#security-groups){:target="_blank”} with bidirectional access to 0.0.0.0/0 and ports 443, 3306, 6666, 2443, and 8443-8451. 
 
 ### Configure PrivateLink for Databricks
 To configure PrivateLink for Databricks:
@@ -36,16 +36,17 @@ The following Databricks integrations support PrivateLink:
 ### Prerequisites
 Before you can configure AWS PrivateLink for RDS Postgres, complete the following prerequisites in your Databricks workspace:
 - **Set up a Network Load Balancer (NLB) to route traffic to your Postgres database**: Segment recommends creating a NLB that has target group IP address synchronization, using a solution like AWS Lambda. 
+If any updates are made to the Availability Zones (AZs) enabled for your NLB, please let your CSM know so that Segment can update the AZs of your VPC endpoint.
 - **Configure your NLB with one of the following settings**: 
   - Disable the **Enforce inbound rules on PrivateLink traffic** setting
-  - Add an inbound rule that allows traffic belonging from Segment's `us-east-1` PrivateLink/Edge CIDR: `10.248.64.0/18`
+  - If you must enforce inbound rules on PrivateLink traffic, add an inbound rule that allows traffic belonging to Segment's PrivateLink/Edge CIDR: `10.0.0.0/8`
 
 ### Configure PrivateLink for RDS Postgres
 1. Create a Network Load Balancer VPC endpoint service using the instructions in the [Create a service powered by AWS PrivateLink](https://docs.aws.amazon.com/vpc/latest/privatelink/create-endpoint-service.html){:target="_blank”} documentation. 
 2. Reach out to your Customer Success Manager (CSM) for more details about Segment's AWS principal.
 3. Add the Segment AWS principal as an “Allowed Principal” to consume the Network Load Balancer VPC endpoint service you created in step 1.
 4. Reach out to your CSM and provide them with the Service name for the service that you created above. Segment's engineering team provisions a VPC endpoint for the service in the Segment Edge VPC. 
-5. After creating the VPC, Segment provides you with private DNS so you can update the **Host** in your Segment app settings or create a new Postgres integration. <br> The following RDS Postgres integrations support PrivateLink: 
+5. After creating the VPC endpoint, Segment provides you with private DNS so you can update the **Host** in your Segment app settings or create a new Postgres integration. <br> The following RDS Postgres integrations support PrivateLink: 
   - [RDS Postgres storage destination](/docs/connections/storage/catalog/postgres/)
   - [RDS Postgres Reverse ETL source](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/postgres-setup/)
 
@@ -59,7 +60,7 @@ Before you can configure AWS PrivateLink for RDS Postgres, complete the followin
 ### Configure PrivateLink for Redshift
 Implement Segment's PrivateLink integration by taking the following steps:
 1. Let your Customer Success Manager (CSM) know that you're interested in PrivateLink. They will share information with you about Segment’s Edge account and VPC.
-2. After you receive the Edge account and VPC, [grant cluster access to Segment's Edge account and VPC](https://docs.aws.amazon.com/redshift/latest/gsg/rs-gsg-connect-to-cluster.html){:target="_blank”}.
+2. After you receive the Edge account ID and VPC ID, [grant cluster access to Segment's Edge account and VPC](https://docs.aws.amazon.com/redshift/latest/gsg/rs-gsg-connect-to-cluster.html){:target="_blank”}.
 3. Reach back out to your CSM and provide them with the Cluster identifier for your cluster and your AWS account ID. 
 4. Segment creates a Redshift managed VPC endpoint within the Segment Redshift subnet on your behalf, which creates a PrivateLink Endpoint URL. Segment then provides you with the internal PrivateLink Endpoint URL. 
 5. After Segment provides you with the URL, use it to update or create new Redshift integrations. The following integrations support PrivateLink: 

src/connections/destinations/catalog/actions-amazon-amc/index.md

@@ -0,0 +1,49 @@
+---
+title: Amazon Ads DSP and AMC Destination
+id: 66543798b2fb3cb3e9ff992c
+beta: true
+---
+
+{% include content/plan-grid.md name="actions" %}
+
+[Amazon Ads](https://advertising.amazon.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank”} can help you achieve your marketing goals, whether that's building brand awareness, driving sales, or increasing customer loyalty. 
+
+The Segment - Amazon Ads DSP and AMC integration allows users to connect their Engage Audiences to Amazon Ads to run ads based on certain attributes & audiences defined in Segment, like the people who have visited your site.
+
+This destination is maintained by Segment. For any issues with the destination, [contact the Segment Support team](mailto:friends@segment.com).
+
+## Getting started
+
+### Add the destination to your Engage Space. 
+
+1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank”} search for "Amazon Ads DSP and AMC".
+2. Select Amazon Ads DSP and AMC and click **Add Destination**.
+3. Select the **Engage Space** you'd like to add the destination to.
+4. Once added, view and input the settings you'd need to complete to configure the destination. 
+  - **Connection**: Click **Connect to Amazon Ads DSP and AMC** to authenticate your destination with Amazon.
+  - **Region**: Select the Amazon Region to deliver data to: NA, EU, or FE.
+  - **Enable the destination**: Switch the toggle to on to enable your destination. 
+
+### Connect your Engage Audience(s) to the destination
+
+1. Navigate to the desired Audience in Engage, and select **Add Destination**.
+2. Select the **Amazon Ads DSP and AMC** destination you just created.
+4. After adding your destination to the Engage audience, click on the destination from the audience page to view and complete the [audience-specific settings](https://advertising.amazon.com/API/docs/en-us/amc-advertiser-audience#tag/Audience-Metadata){:target="_blank"}. 
+  - **Advertiser ID**:
+  - [**Country Code**](https://advertising.amazon.com/API/docs/en-us/guides/amazon-marketing-cloud/audiences/audience-management-service#country-code){:target="_blank"}: A 2-character string in the ISO 3166 format that will be applied for all records within the audience.
+  - (Optional) **CPM Cents**: Cost per thousand impressions (CPM), in cents. For example, $1.00 = 100 cents.
+  - (Optional) **Currency**:
+  - **Description**: The audience description. Must be an alphanumeric, non-null string between 0 to 1000 characters in length.
+  - **External Audience ID**: The user-defined audience identifier. This should be a unique, user-defined audience identifier (For example., "audience-id-for-device").
+  - **TTL**: Time-to-live, in seconds. The amount of time the record is associated with the audience. Values allowed are 0 .. 34300800 (For example, 2592000 for 30 days, 34300800 for 397 days). 
+
+### Configure your mappings
+
+1. Click on the destination from the audience page, and navigate to **Matching Mappings** from the destination side view.
+2. Click **Add mapping**.
+3. Configure the mapping fields.
+4. Save and enable the mapping.
+5. When Segment computes the audience, you can see the created audience and records delivered to Amazon.
+
+{% include components/actions-fields.html %}
+

src/connections/destinations/catalog/actions-display-video-360/index.md

@@ -3,7 +3,6 @@ title: Display and Video 360 (Actions) Destination
 strat: google
 hide-settings: true
 id: 65302a3acb309a8a3d5593f2
-beta: true
 engage: true
 ---
 

src/connections/destinations/catalog/actions-google-analytics-4-web/index.md

@@ -207,3 +207,7 @@ Yes. In the Set Configuration Mapping, click Show All Fields and scroll to Send
 ### Differences between the Google Analytics 4 Cloud and Google Analytics 4 Web destinations 
 
 Segment's [Google Analytics 4 Cloud](/docs/connections/destinations/catalog/actions-google-analytics-4/) server-side destination uses Google's Measurement Protocol API to send event data server to server, whereas Segment's [Google Analytics 4 Web](/docs/connections/destinations/catalog/actions-google-analytics-4-web/) device-mode destination loads the gtag.js library client-side and uses Segment's event data to map to gtag.js events directly. Each destination has its own advantages and disadvantages. Your choice between the two depends on your specific use case, technical expertise, and the platforms from which you want to track data.
+
+### User-provided data collection
+
+Google has introduced a beta feature for collecting data provided by users, [User-provided data collection](https://support.google.com/analytics/answer/14077171?hl=en&utm_id=ad){:target="_blank"}. Note that this feature is currently not supported by Segment, and, acknowledging this feature policy in your Google Analytics 4 Account has irreversible effects.

src/connections/destinations/catalog/actions-linkedin-conversions/index.md

@@ -1,7 +1,6 @@
 ---
 title: LinkedIn Conversions API Destination
 id: 652e765dbea0a2319209d193
-beta: true
 ---
 
 The LinkedIn Conversions API (CAPI) is a conversion tracking tool that creates a direct connection between marketing data from an advertiser’s server and LinkedIn. This integration enables advertisers to measure the performance of their LinkedIn marketing campaigns no matter where the conversion happens and use this data to power campaign optimization. The Conversions API can help strengthen performance and decrease cost per action with more complete attribution, improved reliability, and optimized delivery.