From 164a0c7e7a95c70a9364fd0cc16d4ad1616d5cc8 Mon Sep 17 00:00:00 2001 From: rchinn-segment <93161299+rchinn-segment@users.noreply.github.com> Date: Thu, 13 Jan 2022 12:39:44 -0800 Subject: [PATCH 1/6] Identify-call-NodeJS-2327 --- src/connections/spec/identify.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/connections/spec/identify.md b/src/connections/spec/identify.md index 91c2113483..b65a80e697 100644 --- a/src/connections/spec/identify.md +++ b/src/connections/spec/identify.md @@ -48,6 +48,8 @@ analytics.identify("97980cfea0067", { logins: 5 }); ``` +> note "" +> The `identify` call syntax is different for Node.js. Please visit Segment's [Analytics for Node.js](/docs/connections/sources/catalog/libraries/server/node/#identify) page for more information. Beyond the common fields, an `identify` call has the following fields: From a47e837824b6ae04efbccb230e7e8cfc26e263ae Mon Sep 17 00:00:00 2001 From: rchinn-segment <93161299+rchinn-segment@users.noreply.github.com> Date: Tue, 18 Jan 2022 09:21:29 -0800 Subject: [PATCH 2/6] Update src/connections/spec/identify.md Co-authored-by: stayseesong <83784848+stayseesong@users.noreply.github.com> --- src/connections/spec/identify.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/spec/identify.md b/src/connections/spec/identify.md index b65a80e697..a49f87d726 100644 --- a/src/connections/spec/identify.md +++ b/src/connections/spec/identify.md @@ -49,7 +49,7 @@ analytics.identify("97980cfea0067", { }); ``` > note "" -> The `identify` call syntax is different for Node.js. Please visit Segment's [Analytics for Node.js](/docs/connections/sources/catalog/libraries/server/node/#identify) page for more information. +> The `identify` call syntax is different for Node.js. See the docs for [Analytics for Node.js](/docs/connections/sources/catalog/libraries/server/node/#identify) for more information. Beyond the common fields, an `identify` call has the following fields: From 3a7fdc7945f8b9b8202f14eb9303fd633b3ace3b Mon Sep 17 00:00:00 2001 From: Thomas Gilbert <64277654+tcgilbert@users.noreply.github.com> Date: Tue, 18 Jan 2022 15:55:50 -0500 Subject: [PATCH 3/6] [index.md] updated markdown headings for documentation (#2374) --- .../destinations/catalog/datarangers/index.md | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/src/connections/destinations/catalog/datarangers/index.md b/src/connections/destinations/catalog/datarangers/index.md index 1ac4dba44d..33925f1047 100644 --- a/src/connections/destinations/catalog/datarangers/index.md +++ b/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 From f48f043b689baa2e1df472a56469d0223c05ca94 Mon Sep 17 00:00:00 2001 From: rchinn-segment <93161299+rchinn-segment@users.noreply.github.com> Date: Wed, 19 Jan 2022 15:22:31 -0800 Subject: [PATCH 4/6] Updates to the syntax note --- src/_includes/content/syntax-note.md | 1 + src/connections/spec/alias.md | 1 + src/connections/spec/group.md | 1 + src/connections/spec/identify.md | 3 +-- src/connections/spec/page.md | 1 + src/connections/spec/screen.md | 1 + src/connections/spec/track.md | 1 + 7 files changed, 7 insertions(+), 2 deletions(-) create mode 100644 src/_includes/content/syntax-note.md diff --git a/src/_includes/content/syntax-note.md b/src/_includes/content/syntax-note.md new file mode 100644 index 0000000000..511d6aeafd --- /dev/null +++ b/src/_includes/content/syntax-note.md @@ -0,0 +1 @@ +

Based on the library you use, the syntax in the examples might be different. You can find library-specific documentation from the [Sources Overview](/docs/connections/sources/) page.

