Skip to content

Commit 523cadb

Browse files
Update index.md
1 parent 6735158 commit 523cadb

File tree

1 file changed

+30
-3
lines changed
  • src/connections/destinations/catalog/actions-amplitude

1 file changed

+30
-3
lines changed

src/connections/destinations/catalog/actions-amplitude/index.md

Lines changed: 30 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -243,11 +243,38 @@ In the following example, the Amplitude User property `friendCount` equals 4.
243243
```
244244
## FAQ and troubleshooting
245245

246-
### Why doesn't Segment automatically add the `session_id` to my web events?
247-
For Segment to automatically add the `session_id` to events, your browser must allow the following request URL to load:
246+
### Does Segment load the Amplitude SDK on the webpage to collect data?
247+
Segment does not load the Amplitude SDK directly on the webpage. Instead, Segment collects data using our Analytics.js library. Once events reach Segment’s servers, they are forwarded to Amplitude’s servers using Amplitude’s HTTP API.
248248

249+
### How does Segment handle the Amplitude session ID?
250+
Although the Amplitude SDK is not loaded, the Analytics.js library includes a plugin that sets the Amplitude session ID on the device. This session ID is used to track sessions and is automatically attached to events sent to Amplitude. By default, the session ID is set to timeout after 30 minutes of inactivity. You can review the code implementation for setting the [session ID here](https://github.com/segmentio/action-destinations/blob/12255568e4a6d35cf05ee79a118ee6c1a6823f31/packages/browser-destinations/destinations/amplitude-plugins/src/sessionId/index.ts#L33){:target="_blank”}.
251+
252+
### How can I retrieve the Amplitude session ID set by Segment?
253+
Since Segment does not load the Amplitude SDK, the Amplitude native method `amplitude.getInstance()._sessionId` will not work. However, you can retrieve the session ID using the following method:
254+
255+
``` js
256+
localStorage.getItem('analytics_session_id');
249257
```
258+
259+
This call accesses the session ID stored in the browser's local storage. You can review the [retrieval code here](https://github.com/segmentio/action-destinations/blob/12255568e4a6d35cf05ee79a118ee6c1a6823f31/packages/browser-destinations/destinations/amplitude-plugins/src/sessionId/index.ts#L64 ){:target="_blank”}.
260+
261+
### Why is Segment not automatically adding the session_id to my Web Events?
262+
263+
For Segment to automatically add the session_id to your web events, your website must allow the following URL to load:
264+
265+
``` js
250266
https://cdn.segment.com/next-integrations/actions/amplitude-plugins/..
251267
```
252268

253-
To check if you are loading this request, [inspect the network requests](https://developer.chrome.com/docs/devtools/network){:target="_blank”} on your website and look for 'Amplitude.' If the request is not loading, confirm it is allowed on your side.
269+
How to Check:
270+
271+
1. Open your browser’s developer tools and [inspect the network requests](https://developer.chrome.com/docs/devtools/network){:target="_blank”} on your website.
272+
2. Look for a request related to Amplitude.
273+
274+
If the request is missing:
275+
276+
- Ensure your browser settings or network configuration allow this URL to load.
277+
- Check for any third-party script blockers or restrictions that might be preventing it.
278+
279+
If you still encounter issues, feel free to reach out for support!
280+

0 commit comments

Comments
 (0)