Amplitude

Amplitude is a powerful analytics platform. The Fanplayr 360 Amplitude integration can be used only as a destination. These are the capabilities available:

Destination

• Send Event

Authentication

To allow Fanplayr 360 to connect to your Amplitude account, you will need to provide Fanplayr with two pieces of information:

• API Key: The API Key can be found in the "Project Settings" subsection of your Amplitude "Organization Settings" page. Copy and paste this value into the field in the Fanplayr 360 destination editor. Be sure to use the API Key and not the API secret.

• Region: This value specifies which region you have your data stored in Amplitude. More specifically, this value controls the regional endpoint used by Fanplayr 360 to invoke Amplitude's API.

Capabilities

Send Event

The main Amplitude capability is "Send Event", which can be used as a destination in both Automations and Pipelines. This destination capability formats Fanplayr 360 event data into Amplitude events and sends them via the Amplitude API.

By default, the event name supplied to Amplitude matches the event name in Fanplayr 360, but this can be overridden by the "Event Name Override" field in the properties section. If supplied, the system will use the override value as the event name for all events sent via this destination.

Amplitude's system has a concept of "Revenue", which acts as semantic event indicating that the inbound event generated revenue. This is supported by our system. All Fanplayr 360 events flowing through this destination with an event name (after potential override) that exists in the list of "Order Completed Events" in your account preferences will result in at least one "Revenue" event sent to Amplitude. The system will create one "Revenue" event for each product inside the $order.products array on the corresponding order. For this to be enabled, you must specify "Order" in the System Outputs section of the destination editor. The underlying non-revenue events will still be sent to Amplitude as normal "track" events.

Any additional outputs included in the "Custom Outputs" section of the destination will be included as event properties on the event generated for Amplitude.