Merge pull request #2380 from segmentio/develop

Release 22.3.2

Author: pwseg

src/_data/catalog/overrides.yml

@@ -1,6 +1,16 @@
 # This file is manually generated. When you add or remove an item, add or remove
 # it from the `overrides-list.yml` too.
 items:
+- slug: doubleclick-floodlight
+  connection_modes:
+    device:
+      web: true
+      mobile: false
+      server: false
+    cloud:
+      web: false
+      mobile: true
+      server: true
 - slug: intercom
   connection_modes:
     device:

src/_includes/content/connection-modes.md

@@ -1,12 +1,17 @@
 <!-- in the file we're pulling from the API, "name" corresponds with the path to the yml blob for a specific destination.-->
 {% assign currentSlug = page.url | split: "/" | last %}
-{% if page.cmode-override %}
-{% assign currentIntegration = site.data.catalog.overrides.items | where: "slug", currentSlug | first %}
-{% else %}
+{% assign overrideInfo = site.data.catalog.overrides.items % | where: "slug", currentSlug | first %}
+
+
+
 {% assign currentIntegration = site.data.catalog.destinations.items | where: "slug", currentSlug | first %}
-{% endif %}
 
+
+{% if page.cmode-override %}
+{% assign connectionModes = overrideInfo.connection_modes %}
+{% else %}
 {% assign connectionModes = currentIntegration.connection_modes %}
+{% endif %}
 
 {% if currentIntegration.components.size > 0 %}
 <!--don't show a blank table if we can't find any info about these. -->

src/_includes/content/syntax-note.md

@@ -0,0 +1 @@
+<div class="premonition info"><div class="fa fa-info-circle"></div> <p markdown=1>Based on the library you use, the syntax in the examples might be different. You can find library-specific documentation on the [Sources Overview](/docs/connections/sources/) page.</p></div>

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

@@ -10,8 +10,7 @@ In addition to the docs below, please reference the [BytePlus integration guide]
 
 This destination is maintained by BytePlus. For any issues with the destination, please [contact the BytePlus Support team](mailto:support@byteplus.com)
 
-Getting Started
-
+## Getting Started
 
 {% include content/connection-modes.md %}
 
@@ -24,7 +23,7 @@ Getting Started
 6. Enter the "API Key" in the "BytePlus" destination settings in Segment.
 
 
-Page
+## Page
 
 If you aren’t familiar with the Segment Spec, take a look at the Page method documentation (https://segment.com/docs/connections/spec/page/) to learn about what it does. An example call would look like:
 
@@ -36,7 +35,7 @@ analytics.page()
 
 Segment sends Page calls to BytePlus as a `page` event.
 
-Screen
+## Screen
 
 If you aren’t familiar with the Segment Spec, take a look at the [Screen method documentation](https://segment.com/docs/connections/spec/screen/) to learn about what it does. An example call would look like:
 ```obj-c
@@ -45,7 +44,7 @@ If you aren’t familiar with the Segment Spec, take a look at the [Screen metho
 
 Segment sends Screen calls to BytePlus as a`screen`event.
 
-Identify
+## Identify
 
 If you aren’t familiar with the Segment Spec, take a look at the [Identify method documentation](https://segment.com/docs/connections/spec/identify/) to learn about what it does. An example call would look like:
 
@@ -56,7 +55,7 @@ analytics.identify('userId123', {
 ```
 Segment sends Identify calls to BytePlus as an `identify `event with `SSID`.
 
-Track
+## Track
 
 If you aren’t familiar with the Segment Spec, take a look at the [Track method documentation](https://segment.com/docs/connections/spec/track/) to learn about what it does. An example call would look like:
 ```js

src/connections/destinations/catalog/doubleclick-floodlight/index.md

@@ -1,6 +1,7 @@
 ---
 title: DoubleClick Floodlight Destination
 strat: google
+cmode-override: true 
 ---
 
 The [DoubleClick Floodlight](https://support.google.com/searchads/answer/7298761?hl=en) destination allows you to make calls directly to Floodlight based on your mapped events. All you have to do is enter your **DoubleClick Advertiser ID** in the Doubleclick Floodlight destinations settings in the Segment App, then map the Segment `track` events to their corresponding Floodlight tags.

src/connections/spec/alias.md

@@ -32,6 +32,7 @@ Here's the corresponding Javascript event that would generate the above payload.
 ```js
 analytics.alias("507f191e81");
 ```
+{% include content/syntax-note.md %}
 
 Beyond the common fields, the `alias` call takes the following fields:
 

src/connections/spec/group.md

@@ -35,6 +35,7 @@ analytics.group("0e8c78ea9d97a7b8185e8632", {
   "total billed": 830
 });
 ```
+{% include content/syntax-note.md %}
 
 Beyond the common fields, the `group` call takes the following fields:
 

src/connections/spec/identify.md

@@ -48,6 +48,7 @@ analytics.identify("97980cfea0067", {
   logins: 5
 });
 ```
+{% include content/syntax-note.md %}
 
 Beyond the common fields, an `identify` call has the following fields:
 

src/connections/spec/page.md

@@ -26,6 +26,7 @@ And here's the corresponding JavaScript event that would generate the above payl
 ```js
 analytics.page("Retail Page","Home");
 ```
+{% include content/syntax-note.md %}
 
 Beyond the common fields, the `page` call takes the following fields:
 

src/connections/spec/screen.md

@@ -24,6 +24,7 @@ And here's the corresponding Objective-C event that would generate the above pay
 [[SEGAnalytics sharedAnalytics] screen:@"Home"
                             properties:@{ @"Feed Type": @"private" }];
 ```
+{% include content/syntax-note.md %}
 
 Beyond the common fields, the `screen` call takes the following fields: