analytics-next
analytics-next copied to clipboard
segmentio
Segment Analytics.js 2.0
To solve 3rd party script issues we want to proxy our own api.segment.io calls We're ok having it on the same fqdn and routing back w/ nginx/cloudflare/cloudfront/etc. But it looks...
Hey! Currently the `Content-Type` header is set to `text/plain`, like [here for the batch calls](https://github.com/segmentio/analytics-next/blob/master/packages/browser/src/plugins/segmentio/batched-dispatcher.ts#L88). Since we're sending JSON, should this be updated to `application/json; charset=UTF-8`, or is there any...
Hi team, we’ve run into a reproducible issue with @segment/analytics-next when it’s consumed inside a multi-layer package setup. Summary When @segment/analytics-next is included inside a library that is then re-bundled...
Hey there, We have a google tag manager destination from segment and we are looking into using a same-site proxy url instead of the google domain for loading the script...
Get data endpoint/settings has the following config metrics: When loading the browser, the request still uses the https protocol.
Hello 👋 I've noticed this problem when I needed to migrate client-side tracking from one cookie name to another one. It doesn't work. There is `cookie.oldKey` settings parameter available for...
We are seeing the following error: ```ts QuotaExceededError: Failed to execute 'setItem' on 'Storage': Setting the value of 'persisted-queue:v1:BGnTdxPHAw7r7tNB03yaxqgAs6xYlNtD:dest-Segment.io:items' exceeded the quota. ``` It appears that [persisted queue uses window.localStorage](https://github.com/segmentio/analytics-next/blob/master/packages/browser/src/lib/priority-queue/persisted.ts#L14)...
Hi Team, We are experiencing a lot of “smart” bot (disguised as normal UserAgents) traffic which is affecting our MTU usage. We have implemented bot filtering using regEx. We are...
Hello, We are trying to use Segment’s batching strategy to group events and send it after a specified timeout. After implement the suggested batching code, we noticed the events are...
When using @segment/analytics-next in my browser extension, with Amplitude as a destination, the library attempts to load an external script from cdn.segment.com, which **violates the Content Security Policy (CSP) restrictions...
