Release 22.20.2 (#2927)

* Update index.md (#2920)

add missing "title" header

* Session Id and Session Number using gtag

* Update index.md

* Update index.md

* Update index.md

* Fix Intercom connection modes (#2923)

* Fix Intercom connection modes

* Update src/connections/destinations/catalog/intercom/index.md

Co-authored-by: stayseesong <[email protected]>

Co-authored-by: stayseesong <[email protected]>

* Bump nokogiri from 1.13.4 to 1.13.6 (#2924)

Bumps [nokogiri](https://github.com/sparklemotion/nokogiri) from 1.13.4 to 1.13.6.
- [Release notes](https://github.com/sparklemotion/nokogiri/releases)
- [Changelog](https://github.com/sparklemotion/nokogiri/blob/main/CHANGELOG.md)
- [Commits](sparklemotion/nokogiri@v1.13.4...v1.13.6)

---
updated-dependencies:
- dependency-name: nokogiri
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Update documentation about testing (#2917)

* Update documentation about testing

* Update src/connections/sources/catalog/libraries/server/python/index.md

Co-authored-by: markzegarelli <[email protected]>

Co-authored-by: markzegarelli <[email protected]>

* Apply suggestions from code review

* fixes

Co-authored-by: Segment Docs Robot <[email protected]>
Co-authored-by: Thomas Gilbert <[email protected]>
Co-authored-by: Gavin-Fitzpatrick <[email protected]>
Co-authored-by: stayseesong <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: g-normand <[email protected]>
Co-authored-by: stayseesong <[email protected]>

Author: 7 people

Gemfile.lock

@@ -104,12 +104,12 @@ GEM
     mercenary (0.4.0)
     mini_portile2 (2.8.0)
     multipart-post (2.1.1)
-    nokogiri (1.13.4)
+    nokogiri (1.13.6)
       mini_portile2 (~> 2.8.0)
       racc (~> 1.4)
-    nokogiri (1.13.4-x86_64-darwin)
+    nokogiri (1.13.6-x86_64-darwin)
       racc (~> 1.4)
-    nokogiri (1.13.4-x86_64-linux)
+    nokogiri (1.13.6-x86_64-linux)
       racc (~> 1.4)
     pathutil (0.16.2)
       forwardable-extended (~> 2.6)

src/_data/catalog/overrides.yml

@@ -51,7 +51,7 @@ items:
   connection_modes:
     device:
       web: true
-      mobile: false
+      mobile: true
       server: false
     cloud:
       web: false

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

@@ -81,6 +81,22 @@ The Google Analytics 4 reports only display active users who engage with your si
 
 If you choose to integrate with Google Analytics 4 client-side (using Gtag outside of Segment) _and_ also use Segment's Google Analytics 4 destination to send events through the API, you can track sessions server-side. When using Gtag, [Google generates a `session_id` and `session_number` when a session begins](https://support.google.com/analytics/answer/9191807?hl=en){:target='_blank'}. The `session_id` and `session_number` generated on the client can be passed as Event Parameters to stitch events sent through the API with the same session that was collected client-side.
 
+You can double-check your session_id and session_number with the [Google Site Tag function](https://developers.google.com/tag-platform/gtagjs/reference){:target='_blank'} or by running this script in your JavaScript console and replacing `G-xxxxxxxxxx` with your GA4 measurement ID:
+
+```java
+const sessionIdPromise = new Promise(resolve => {
+  gtag('get', 'G-xxxxxxxxxx', 'session_id', resolve)
+});
+const sessionNumPromise = new Promise(resolve => {
+  gtag('get', 'G-xxxxxxxxxx', 'session_number', resolve)
+});
+
+Promise.all([sessionIdPromise, sessionNumPromise]).then(function(session_data) {
+  console.log("session ID: "+session_data[0]);
+  console.log("session Number: "+session_data[1]);
+});
+```
+
 > info "Session tracking limitations"
 > Session tracking server-side only works if you're also sending data to Google Analytics 4 client-side. This is because the `session_id` must match a value that was previously collected on the client. For events to stitch properly, they must arrive within a 48 hour window of when the client-side events arrived.
 >

src/connections/destinations/catalog/blitzllama/index.md

@@ -1,5 +1,5 @@
 ---
-Blitzllama
+title: Blitzllama
 rewrite: true
 id: 616d3b0494950977f91f81a4
 ---
@@ -47,4 +47,4 @@ analytics.group("0e8c78ea9d97a7b8185e8632", {
 });
 ```
 
-Segment sends Groups calls to Blitzllama as a `group` event.
+Segment sends Groups calls to Blitzllama as a `group` event.

src/connections/destinations/catalog/intercom/index.md

@@ -9,36 +9,14 @@ id: 54521fd725e721e32a72eec6
 
 ## Getting Started
 
-The first step is to make sure Intercom supports the source type and connection mode you've chosen to implement. You can learn more about what dictates [the connection modes we support here](/docs/connections/destinations/#connection-modes).
-
-<table>
-  <tr>
-    <th></th>
-    <th>Web</th>
-    <th>Mobile</th>
-    <th>Server</th>
-  </tr>
-  <tr>
-    <td>📱 Device-based</td>
-    <td> ✅ </td>
-    <td> ✅ </td>
-    <td></td>
-  </tr>
-  <tr>
-    <td>☁️  Cloud-based</td>
-    <td></td>
-    <td> ✅ </td>
-    <td> ✅ </td>
-  </tr>
-</table>
 
 1.  From your Segment UI's Destinations page click **Add Destination**.
 2.  Search for "Intercom" and select it in the results that appear.
 3.  Choose which Source to connect Intercom to.
-3.  Authorize your Intercom account in Segment and select the Intercom Account to sync with Segment.
+4.  Authorize your Intercom account in Segment and select the Intercom Account to sync with Segment.
 
     You can choose which account to sync from the drop down menu in the top right. If you are using [server-side sources](/docs/connections/sources#server), Segment starts passing data through once you activate the Destination. For other libraries  continue reading below.
-4. Find your "App ID" in the Intercom UI following [the instructions here](https://docs.intercom.com/faqs-and-troubleshooting/getting-set-up/where-can-i-find-my-app-id) or by navigating to the Gear Menu and clicking on "App Settings" followed by "API Keys". It should look something like `9iefb489`.
+5. Find your "App ID" in the Intercom UI following [the instructions here](https://docs.intercom.com/faqs-and-troubleshooting/getting-set-up/where-can-i-find-my-app-id){:target="_blank"} or by navigating to the Gear Menu and clicking on "App Settings" followed by "API Keys". It should look something like `9iefb489`.
 
 
 Your changes appear in the Segment CDN in about 45 minutes, and then Analytics.js starts asynchronously loading Intercom's `library.js` onto your page.

src/connections/sources/catalog/libraries/server/python/index.md

@@ -45,6 +45,12 @@ analytics.debug = True
 analytics.on_error = on_error
 ```
 
+If you don't want to send information to Segment during testing, add the following code to your test:
+
+```python
+analytics.send = False
+```
+
 **Using Django?** Check out the [Django docs](/docs/connections/sources/catalog/libraries/server/python/#django).
 
 ## Identify