Amplitude

Nimriz integrates with Amplitude through the HTTP V2 API. You connect the project once, then add one or more actions to control how Nimriz activity should be forwarded.

Requirements

You must have a Professional plan or higher to use the Amplitude integration.

Configuration

To connect Nimriz to Amplitude, you need an API Key from your Amplitude project.

1. Find Your API Key

1. In Amplitude, go to Settings → Projects.
2. Select the project you want to send data to.
3. Copy the API Key (do not use the Secret Key).

2. Set up Amplitude in Nimriz

1. In Nimriz, open Integrations.
2. Go to Catalog and choose Amplitude.
3. Paste your API Key and save the destination.
4. Add an action such as Send event.
5. Choose the event triggers and any mapping overrides you want.
6. Review the preview, send a test event, then enable the connection.

Event Payload

By default, Nimriz sets the Amplitude event_type to Link Clicked, QR Scanned, or the configured conversion name.

Nimriz does not forward original IP addresses or complete User-Agent strings to Amplitude. In standard privacy, Nimriz may use a daily-salted pseudonymous hash as the Amplitude device_id where supported. In strict privacy, visitor hashes are omitted and Nimriz uses a synthetic per-click identifier for required destination identifier fields.

Canonical schema fields such as short_url, domain_name, country, device_category, and utm_* are mapped into the Amplitude event_properties object automatically. Strict privacy may omit selected granular fields such as city. Per-action mapping overrides let you rename fields, add static values, or exclude fields.

Review your Amplitude project, notices, and legal basis before enabling forwarding. Do not place personal data, secrets, access tokens, or sensitive data in UTMs, custom parameters, destination URLs, or conversion payloads.

Troubleshooting

If you are not seeing data in Amplitude's real-time event stream:

1. Open the Amplitude destination in Nimriz.
2. Select the action you want to verify.
3. Check the trigger filters and payload preview.
4. Use Send test to this action to confirm the API key and payload are accepted.