Skip to content

Commit 1a167d8

Browse files
author
markzegarelli
authored
Merge pull request #1852 from segmentio/engage-messaging
Add catalog entry for Engage Messaging
2 parents fd8f3c5 + f1409a3 commit 1a167d8

File tree

6 files changed

+59
-7
lines changed

6 files changed

+59
-7
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-09-16
2+
# destination categories last updated 2021-09-17
33
items:
44
- display_name: A/B Testing
55
slug: a-b-testing

src/_data/catalog/destinations.yml

Lines changed: 7 additions & 3 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-09-16
2+
# destination data last updated 2021-09-17
33
items:
44
- display_name: 2mee
55
name: 2mee
@@ -883,13 +883,17 @@ items:
883883
- name: trackingServerSecureUrl
884884
type: string
885885
defaultValue: ''
886-
description: This is the secure URL of your Adobe Analytics server.
886+
description: >-
887+
This is the secure URL of your Adobe Analytics server. It should start
888+
with `https://`
887889
required: true
888890
label: Tracking Server Secure URL
889891
- name: trackingServerUrl
890892
type: string
891893
defaultValue: ''
892-
description: This is the URL of your Adobe Analytics server.
894+
description: >-
895+
This is the URL of your Adobe Analytics server. It should start with
896+
`http://`
893897
required: true
894898
label: Tracking Server URL
895899
- name: useLegacyLinkName

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-09-16
2+
# source cateogries last updated 2021-09-17
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-09-16
2+
# sources last updated 2021-09-17
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-09-16
2+
# warehouse data last updated 2021-09-17
33
items:
44
- display_name: Azure SQL Data Warehouse
55
slug: azuresqldw
Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
---
2+
title: Engage Destination
3+
---
4+
5+
## Engage Messaging
6+
7+
[Engage Messaging](https://engage.so/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) helps businesses send personalised messages to customers based on customer traits and actions.
8+
9+
This destination is maintained by Engage Messaging. For any issues with the destination, [contact the Engage Messaging Support team](mailto:[email protected]).
10+
11+
12+
## Getting Started
13+
14+
15+
1. From the Destinations catalog page in the Segment App, click **Add Destination**.
16+
2. Search for "Engage Messaging" in the Destinations Catalog, after selecting it, choose the Source that will send data to Engage Messaging.
17+
4. Go to your [Engage dashboard](https://app.engage.so/settings/account), find and copy your "Public API key".
18+
5. Enter the API Key in the destination settings in Segment.
19+
20+
## Supported methods
21+
22+
Engage Messaging supports the following methods, as specified in the [Segment Spec](/docs/connections/spec).
23+
24+
### Identify
25+
26+
Send [Identify](/docs/connections/spec/identify) calls to identify the user profile and traits on Engage. For example:
27+
28+
```js
29+
analytics.identify('userId123', {
30+
31+
});
32+
```
33+
34+
If the user already exists on Engage, identify can also be used to update the user traits.
35+
Segment sends Identify calls to Engage Messaging as an `identify` event.
36+
37+
38+
### Track
39+
40+
Send [Track](/docs/connections/spec/track) calls to track user events and actions. For example:
41+
42+
```js
43+
analytics.track('Login Button Clicked')
44+
```
45+
46+
Segment sends Track calls to Engage Messaging as a `track` event.
47+
48+
---

0 commit comments

Comments
 (0)