Recently active topics

We're planning to deploy Amplitude across multiple teams and need expert guidance on implementation best practices. Looking for a consultant with 1-2 weeks availability to help us:Develop comprehensive data taxonomy and tracking plan strategies Establish proper instrumentation workflows and review processes Train our teams on Amplitude analytics best practices Configure organizational settings and data governance frameworksExperience with similar Amplitude implementations preferred.

I need help!  I’m using Kajabi to host my site. My unique visitor count in Amplitude has been way too high during my testing phase. I haven’t publicly launched yet so I’m the only one using the site during setup and testing, which is how I know the numbers are totally wrong.I had a feeling the original issue was that it was tracking both my domain and the kajabi testing subdomain for my site. I fixed that over a week ago.I was also testing on different browsers on my computer and using private browser sessions, which I know could have contributed to multi-counting me as different people. However, that was all last week.My unique visitor count for today says 67 people. There's no way. I only visited the site a handful of times today – all from one Safari browser session on one laptop. Here’s a good example: It says 11 people visited my /sample-lesson page and had 18 page views today. There’s no way that’s true. I visited that page once, MAYBE twice. It also says 5 people had 10 page vie

 Hello! We paid for access and set up a remote configuration in Data within the project.Also connected inside the project via the following code:await init(apiKey, '', { disableCookies: true,}).promise;const config = { enableRemoteConfig: true, sampleRate: 0.1, autoStart: !isDevEnv, disableCookies: true,};const sessionReplayPlugin = new SessionReplayPlugin(config);await add(sessionReplayPlugin).promise; But it still doesn't work, Amplitude doesn't record and doesn't seem to recognize that we've connected Session Replay. Please help us with solution. Thank you!

This is so irritating. I want to enable session replay, but not have auto capture events since they are so annoying. I use the following sdks for two reasons: For some reason session replay does not work if I use this:<script src="https://cdn.amplitude.com/script/AMPLITUDE_API_KEY.js"></script> Also, I have a different api key for staging, uat and prod. Therefore I would rather add in the api key at run time in the init function.My current setup is:<script src="https://cdn.amplitude.com/libs/analytics-browser-2.9.0-min.js.gz"></script><script src="https://cdn.amplitude.com/libs/plugin-session-replay-browser-1.4.0-min.js.gz"></script><script>// These are public values! :)const AMPLITUDE_API_KEYS = {"prod http url": "redacted","uat http url": "redacted","stg http url": "redacted",}; // We will blow up our usage if this is set too high.const AMPLITUDE_SAMPLE_RATES = {"prod sample rate": 0.1,"uat sample rate": 1.0,"stg sample rate": 1.0,}; // Also,

Hi Amplitude Team and Community,We're currently using a forked version of the Amplitude server for our service. This server uses the Amplitude HTTP API V1, and we're in a situation where we need to refer to its official documentation for a technical review.We understand that the V1 API has been deprecated, but since our current setup is based on this version, we're urgently looking for the official documents related to it.Could you please let us know if there is an archive or a location where we can access the V1 API documentation?Thank you for your time and help.Best regards,Jamin Ahn

I see in some of the events that client_upload_time was long before client_event_time. How can upload  event happen before the event was generated? Here is one example record.  

Hi Team, Just wanted to double check - the time clause ‘during X date range’ after the ‘Then’ clause in cohorts is related to our starting event and not the event mentioned after then clause. Like in this case :During 1 Jan to 28 Feb will apply to open-editor and not  ‘access-app-complete’ Tia!

I am trying to set up a Snowflake Destination connection using RSA Key Pair authentication, but the connection is failing. The login attempts do not even show up in Snowflake's LOGIN_HISTORY view, which indicates the connection is being rejected before it reaches the Snowflake database itself.I have already verified that: The role, database, warehouse, and schema for this new user are the same as another existing user who can successfully connect to Snowflake. The existing user is also configured with RSA key pair authentication and is working correctly. ​​​​​​

Hi Team, Can someone help explain why the daily numbers for D1-6 retention don’t match the averages at the top row. I have added an offset as well in the date range so that we do not have incomplete data.  

After Integration as mentioned in home page we have added below code in our shopify website But in browser console we are getting too many errors regarding amplitudeAmplitude Logger [Error]: TypeError: Failed to construct 'URL': Invalid URLKindly check and let us know solution  <script type="text/javascript"> !function(){"use strict";!function(e,t){var r=e.amplitude||{_q:[],_iq:{}};if(r.invoked)e.console&&console.error&&console.error("Amplitude snippet has been loaded.");else{var n=function(e,t){e.prototype[t]=function(){return this._q.push({name:t,args:Array.prototype.slice.call(arguments,0)}),this}},s=function(e,t,r){return function(n){e._q.push({name:t,args:Array.prototype.slice.call(r,0),resolve:n})}},o=function(e,t,r){e[t]=function(){if(r)return{promise:new Promise(s(e,t,Array.prototype.slice.call(arguments)))}}},i=function(e){for(var t=0;t<m.length;t++)o(e,m[t],!1);for(var r=0;r<y.length;r++)o(e,y[r],!0)};r.invoked=!0;var a=t.createElement("scrip

Hi all,We are getting set up on Amplitude and want to be able to have demo videos automatically show up in a guide in a 9:16 ratio (vertical/portrait) and not in the crunched landscape orientation that the current frame delivers for Vimeo and YouTube. We are using the iOS SDK, which seems like it may be the limiting factor here...Has anyone successfully accomplished this? If so, would appreciate any guidance you may have. Thanks!!

I noticed that the exact same event is firing twice, usually within less than a second (via event stream in “View Users”). It’s not possible for the user to do this. This is not observed in QA.For the double-fired events, I will only see one of the two events listed in the user’s log. When I use the search bar to look up the event name, then I’ll see the count as 2. If I click the up/down arrows by the search bar, I then see the second event’s info on the right panel. It’s still not listed in the user’s log. Why is it hidden?The incorrect event count seems to be reflected in chart view. In the raw data, I saw the double-fired events have different libraries. One library is “amplitude-js/5.2.2”, and the other is “segment”. The event IDs, timestamps, session IDs, and insert IDs are also different. Is that why the events weren’t deduplicated?Is this a set-up issue or a bug with Amplitude?