Skip to content

Commit 1c88354

Browse files
author
markzegarelli
committed
Vale updates
1 parent 2cdc981 commit 1c88354

File tree

2 files changed

+19
-18
lines changed
  • .github/styles/Vocab/Docs
  • src/connections/destinations/catalog/selligent-marketing-cloud

2 files changed

+19
-18
lines changed

.github/styles/Vocab/Docs/accept.txt

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -78,6 +78,7 @@ onboarding
7878
Optimizely
7979
performant
8080
Preact
81+
Selligent
8182
Shopify
8283
Skalin
8384
Smartly

src/connections/destinations/catalog/selligent-marketing-cloud/index.md

Lines changed: 18 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -17,9 +17,9 @@ Before you enable Selligent Marketing Cloud in your Destination page, validate w
1717
1. Login into your *Selligent Marketing Cloud* environment.
1818
2. Within the *Selligent Marketing Cloud* module click the wheel icon at the bottom-left corner to access the general configuration panel:
1919
![1](images/1.png)
20-
3. Click on the "Access Management" tab and select "Service Accounts":
20+
1. Navigate tothe "Access Management" tab and select "Service Accounts":
2121
![2](images/2.png)
22-
4. In order to create a new account click on the "New" icon:
22+
4. To create a new account click on the "New" icon:
2323
![3](images/3.png)
2424
5. Provide a "Name" and choose the type "Custom", confirm by clicking the Save button.
2525
6. Set an expiration date. This indicates the period the key will be valid before it needs to be refreshed.
@@ -30,21 +30,21 @@ You can then proceed to configure your destination.
3030

3131
1. From your Segment UI's Destinations page click on "Add Destination".
3232
2. Search for "*Selligent Marketing Cloud*" within the Destinations Catalog and confirm the Source you'd like to connect to.
33-
3. Drop in the "*API Key*" and "*API Secret*" into your Segment Settings UI.
33+
3. Enter the "*API Key*" and "*API Secret*" into your Segment Settings UI.
3434
4. *SMC Admin URL* - Copy the link you use to log into the SMC admin should look like https://**{you company}**.slgnt.us
3535
![5](images/5.png)
3636
5. *Organization* - You will find the organization name on the top-right hand corner next to the menu icon.
3737
![6](images/6.png)
38-
6. *Allowed Events* - Add the `track` event names that you would like to whitelist/send to SMC
38+
6. *Allowed Events* - Add the `track` event names that you would like to allowlist or send to SMC
3939
7. *Events data list API name* - The default value is **segment_events**, if you have any issue regarding the property please contact the *Selligent Marketing Cloud* [Support team](https://support.selligent.com).
4040

4141
## Identify
4242

43-
If you haven't had a chance to review our spec, please take time to review and to understand what the [`identify` method](https://segment.com/docs/spec/identify/) does.
43+
If you haven't had a chance to review the Segment spec, please take time to review and to understand what the [`identify` method](/docs/spec/identify/) does.
4444

4545
An example call can look like:
4646

47-
```
47+
```js
4848
analytics.identify('userId123', {
4949
property1: 1,
5050
property2: 'test',
@@ -57,11 +57,11 @@ Identify calls will be sent to *Selligent Marketing Cloud* as an `identify` even
5757

5858
## Track
5959

60-
If you haven't had a chance to review our spec, please take time to review to understand what the [`track` method](https://segment.com/docs/spec/track/) can do.
60+
If you haven't had a chance to review the Segment spec, please take time to review to understand what the [`track` method](/docs/spec/track/) can do.
6161

6262
An example call can look like:
6363

64-
```
64+
```js
6565
analytics.track('userId123', {
6666
property1: 1,
6767
property2: 'test',
@@ -73,11 +73,11 @@ Track calls will be sent to *Selligent Marketing Cloud* as a `track` event.
7373

7474
## Group
7575

76-
If you haven't had a chance to review our spec, please take time to review to understand what the [`group` method](https://segment.com/docs/spec/group/) can do.
76+
If you haven't had a chance to review the Segment spec, please take time to review to understand what the [`group` method](/docs/spec/group/) can do.
7777

7878
An example call can look like:
7979

80-
```
80+
```json
8181
{
8282
"type": "group",
8383
"groupId": "SegmentToSMCStatic",
@@ -90,32 +90,32 @@ An example call can look like:
9090
}
9191
```
9292

93-
Group calls will be sent to *Selligent Marketing Cloud* as a `group` event. These calls can be leveraged to populate static segments in the *Selligent Marketing Cloud* platform. The static segment needs to be created first in the Selligent Marketing Cloud platform before it can be leveraged. The call should adhere the above example and consists out of the following elements:
93+
Segment sends Group calls to *Selligent Marketing Cloud* as a `group` event. These calls are used to populate static segments in the *Selligent Marketing Cloud* platform. The static segment must be created in Selligent Marketing Cloud before you can use it. The call should adhere the above example and contain the following elements:
9494
* <u>groupId</u>: The *api_name* of the static segment to populate
9595
* <u>userId</u>: The value on which the matching to populate the segment should happen
9696
* <u>traits</u>:
9797
* <u>matchkey</u>: this is a mandatory trait and should contain the name of the field in the userlist on which the matching should be done
98-
* <u>method</u>: this trait is optional and based on it we will do a remove call or an add call to the *Selligent Marketing Cloud* segment. The two values possible are REMOVE or ADD but it will default to ADD. So it’s only needed in case of a remove call
98+
* <u>method</u>: this trait is optional and indicates either a remove call or an add call to the *Selligent Marketing Cloud* segment. The two values possible are REMOVE or ADD but it will default to ADD. So it’s only needed in case of a remove call
9999
* <u>userlist</u>: this is a mandatory trait and should contain the *api_name* of the userlist in *Selligent Marketing Cloud*
100100

101101
## Alias
102102

103-
If you haven't had a chance to review our spec, please take time to review to understand what the [`alias` method](https://segment.com/docs/spec/alias/) can do.
103+
If you haven't had a chance to review the Segment spec, please take time to review to understand what the [`alias` method](/docs/spec/alias/) can do.
104104

105105
An example call can look like:
106106

107-
```
107+
```js
108108
analytics.alias("507f191e81");
109109
```
110110

111111
Track calls will be sent to *Selligent Marketing Cloud* as a `alias` event.
112112

113113
## Page
114114

115-
If you haven't had a chance to review our spec, please take time to review to understand what the [`page` method](https://segment.com/docs/spec/[page]/) can do.
115+
If you haven't had a chance to review the Segment spec, please take time to review to understand what the [`page` method](/docs/spec/page/) can do.
116116

117117
An example call can look like:
118-
```
118+
```js
119119
analytics.page("Home");
120120
```
121121

@@ -125,11 +125,11 @@ Track calls will be sent to *Selligent Marketing Cloud* as a `page` event.
125125

126126
## Screen
127127

128-
If you haven't had a chance to review our spec, please take time to review to understand what the [`screen` method](https://segment.com/docs/spec/screen/) can do.
128+
If you haven't had a chance to review the Segment spec, please take time to review to understand what the [`screen` method](/docs/spec/screen/) can do.
129129

130130
An example call in Objective C can look like:
131131

132-
```
132+
```obj-c
133133
[[SEGAnalytics sharedAnalytics] screen:@"Home"
134134
properties:@{ @"Feed Type": @"private" }];
135135
```

0 commit comments

Comments
 (0)