Question

When sending an Order Completed event through the Amplitude (Actions) destination in Segment, why do both Order Completed and Product Purchased appear in Amplitude? These look like redundant or duplicate events firing at the same rate from the same library.

Product

Twilio Segment

Environment

Segment Console

Answer

This is expected behavior, not a duplication bug.

When an Order Completed event is sent through the Log Purchase mapping in the Amplitude (Actions) destination, Segment sends two separate events to Amplitude:

• The original Order Completed event, forwarded as-is with all of its properties.
• A Product Purchased event, generated separately for each product in the order, to carry revenue data into Amplitude's native Revenue Analysis and Lifetime Value (LTV) reporting.

This dual-event behavior is specific to the Log Purchase action and Order Completed events; other Amplitude (Actions) mappings do not generate an additional revenue event. It happens because Amplitude's revenue reporting is built around events with specific revenue-related fields (product ID, price, quantity, revenue type). Rather than requiring you to restructure Order Completed properties, the Log Purchase action extracts the product-level data and submits it as its own event so it lines up with what Amplitude's revenue reports expect.

If Order Completed is only mapped through Log Purchase, disabling that mapping to remove Product Purchased will also stop Order Completed from reaching Amplitude, since there would be no mapping left to forward it. 

To keep Order Completed flowing while dropping the Product Purchased event, add a separate mapping (for example, using a Log Event action) triggered on Order Completed, so it no longer depends solely on the Log Purchase mapping.

Additional Information 

• Before disabling the Log Purchase mapping, confirm whether Amplitude's native Revenue Analysis or LTV charts are in use, since those rely on the Product Purchased revenue data.
• See Segment's Amplitude destination docs for details on the Order Completed event mapping.
• See Amplitude's revenue tracking documentation for how they expect revenue events to be structured.