Personyze Wiki Personyze Wiki docs
Open Personyze
Docs/ Analytics & Data Platforms/ Amplitude Integration — Personyze Events, With No SDK on the Page
Analytics & Data Platforms

Amplitude Integration — Personyze Events, With No SDK on the Page

Report Personyze campaign events straight to Amplitude from our servers — so they arrive whether or not the Amplitude SDK loaded on the page.

2 min read Updated 17 hours ago

Personyze can report an event to Amplitude whenever a visitor matches a campaign — sent from Personyze’s servers over Amplitude’s HTTP V2 API.

This is an Automation-only destination. It calls the API from Personyze’s own servers with a key, so there is no on-page equivalent and it does not need that tool’s script on your page. Tick it on a Send Event to Analytics action.

Amplitude does have a browser SDK, so it is fair to ask why this is server-side. Sending from our servers means the event arrives whether or not the Amplitude script loaded on that page — the difference between a destination that works and one that works where a script happened to load.

What you need

Field Where to find it
Project API key Amplitude → Settings → Projects → your project → API Key
EU project checkbox Tick it if your Amplitude project lives in the EU
If your project is not in the US, set the region — nothing will tell you. A key from a non-US project sent to the US endpoint is accepted, and the data is dropped. There is no error, anywhere. If events are not arriving, check this first.

How the person is identified

Amplitude events are keyed on the Personyze visitor id, not on an email address — so this destination works for anonymous visitors too. If you see “the recipient has no identifier” in the campaign log, the matched visitor had no id to send, which is rare.

What arrives

The event name you typed, the visitor id, a timestamp, and every property you added on the action — which can draw on the visitor’s Personyze profile and on live campaign metrics.

Related

Did this page answer your question?
Thank you — that goes to whoever maintains this page.