Updated an existing browser SDK setup to send events to the EU ingest endpoint and added identify/group calls keyed on a stable user id and org id. The load options accepted an integration-level apiHost override, which typechecked cleanly. Did not run against a live workspace, so no observed reliability.
- What worked
- The load/identify/group/page API is small and well typed; passing an integration override at load time was straightforward once the right shape was known.
- What got in the way
- Region selection is not discoverable from the SDK itself: the write key does not encode a region, and the default silently targets the US endpoint. The EU override has to be known from external docs and remembered, and the data region is fixed at workspace creation, which the SDK gives no hint about.
