Connect Amplitude to SiteOps
Amplitude tracks what people do inside your product — signups, clicks, the journey from first visit to paying customer. Where Google Analytics tells you who came to the site, Amplitude tells you what they did after they arrived.
Connecting it to SiteOps puts those two stories on one page. When a campaign brings a spike in traffic, you can see right away whether that spike turned into signups and real usage, or just bounced.
The whole setup is copying one key from your Amplitude project into SiteOps. It takes about five minutes, and you do not need to touch your tracking code.
Set it up, step by step
0 of 8 done
- Settings
- Organization settings
- Projects
The API key's journey — the secret key never leaves Amplitude Copy the whole key with no spaces around it — a stray space at the end is the most common reason a key is rejected.
- Settings
- Amplitude
- Save
If something does not work
- Which key do I paste — there are two on the project page
- The API key. The secret key sits right next to it and looks similar, but SiteOps does not need it and will reject it. Leave the secret key where it is.
- The key is rejected on Save
- Three usual causes: you copied the secret key instead of the API key, a space sneaked in at the start or end, or your Amplitude data lives in the EU region and SiteOps is asking the US one. Fix the key first, then check the region.
- It saved fine, but the chart stays empty
- The key is valid but the project has no events, or the events are very new. Open Amplitude and check that data arrived in the last day. If the project is fresh, give it a few hours of real traffic and check back.
- The Amplitude numbers do not match my Google Analytics numbers
- That is normal. Amplitude counts events you instrumented; Google Analytics counts sessions and visitors its own way. Ad blockers, consent settings and different counting rules mean the two lines will be close but rarely identical. Watch the trend, not the exact match.
- I cannot find Organization settings or the Projects page
- Your role in the organization is too limited to see project keys. Ask an admin to either raise your role or simply send you the API key for the right project — that is all you need.