Question

What are the key differences between Amplitude (Actions) and the classic Amplitude destination?

Product

Twilio Segment

Environment

Segment Console

Answer

The classic Amplitude destination captures the following user fields in device-mode (when it runs on the user’s device):

• Device Type (for example, Mac, PC, mobile device)
• Platform (for example, iOS or Android)

In contrast, Amplitude (Actions) only runs in cloud-mode, so it does not capture these device-level fields.

However, Amplitude (Actions) offers several benefits over the classic Amplitude destination:

• Fewer settings. Data mapping for actions-based destinations happens in during configuration, which eliminates the need for most settings.
• Clearer mapping of data. Actions-based destinations enable you to define the mapping between the data Segment receives from your source, and the data Segment sends to the destination.
• Support for Amplitude’s HTTP API v2. Amplitude (Actions) is built on the latest version of Amplitude’s HTTP API.
• Revenue is a top-level property. Amplitude (Actions) elevates revenue to a top-level property in requests sent to Amplitude. This enables inclusion of this data in Amplitude features like customer LTV reports.
• Tracking in cloud-mode. Amplitude (Actions) supports sending details from cloud-mode sources.

Additional Information 

You can find more details here.