diff --git a/src/connections/spec/alias.md b/src/connections/spec/alias.md index 9bca810ada..bc38dc3556 100644 --- a/src/connections/spec/alias.md +++ b/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: diff --git a/src/connections/spec/group.md b/src/connections/spec/group.md index bc58812682..cc33d26f69 100644 --- a/src/connections/spec/group.md +++ b/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: diff --git a/src/connections/spec/identify.md b/src/connections/spec/identify.md index a49f87d726..24678f39dd 100644 --- a/src/connections/spec/identify.md +++ b/src/connections/spec/identify.md @@ -48,8 +48,7 @@ analytics.identify("97980cfea0067", { logins: 5 }); ``` -> note "" -> The `identify` call syntax is different for Node.js. See the docs for [Analytics for Node.js](/docs/connections/sources/catalog/libraries/server/node/#identify) for more information. +{% include content/syntax-note.md %} Beyond the common fields, an `identify` call has the following fields: diff --git a/src/connections/spec/page.md b/src/connections/spec/page.md index fdf324e54b..bb2b22ebd1 100644 --- a/src/connections/spec/page.md +++ b/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: diff --git a/src/connections/spec/screen.md b/src/connections/spec/screen.md index 14a39f802f..2371eacc2c 100644 --- a/src/connections/spec/screen.md +++ b/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: diff --git a/src/connections/spec/track.md b/src/connections/spec/track.md index 307a961563..7501d6b185 100644 --- a/src/connections/spec/track.md +++ b/src/connections/spec/track.md @@ -29,6 +29,7 @@ analytics.track("User Registered", { accountType: "Facebook" }); ``` +{% include content/syntax-note.md %} Beyond the common fields, the `track` call has the following fields: From edfee657079a9b9adeecb688a15b5f2c8ad55706 Mon Sep 17 00:00:00 2001 From: rchinn-segment <93161299+rchinn-segment@users.noreply.github.com> Date: Wed, 19 Jan 2022 16:02:16 -0800 Subject: [PATCH 5/6] Update src/_includes/content/syntax-note.md Co-authored-by: markzegarelli --- src/_includes/content/syntax-note.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/_includes/content/syntax-note.md b/src/_includes/content/syntax-note.md index 511d6aeafd..c75b1033d6 100644 --- a/src/_includes/content/syntax-note.md +++ b/src/_includes/content/syntax-note.md @@ -1 +1 @@ -

Based on the library you use, the syntax in the examples might be different. You can find library-specific documentation from the [Sources Overview](/docs/connections/sources/) page.

+

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.

From 07d64e67d0e4ab6533cf96b69b8390e9e1ac2cdd Mon Sep 17 00:00:00 2001 From: markzegarelli Date: Thu, 20 Jan 2022 09:07:14 -0800 Subject: [PATCH 6/6] Update connection mode overrides (#2350) --- src/_data/catalog/overrides.yml | 10 ++++++++++ src/_includes/content/connection-modes.md | 13 +++++++++---- .../catalog/doubleclick-floodlight/index.md | 1 + 3 files changed, 20 insertions(+), 4 deletions(-) diff --git a/src/_data/catalog/overrides.yml b/src/_data/catalog/overrides.yml index 8749dae38b..9960604029 100644 --- a/src/_data/catalog/overrides.yml +++ b/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: diff --git a/src/_includes/content/connection-modes.md b/src/_includes/content/connection-modes.md index 3ca229d39f..2b4637d05d 100644 --- a/src/_includes/content/connection-modes.md +++ b/src/_includes/content/connection-modes.md @@ -1,12 +1,17 @@ {% 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 %} diff --git a/src/connections/destinations/catalog/doubleclick-floodlight/index.md b/src/connections/destinations/catalog/doubleclick-floodlight/index.md index 1bc9500b1a..481dd2ef58 100644 --- a/src/connections/destinations/catalog/doubleclick-floodlight/index.md +++ b/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.