Disable default Amplitude destination

[huv1k]

Summary

In the old SDK it was possible to disable sending data to Amplitude using middleware. In the current version, it's not possible to disable the default Amplitude destination. For example:

ampli.load({
  client: {
    apiKey: "***"
  },
});

ampli.client.remove("amplitude");

We are using @amplitude/analytics-browser version 2.11.11 and SDK generated with @amplitude/ampli. We could patch it and disable it here

Amplitude-TypeScript/packages/analytics-browser/src/browser-client.ts

Line 120 in ab16340

await this.add(new Destination()).promise;

but we would love to skip patching it. Would you be open to somehow disabling programmatically this default destination?

Motivations

We are sending data to Amplitude through Segment because we enhance data with some custom properties that are impossible to access in our frontend code. If we sent it both ways, there would be double the number of events and one without our important custom properties.

[izaaz]

@huv1k , if you do ampli.client.remove("amplitude"), does that not work?

[huv1k]

@huv1k , if you do ampli.client.remove("amplitude"), does that not work?

Amplitude Logger [Warn]: Plugin with name amplitude does not exist, skipping deregistration and events are still sent.

[Mercy811]

Hi @huv1k, could you try await ampli.load().promise? The default destination is registered on initialization asynchronously. It might be that remove() is executed when the default plugin hasn't been installed yet.

[huv1k]

Hi @huv1k, could you try await ampli.load().promise? The default destination is registered on initialization asynchronously. It might be that remove() is executed when the default plugin hasn't been installed yet.

Yes, this works. Thanks it didn't cross my mind that it can be issue 😅 I though it's going to execute faster 🙈