Skip to content

Commit c278920

Browse files
Merge branch 'master' into abSmartlyDocs
2 parents 4fa4692 + 4361695 commit c278920

File tree

9 files changed

+28
-24
lines changed

9 files changed

+28
-24
lines changed

src/_data/catalog/destination_categories.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
# AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
2-
# destination categories last updated 2021-08-12
2+
# destination categories last updated 2021-08-16
33
items:
44
- display_name: A/B Testing
55
slug: a-b-testing

src/_data/catalog/destinations.yml

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
# AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
2-
# destination data last updated 2021-08-12
2+
# destination data last updated 2021-08-16
33
items:
44
- display_name: ActiveCampaign
55
name: ActiveCampaign
@@ -2305,8 +2305,8 @@ items:
23052305
type: boolean
23062306
defaultValue: true
23072307
description: >-
2308-
Enabling this will send referrer information as a user property to
2309-
Amplitude when you call Segment's `page` method.
2308+
Client Side Only - Enabling this will send referrer information as a user
2309+
property to Amplitude when you call Segment's `page` method.
23102310
required: false
23112311
label: Track Referrer to Amplitude
23122312
- name: trackRevenuePerProduct
@@ -16164,8 +16164,7 @@ items:
1616416164
- Marketing Automation
1616516165
- Personalization
1616616166
logo:
16167-
url: >-
16168-
https://public-segment-devcenter-production.s3.amazonaws.com/58c0f9b4-3ec6-43c3-9158-0942ff36262b.svg
16167+
url: 'https://cdn.filepicker.io/api/file/R1AmIwNrRNGc139Q5SlY'
1616916168
mark:
1617016169
url: >-
1617116170
https://public-segment-devcenter-production.s3.amazonaws.com/d180bde1-ed0e-4155-95c4-e8013e6bda4e.svg

src/_data/catalog/source_categories.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
# AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
2-
# source cateogries last updated 2021-08-12
2+
# source cateogries last updated 2021-08-16
33
items:
44
- display_name: A/B Testing
55
slug: a-b-testing

src/_data/catalog/sources.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
# AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
2-
# sources last updated 2021-08-12
2+
# sources last updated 2021-08-16
33
items:
44
- display_name: .NET
55
slug: net

src/_data/catalog/warehouse_papi.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
# AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
2-
# warehouse data last updated 2021-08-12
2+
# warehouse data last updated 2021-08-16
33
items:
44
- display_name: Azure SQL Data Warehouse
55
slug: azuresqldw

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,7 @@ Then, inside AdRoll you can create a "segment" of all users doing any of those e
6060

6161
### Conversion Value
6262

63-
When you include an event property labeled `revenue` it will be tracked to AdRoll as `adroll_conversion_value`.
63+
When you include an event property labeled `price` it will be tracked to AdRoll as `adroll_conversion_value`.
6464

