Skip to content

Commit b2f5323

Browse files
committed
DOC-240 test incremental build
1 parent dba79d7 commit b2f5323

File tree

1 file changed

+0
-6
lines changed
  • src/connections/destinations/catalog/actions-amplitude

1 file changed

+0
-6
lines changed

src/connections/destinations/catalog/actions-amplitude/index.md

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -20,11 +20,6 @@ and conversion.
2020
> success ""
2121
> **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Amplitude Segment destination. There's also a page about the [non-Actions Amplitude destination](/docs/connections/destinations/catalog/amplitude/). Both of these destinations receives data _from_ Segment. There's also the [Amplitude Engage Segment source](/docs/connections/sources/catalog/cloud-apps/amplitude-cohorts/), which sends data _to_ Segment!
2222
23-
24-
25-
26-
27-
2823
## Getting started
2924

3025
1. Before you start, go to your [Amplitude workspace](https://analytics.amplitude.com){:target="_blank"}. Click **Settings** in the bottom left, then click **Projects** in the left menu. Select your **Project**. Copy the Amplitude API Key and Secret Key for the project.
@@ -111,7 +106,6 @@ Build your own subscriptions with the following Amplitude-supported actions:
111106

112107
You can see the Segment event fields Amplitude accepts for each action in the Actions subscription set up page.
113108

114-
115109
### Log Event
116110

117111
In the default configuration, the Log Event mapping is triggered when Segment sends a Track call to Amplitude (Actions).

0 commit comments

Comments
 (0)