Skip to content

Commit 9b4051b

Browse files
authored
Add default mappings caveat (Amplitude Actions)
- When a customer migrates from Amplitude Classic to Amplitude Actions, they should be mindful to make sure that they customize their mappings - This is already mentioned under "Getting Started", but it might be helpful if it's mentioned under the "Migration from Amplitude Classic" section as well
1 parent fa585c1 commit 9b4051b

File tree

1 file changed

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

1 file changed

+3
-0
lines changed

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

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -206,6 +206,9 @@ To use Amplitude's groups with Segment, you must enable the following Action set
206206

207207
Keep the following in mind if you plan to move to Amplitude (Actions) from a classic Amplitude destination.
208208

209+
> info ""
210+
> Amplitude Classic uses different default mappings than Amplitude (Actions) in some cases (e.g. the `Viewed Home Page` event in Amplitude Classic will be `Viewed Home` in Amplitude Actions). Be sure to follow the steps in the Destination Actions documentation to [customize your mappings](https://segment.com/docs/connections/destinations/actions/#customizing-mappings).
211+
209212
### Amplitude (Actions) uses Amplitude's HTTP API v2
210213

211214
> warning ""

0 commit comments

Comments
 (0)