From 65cb8ebc87d86c6b4759cc4355dc8230e4ddb800 Mon Sep 17 00:00:00 2001 From: stayseesong Date: Fri, 17 Jun 2022 12:43:54 -0700 Subject: [PATCH 01/22] updates to braze [issue 2934] --- .../destinations/catalog/braze-cloud-mode-actions/index.md | 3 ++- .../catalog/braze-web-device-mode-actions/index.md | 5 ++++- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/src/connections/destinations/catalog/braze-cloud-mode-actions/index.md b/src/connections/destinations/catalog/braze-cloud-mode-actions/index.md index 43f84469f7..98f54a2945 100644 --- a/src/connections/destinations/catalog/braze-cloud-mode-actions/index.md +++ b/src/connections/destinations/catalog/braze-cloud-mode-actions/index.md @@ -28,6 +28,8 @@ Braze Cloud Mode (Actions) provides the following benefit over Braze Classic: - **App ID**: The app identifier used to reference specific Apps in requests made to the Braze API. Created under Developer Console in the Braze Dashboard. - **REST Endpoint**: Your Braze REST Endpoint. For more information, see [API Overview](https://www.braze.com/docs/api/basics/){:target="_blank"} in the Braze documentation. +> info "" +> Braze requires that you include a `userId` or `braze_id` for all calls made in cloud-mode. Segment sends a `braze_id` if the `userId` is missing. When you use a device-mode connection, Braze automatically tracks anonymous activity using the `braze_id` if a `userId` is missing. {% include components/actions-fields.html settings="true"%} @@ -40,4 +42,3 @@ Braze Cloud Mode (Actions) provides the following benefit over Braze Classic: Keep the following in mind if you plan to move to Braze (Actions) from the classic Braze destination. {% include components/actions-map-table.html name="braze-cloud" %} - diff --git a/src/connections/destinations/catalog/braze-web-device-mode-actions/index.md b/src/connections/destinations/catalog/braze-web-device-mode-actions/index.md index 24ad431435..d954617b14 100644 --- a/src/connections/destinations/catalog/braze-web-device-mode-actions/index.md +++ b/src/connections/destinations/catalog/braze-web-device-mode-actions/index.md @@ -28,6 +28,10 @@ Braze Web Mode (Actions) provides the following benefits over Braze Classic: 2. Search for "Braze" in the Catalog, select **Braze Web Mode (Actions)**, and choose which of your sources to connect the destination to. 3. Configure the Connection Settings. **API Key** and **SDK Endpoint** are required settings. +> info "" +> If you're using a device-mode connection, Braze's SDK assigns a `device_id` and a backend identifier, `braze_id`, to every user. This allows Braze to capture anonymous activity from the device by matching on those identifiers instead of `userId`. This applies to _device-mode connections_. + + {% include components/actions-fields.html settings="true"%} {% include components/actions-fields.html%} @@ -170,4 +174,3 @@ For more details on this snippet, see Braze's documentation [here](https://www.b Keep the following in mind if you plan to move to Braze (Actions) from the classic Braze destination. {% include components/actions-map-table.html name="braze-web" %} - From 6630dddd0afbb25375cba11a32aab0c1761f57eb Mon Sep 17 00:00:00 2001 From: Thomas Gilbert Date: Thu, 23 Jun 2022 14:16:47 -0400 Subject: [PATCH 02/22] add matcha destination documentation --- .../destinations/catalog/matcha/index.md | 67 +++++++++++++++++++ 1 file changed, 67 insertions(+) create mode 100644 src/connections/destinations/catalog/matcha/index.md diff --git a/src/connections/destinations/catalog/matcha/index.md b/src/connections/destinations/catalog/matcha/index.md new file mode 100644 index 0000000000..96fd7b3d7c --- /dev/null +++ b/src/connections/destinations/catalog/matcha/index.md @@ -0,0 +1,67 @@ +--- +title: Matcha Destination +id: 6286930129cf5f85d889854f +--- + +[Matcha](https://www.matcha.co/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) provides scoring and insights based on product usage data for Product-Led Growth companies to better detect and leverage upsell opportunities. + +This destination is maintained by Matcha. For any issues with the destination, [contact the Matcha Support team](mailto:support@matcha.co). + +## Getting Started + +{% include content/connection-modes.md %} + +1. From the Destinations catalog page in the Segment App, click **Add Destination**. +2. Search for "Matcha" in the Destinations Catalog, and select the "Matcha" destination. +3. Choose which Source should send data to the "Matcha" destination. +4. Ask you Account Manager for your API key or [contact the Matcha Support team](mailto:support@matcha.co). +5. Enter the "API Key" in the "Matcha" destination settings in Segment. + +## Supported methods + +Matcha supports the following methods, as specified in the [Segment Spec](/docs/connections/spec). + +### Page + +Send [Page](/docs/connections/spec/page) calls to allow Matcha to leverage pageviews information in the scoring. For example: + +```js +analytics.page() +``` + +Segment sends Page calls to Matcha as a `pageview`. + + +### Screen + +Send [Screen](/docs/connections/spec/screen) calls to Matcha to leverage mobile information in the scoring. For example: + +```obj-c +[[SEGAnalytics sharedAnalytics] screen:@"Home"]; +``` + +Segment sends Screen calls to Matcha as a `screenview`. + + +### Identify + +Send [Identify](/docs/connections/spec/identify) calls to relay identification information that will be used for cross references in Matcha's scoring. For example: + +```js +analytics.identify('userId123', { + email: 'john.doe@example.com' +}); +``` + +Segment sends Identify calls to Matcha as an `identify` event. + + +### Track + +Send [Track](/docs/connections/spec/track) calls to allow Matcha to better understand user interactions with your product and leverage it in the scoring. For example: + +```js +analytics.track('Login Button Clicked') +``` + +Segment sends Track calls to Matcha as a `track` event. From 461a0cd3bef14a370afa3020c874bfcf1f2eae2c Mon Sep 17 00:00:00 2001 From: Thomas Gilbert Date: Thu, 23 Jun 2022 16:37:26 -0400 Subject: [PATCH 03/22] update event list to add events, correct naming conventions, and also alphabetized event names --- .../catalog/cloud-apps/iterable/index.md | 208 +++++++++++------- 1 file changed, 133 insertions(+), 75 deletions(-) diff --git a/src/connections/sources/catalog/cloud-apps/iterable/index.md b/src/connections/sources/catalog/cloud-apps/iterable/index.md index 35f444c19d..dc0c9cebe3 100644 --- a/src/connections/sources/catalog/cloud-apps/iterable/index.md +++ b/src/connections/sources/catalog/cloud-apps/iterable/index.md @@ -43,81 +43,139 @@ The default behavior is for Iterable to pass the `userId` associated with the em Collections are the groupings of data we pull from your Source. In your warehouse, each collection gets its own table, as well as a `tracks` table that aggregates all the events into a single table.  - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
**Collection****Type****Description**
Email DeliveredEventMessage has been successfully delivered to the receiving server
Email OpenedEventRecipient has opened the HTML message. You need to enable Open Tracking for getting this type of event
Email BouncedEventReceiving server could not or would not accept message
Email Link ClickedEventRecipient clicked on a link within the message. You need to enable Click Tracking for getting this type of event
Email SubscribedEventUser subscribes to a messaging channel
Email UnsubscribedEventRecipient clicked on message's subscription management link
Email Marked as SpamEventRecipient marked message as spam
Push DeliveredEventMessage has been successfully delivered to the receiving server
Push OpenedEventUser has been shown push notification by client app
Push BouncedEventReceiving server could not or would not accept message
Mobile App UninstalledEventGhost message sent 12 hours after original push delivered results in rejection from receiving server
SMS SendEventMessage has been successfully delivered to the receiving server
SMS BouncedEventReceiving server could not or would not accept message
SMS ReceivedEventUser has sent an inbound SMS that was received by server
**Collection****Type****Description**
Email BouncedEventReceiving server could not or would not accept message
Email DeliveredEventMessage has been successfully delivered to the receiving server
Email Link ClickedEvent + Recipient clicked on a link within the message. You need to enable Click Tracking for getting this type of event +
Email Marked as SpamEventRecipient marked message as spam
Email OpenedEvent + Recipient has opened the HTML message. You need to enable Open Tracking for getting this type of event +
Hosted Unsubscribe ClickEvent + User navigated to email preference center through a `hostedUnsubscribeUrl` link +
In App ClickedEvent + An in-app click event indicates that a user tapped a link or button in an in-app message +
In App DeliveredEvent + Indicates that an in-app message arrived on a user's device. It does not mean that the user viewed the message. +
In App OpenedEvent + Indicates that an in-app message displayed in an app, either because it appeared on arrival or because the user selected it in the inbox. +
In App SentEvent + Indicates that Iterable sent an in-app message to a user. It does not mean that the user received the message. +
Mobile App UninstalledEvent + Ghost message sent 12 hours after original push delivered results in rejection from receiving server +
Push BouncedEventReceiving server could not or would not accept message
Push DeliveredEventMessage has been successfully delivered to the receiving server
Push OpenedEventUser has been shown push notification by client app
SMS BouncedEventReceiving server could not or would not accept message
SMS ClickedEventUser has clicked link within SMS message
SMS DeliveredEventMessage has been successfully delivered to the receiving server
SMS ReceivedEventUser has sent an inbound SMS that was received by server
SubscribedEventUser subscribes to a messaging channel
UnsubscribedEventRecipient clicked on message's subscription management link
Web Push ClickedEventUser clicked on web push notification
Web Push DeliveredEvent + Web Push has been successfully delivered to the receiving server +