Skip to content

Commit 7bafafa

Browse files
committed
Fix identation of code blocks
1 parent ea5e564 commit 7bafafa

File tree

2 files changed

+16
-17
lines changed
  • src/connections/sources/catalog

2 files changed

+16
-17
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ Below is a table of events that InMoment sends to Segment. These events will sho
2424

2525

2626
| Event Name | Description |
27-
| ------------------------------- | --------------------------------------- | |
27+
| ------------------------------- | --------------------------------------- |
2828
| Wootric survey response created | A survey response was created |
2929
| Wootric survey response updated | An existing survey response was updated |
3030

@@ -33,7 +33,7 @@ Below is a table of events that InMoment sends to Segment. These events will sho
3333
Below are tables outlining the properties included in the events listed above.
3434

3535
| Property Name | Description |
36-
| ------------- | --------------------------------------------------------------------- | |
36+
| ------------- | --------------------------------------------------------------------- |
3737
| channel | The channel from which the survey was responded like ‘web' or ‘email' |
3838
| created_at | The timestamp of when the response was created |
3939
| metric_type | The mode of the survey like "NPS" or “CSAT” |

src/connections/sources/catalog/libraries/mobile/amp/index.md

Lines changed: 14 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -17,14 +17,14 @@ If you're new to [AMP](https://www.ampproject.org){:target="_blank"}, go through
1717
### Step 1: Include AMP component
1818
Before the closing `</head>` tag, include the [`amp-analytics` component](https://www.ampproject.org/docs/reference/components/amp-analytics){:target="_blank"}:
1919

20-
```js
20+
```js
2121
<script async custom-element="amp-analytics" src="https://cdn.ampproject.org/v0/amp-analytics-0.1.js"></script>
22-
```
22+
```
2323

2424
### Step 2: Include Segment analytics
2525
Within your `<body>` tags, include the following Segment analytics snippet:
2626

27-
```html
27+
```html
2828
<body>
2929
<amp-analytics type="segment">
3030
<script type="application/json">
@@ -37,12 +37,12 @@ Within your `<body>` tags, include the following Segment analytics snippet:
3737
</script>
3838
</amp-analytics>
3939
</body>
40-
```
40+
```
4141
Replace `WRITE_KEY` with the write key you obtain from the AMP Source you've set up within the Segment UI.
4242

4343
For sources in [EU workspaces](/docs/guides/regional-segment/), use the following snippet:
4444

45-
```html
45+
```html
4646
<amp-analytics type="segment">
4747
<script type="application/json">
4848
{
@@ -55,7 +55,7 @@ For sources in [EU workspaces](/docs/guides/regional-segment/), use the followin
5555
}
5656
</script>
5757
</amp-analytics>
58-
```
58+
```
5959

6060
By default, the snippet will automatically fire a page event which you can read more about [in the Page section of this documentation](/docs/connections/sources/catalog/libraries/mobile/amp/#page).
6161

@@ -66,7 +66,7 @@ The Page method lets you record page views on your website, along with your choi
6666

6767
A `page` call is included by default when you include Segment Analytics into your code with the ability to customize the `name` of your page:
6868

69-
```html
69+
```html
7070
<amp-analytics type="segment">
7171
<script type="application/json">
7272
{
@@ -77,15 +77,15 @@ A `page` call is included by default when you include Segment Analytics into you
7777
}
7878
</script>
7979
</amp-analytics>
80-
```
80+
```
8181

8282
## Track
8383

8484
The Track method (referred to as `click` in AMP) lets you record any actions your users perform.
8585

8686
In order to track these `click` events simply add a trigger with a `selector`, which behaves the same way as [CSS Selectors](https://www.w3schools.com/cssref/css_selectors.asp){:target="_blank"}, which will send that event once the user clicks:
8787

88-
```html
88+
```html
8989
<body>
9090
<amp-analytics type="segment">
9191
<script type="application/json">
@@ -109,15 +109,15 @@ In order to track these `click` events simply add a trigger with a `selector`, w
109109
</amp-analytics>
110110
<button class="read-more-button">Read More</button>
111111
</body>
112-
```
112+
```
113113

114114
## Properties
115115

116116
### Default properties
117117

118118
A few properties are automatically collected with each page view and track call:
119119

120-
```json
120+
```json
121121
{
122122
"anonymousId": "amp-<unique-id>",
123123
"context.locale": "en-US",
@@ -128,13 +128,13 @@ A few properties are automatically collected with each page view and track call:
128128
"context.screen.width": 600,
129129
"context.screen.height": 800
130130
}
131-
```
131+
```
132132

133133
### Custom properties
134134

135135
If you would like to collect additional, custom properties, include an `extraUrlParams` object. All properties you'd like to include must follow the format of `properties.<property_name>`:
136136

137-
```html
137+
```html
138138
<amp-analytics type="segment">
139139
<script type="application/json">
140140
{
@@ -152,7 +152,7 @@ If you would like to collect additional, custom properties, include an `extraUrl
152152
}
153153
</script>
154154
</amp-analytics>
155-
```
155+
```
156156

157157
### UTM parameters
158158

@@ -226,4 +226,3 @@ For further details refer to the various `Client ID` scenarios in relation to AM
226226
<!-- TODO: the product linked above was deprecated, need to find a replacement or hide this page --->
227227

228228
See a live <a href="https://segment-amp.firebaseapp.com">AMP with Segment analytics</a>
229-
<link rel="amphtml" href="https://segment-amp.firebaseapp.com">

0 commit comments

Comments
 (0)