Merge remote-tracking branch 'upstream/develop' into develop

Author: lopenchi

.github/workflows/new-files-report.yml

@@ -0,0 +1,58 @@
+name: New Files Report
+on:
+  schedule:
+    - cron: '0 16 * * 5'  # This will run automatically every Friday at noon Eastern 
+  workflow_dispatch:  # We can also trigger it manually from the Actions tab
+
+jobs:
+  report:
+    if: github.repository == 'segmentio/segment-docs'
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+      contents: read
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      
+      - name: Generate report
+        id: report
+        run: |
+          echo "## New files since July 20th, 2025" > report.md
+          echo "" >> report.md
+          
+          FILES=$(git log --since="2025-07-20" --diff-filter=A --name-only --pretty=format:"" -- src/ 2>/dev/null | grep -v '^$' | sort -u || echo "")
+          
+          if [ -z "$FILES" ]; then
+            echo "No new files found." >> report.md
+          else
+            echo "$FILES" | while read file; do
+              if [ -n "$file" ]; then
+                COMMIT=$(git log --diff-filter=A --format="%h" -- "$file" | head -1)
+                DATE=$(git log --diff-filter=A --format="%ad" --date=short -- "$file" | head -1)
+                MSG=$(git log --diff-filter=A --format="%s" -- "$file" | head -1)
+                echo "- **$DATE**: \`$file\` - $MSG ([${COMMIT}](../../commit/${COMMIT}))" >> report.md
+              fi
+            done
+          fi
+          
+          echo "" >> report.md
+          echo "_Report generated on $(date +'%Y-%m-%d %H:%M UTC')_" >> report.md
+      
+      - name: Create issue
+        uses: actions/github-script@v7
+        with:
+          script: |
+            const fs = require('fs');
+            const report = fs.readFileSync('report.md', 'utf8');
+            const today = new Date().toISOString().split('T')[0];
+            
+            github.rest.issues.create({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              title: `New files report - ${today}`,
+              body: report,
+              labels: ['migration'],
+              assignees: ['pwseg']
+            });

src/_includes/content/beta-note.md

@@ -1 +1,7 @@
-<div class="premonition info"><div class="fa fa-info-circle"></div><div class="content"><p class="header">This document is about a {{ page.integration_type }} which is in beta</p><p markdown=1>This means that the {{ page.title }} is in active development, and some functionality may change before it becomes generally available.</p></div></div>
+<div class="premonition info">
+  <div class="fa fa-info-circle"></div>
+  <div class="content">
+    <p class="header">This document is about a {{ page.integration_type }} which is in beta</p>
+    <p markdown=1>This means that the {{ page.title }} is in active development, and some functionality may change before it becomes generally available.</p>
+  </div>
+</div>

src/_includes/content/tracking-api-limit.md

@@ -1,4 +1,3 @@
-<div class="premonition warning"><div class="fa fa-exclamation-circle"></div><div class="content"><p class="header">HTTP Tracking API limits</p><p>Segment's HTTP Tracking API accepts batch requests up to <strong>500KB</strong>. To avoid errors in event creation, ensure that individual event payload sizes remain below <strong>32KB</strong>.</p>
-
-
-</div></div>
+> warning "HTTP Tracking API limits"
+>
+> Segment's HTTP Tracking API accepts batch requests up to **500 KB**. To avoid errors in event creation, ensure that individual event payload sizes remain below **32 KB**.

src/api/config-api/tutorial-javascript-google-analytics.md

@@ -33,8 +33,8 @@ See the [Authentication](/docs/api/config-api/authentication/) doc for more info
 
 To set up Segment Protocols through the API you first need to create a personal access token with **full access** to your workspace through the `workspace` scope.
 
-> success ""
-> **Tip**: As best practice, tokens should be assigned the least permissions needed to perform a required API action, however for simplicity in this demo, we'll select Workspace Owner. You may want to delete the token once you've finished this demo.
+> info "Tip"
+> As best practice, tokens should be assigned the least permissions needed to perform a required API action, however for simplicity in this demo, we'll select Workspace Owner. You may want to delete the token once you've finished this demo.
 
 1. Log in to your Segment workspace.
 2. Click **Settings** in the left navigation bar.

