Skip to content

Commit fd214d1

Browse files
final edit and clean up
1 parent 80fac29 commit fd214d1

File tree

1 file changed

+10
-11
lines changed
  • src/connections/destinations/catalog/markettailor

1 file changed

+10
-11
lines changed
Lines changed: 10 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Markettailor Destination
2+
title: Markettailor destination
33
rewrite: true
44
---
55

@@ -10,24 +10,23 @@ This destination is maintained by Markettailor. For any issues with the destinat
1010
## Getting Started
1111
{% include content/connection-modes.md %}
1212

13-
1. From the Destinations catalog page in the Segment App, click Add Destination.
14-
2. Search for “Markettailor” in the Destinations Catalog search field, and select the Markettailor destination.
13+
1. From the destinations catalog page in the Segment App, click **Add destination**.
14+
2. Search for “Markettailor” in the destinations Catalog, and select the Markettailor destination.
1515
3. Choose which Source should send data to the Markettailor destination.
16-
4. Go to the Markettailor integrations, find the Segment integration, click Authorize, and copy the API key.
16+
4. Go to the [Markettailor Integrations page](https://app.markettailor.io/integrations), find the Segment integration, click **Authorize**, and copy the API key.
1717
5. Enter the API Key in the Markettailor destination settings in Segment.
1818

19-
20-
## Page
19+
### Page
2120

2221
If you aren’t familiar with the Segment Spec, take a look at the Page method documentation to learn about what it does. An example call would look like:
2322

2423
```js
2524
analytics.page()
2625
```
2726

28-
Segment sends Page calls to Markettailor as a page view. These events can be used for specific conversion events such as “Thank you page” viewed.
27+
Segment sends Page calls to Markettailor as a `page view`.
2928

30-
## Identify
29+
### Identify
3130
If you aren’t familiar with the Segment Spec, take a look at the Identify method documentation to learn what it does. An example call would look like:
3231

3332
```js
@@ -36,13 +35,13 @@ analytics.identify('userId123', {
3635
});
3736
```
3837

39-
Segment sends Identify calls to Markettailor as an identify event.
38+
Segment sends Identify calls to Markettailor as an `identify` event.
4039

41-
## Track
40+
### Track
4241
If you aren’t familiar with the Segment Spec, take a look at the Track method documentation to learn what it does. An example call would look like:
4342

4443
```js
4544
analytics.track('Login Button Clicked')
4645
```
4746

48-
Segment sends Track calls to Markettailor as a track event. These events are used to track conversions and measure performance of personalized websites against generic version.
47+
Segment sends Track calls to Markettailor as a `track` event.

0 commit comments

Comments
 (0)