6565
### Currency
6666

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -184,7 +184,7 @@ analytics.track('Purchased Item', {
184184
name: 'bag'
185185
})
186186
```
187-
When you `track` an event, Segment sends that event to Braze as a custom event. Braze does not support arrays or nested objects for custom track event properties.
187+
When you `track` an event, Segment sends that event to Braze as a custom event.
188188
189189
> note ""
190190
> Braze requires that you include a `userId` or `braze_id` for all calls made in cloud-mode. Segment sends a `braze_id` if `userId` is missing. When you use a device-mode connection, Braze automatically tracks anonymous activity using the `braze_id` if a `userId` is missing.
33 KB
Loading

src/connections/sources/catalog/cloud-apps/braze/index.md

Lines changed: 18 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -4,29 +4,34 @@ title: Braze Source
44

55
[Braze](https://www.braze.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) is a marketing automation and customer engagement platform. Growth, Engagement, and Marketing teams use Braze to build great long term relationships with their customers across key digital channels.
66

7-
Take your company's marketing and customer engagement to the next level by adding Braze as a Segment Source, using Braze's Currents product. Segment automatically collects marketing and analytics events, forward them to your destinations, and load them into your data warehouse.
7+
Take your company's marketing and customer engagement to the next level by adding Braze as a Segment Source, using Braze's Currents product. Segment automatically collects marketing and analytics events, forwards them to your destinations, and loads them into your data warehouse.
88

99
In your favorite BI or analytics tool, you'll be able to analyze your mobile, email, and web marketing campaign data in SQL or using drag-and-drop reports. You'll be able to join your Braze data with the event data you're already sending through Segment to analyze the impacts of your marketing and engagement programs.
1010

11-
This source is maintained by Braze. For any issues with the source, you may [contact the Braze Support team](https://www.braze.com/docs/support_contact/).
11+
Braze maintains this source. For any issues with the source, you can [contact the Braze Support team](https://www.braze.com/docs/support_contact/).
1212

13-
_**NOTE:** If you are interested in using Braze, contact your Braze Customer Success Manager. Braze Currents is only available in select Braze packages and cannot be configured without assistance from the Braze team._
13+
> info ""
14+
> If you're interested in using Braze, contact your Braze Customer Success Manager. Braze Currents is only available in select Braze packages and can't be configured without assistance from the Braze team.
1415
1516
## Getting Started
1617

17-
1. From the Segment Sources page click **Add Source**.
18-
2. Search for "Braze" in the Sources Catalog and confirm by clicking "Connect".
19-
3. Give the Source a nickname and follow the set up steps to "Add Source".
20-
The nickname is used as a label for the source in your Segment interface, and Segment creates a related schema name. The schema name is the namespace you'll query against in a warehouse. The nickname can be anything, but we recommend sticking to something that reflects the source itself and distinguishes amongst your environments (for example, `Braze_Prod`, `Braze_Staging`, `Braze_Dev`).
21-
4. The next page "Overview" shows the Segment write key for Braze. Copy this write key.
22-
5. To finish set up, contact Braze Support or your Customer Support Manager to activate "Currents" in Braze.
23-
Braze Currents is only available in select Braze packages and cannot be configured within Braze without assistance from your Braze Customer Success representative.
24-
6. Go back to Segment, click into the Braze Source and you can add Destinations where you want to receive your Braze data.
25-
Events are now sent to these destinations and automatically loaded into any warehouses you have enabled.
18+
1. Go to **Connections > Sources** and click **Add Source** in the Segment app.
19+
2. Search for **Braze** in the Sources Catalog and click **Add Source**.
20+
3. Give the Source a nickname and click **Add Source**.
21+
The nickname is used as a label for the source in your Segment interface, and Segment creates a related schema name. The schema name is the namespace you'll query against in a warehouse. The nickname can be anything, but Segment recommends sticking to something that reflects the source itself and distinguishes amongst your environments (for example, `Braze_Prod`, `Braze_Staging`, `Braze_Dev`).
22+
4. Copy the **Write Key** on the Overview page.
23+
5. To finish the setup, contact Braze Support or your Customer Support Manager to activate Currents in Braze.
24+
Braze Currents is only available in select Braze packages and can't be configured within Braze without assistance from your Braze Customer Success representative.
25+
6. Go back to Segment and click **Add Destinations** in your Braze source to add the destinations where you want to receive your Braze data.
26+
27+
Events are now sent to these destinations and automatically loaded into any warehouses you enabled.
28+
29+
> warning ""
30+
> The Braze Segment Currents integration doesn't isolate events by different apps in a single app group. If you create more than 1 of the same Currents connectors (for example, 2 message engagement event connectors), they must be in different app groups. If you don't do this, it leads to data deduping and lost data.
2631
2732
## Components
2833
**Stream**
29-
Braze uses our stream Source component to send events to Segment. These events are then available in any Destination that accepts server-side events, including your data warehouse.
34+
Braze uses Segment's stream Source component to send events to Segment. These events are then available in any Destination that accepts server-side events, including your data warehouse.
3035

3136
## Events
3237

0 commit comments

Comments
 (0)