Skip to main content
Hi, we're trying to use the Session Replay service on the Starter plan.
 
We have Session Replay enabled and sampling set to 100% of the traffic for our project.
 
Data is coming into the service, we can see successful requests in Ingestion Monitor https://app.amplitude.com/analytics/{our-org}/session-replay/monitor for our app but in the Session Replay page https://app.amplitude.com/analytics/{our-org}/session-replay it is showing 'Watch your first session replay'
 
 
We are currently using Segment to track analytics through to Amplitude, so are using @amplitude/session-replay-browser and have set Segment to prefer anonymous ids as outlined https://community.amplitude.com/data-instrumentation-57/amplitude-device-id-vs-segment-anonymous-id-vs-google-client-id-1608
 
import { AnalyticsBrowser } from "@segment/analytics-next"
import * as sessionReplay from "@amplitude/session-replay-browser"


let analytics: AnalyticsBrowser

...



const anonId = analytics.instance?.user()?.anonymousId() as string

await sessionReplay.init(apiKey, {
  sessionId: new Date().getTime(),
  deviceId: anonId,
  sampleRate: 1
}).promise

 

The device ids being used are the same as those listed in Amplitude for the given user, and http requests are being sent to https://api-sr.amplitude.com/sessions/v2/track?device_id={deviceId}&session_id={sessionId}&seq_number=4&type=replay with a 200 response
 
I'm not sure what to change to make this work correctly.

 

We are having the same issue. Data ingestion tools is showing that it’s receiving data but the session replay screen is showing the initial ‘get started’ message. I’ve the sample rate to 100%  

@Afzal Hossain I got this advice from amplitude support:

With the Standalone SDK, you need to instrument your application to add the property >Amplitude] Session Replay ID to any events that occur during capture. Please ensure you have seen this field in the normal events first and then check if you can see Session Replays.
 
More details can be found in the document https://amplitude.com/docs/session-replay/session-replay-standalone-sdk#add-session-replay-id-to-your-events 

We ended up using  @amplitude/analytics-browser with @amplitude/plugin-session-replay-browser to spike something out instead of going via segment as we just wanted to see what amplitude session replay was going to give us.

Yes, we’re adding `mAmplitude] Session Replay ID` but it’s not helping

Reply


Terms & ConditionsCookie settings