src/connections/destinations/catalog/actions-absmartly/index.md

@@ -166,5 +166,3 @@ analytics.ready(function() {
 
 To migrate from the classic ABsmartly destination to ABsmartly (Actions), disconnect the classic ABsmartly destination before enabling the ABsmartly (Actions) destination to avoid duplicate experimentation events.
 
----
-

src/connections/destinations/catalog/actions-google-campaign-manager/index.md

@@ -66,4 +66,3 @@ Track non-monetary conversion data such as unique users, conversions, and sessio
 - **uVariables**: Custom Floodlight variables.
 - **dcCustomParams**: Custom data for event snippets.
 
----

src/connections/destinations/catalog/actions-nudge/index.md

@@ -46,8 +46,6 @@ How Nudge handles Identify calls:
 * If `userId` already exists, Nudge merges or overwrites profile properties with the latest values.
 * Identify calls without `userId`, or with only `anonymousId`, are dropped.
 
----
-
 ### Track
 
 The Track method sends custom events and their properties into Nudge. You must include `event` name in every Track call so events can be associated with the correct user. See Segment's Spec for Track for any reference: [Track Spec](/docs/connections/spec/track/)

src/connections/destinations/catalog/actions-stackadapt-audiences/index.md

@@ -50,9 +50,7 @@ Each Engage audience should only contain profiles that have a valid email addres
    - Add traits as needed. Note that you should set up corresponding mappings for the fields in step 9 for the traits selected here if you want them to be imported.
 5. Click **Save**.
 6. Click on the **StackAdapt Audience** destination under the **Destinations** section.
-7. Under the **Matching Mappings** tab, click **Add mapping**.
-   - To reuse your Segment audience on the StackAdapt platform, select **Sync Audience**.
-   - To import profiles to the StackAdapt platform, select **Forward Profile**.
+7. Under the **Matching Mappings** tab, click **Add mapping** and then select **Sync Audience**.
    - **Note**: You don't have to set up both mappings. The mappings will be shared across all audiences that have sync enabled to this destination. You should create a new destination if you wish to use different mappings for different audiences.
 8. Define the event trigger: Ensure the Event Type is `Track` or `Identify`.
 9. Map fields:

src/connections/destinations/catalog/actions-tiktok-offline-conversions/index.md

@@ -51,5 +51,3 @@ TikTok Offline Events API requires at least one type of PII (email addresses and
 - iOS compliance checks will be performed on PII (ATT opt-out users will still be reported and attributed).
 - TikTok will pruge unmatched offline conversions IDs/records.
 
-
----

src/connections/destinations/catalog/adobe-analytics/mobile.md

@@ -17,8 +17,8 @@ Before you start sending data from your mobile application to Adobe Analytics, y
 - Download these settings as the `ADBMobileConfig.json` file by clicking the **Config JSON** link at the bottom of the same tab. Follow the instructions in Adobe's [Configuration documentation](https://developer.adobe.com/client-sdks/home/base/mobile-core/configuration/){:target="_blank”}.
 - Finally, follow the instructions below for each mobile environment to bundle Segment's Adobe Analytics SDK in your project.
 
-> success ""
-> **Tip**: Mobile implementations use the `ADBMobileConfig.json` file to store the settings that you would otherwise enter in the Adobe Analytics destination settings in the Segment app. You can change these settings from the Manage App Settings tab in your Adobe Mobile Services dashboard, and can download the file from that same tab. This file includes the Report Suite ID, Timestamp Option, Tracking Server Secure URL, Tracking Server URL, and Use Secure URL for Server-side settings.
+> info "Tip"
+> Mobile implementations use the `ADBMobileConfig.json` file to store the settings that you would otherwise enter in the Adobe Analytics destination settings in the Segment app. You can change these settings from the Manage App Settings tab in your Adobe Mobile Services dashboard, and can download the file from that same tab. This file includes the Report Suite ID, Timestamp Option, Tracking Server Secure URL, Tracking Server URL, and Use Secure URL for Server-side settings.
 
 #### For Android