Default Event Tracking ignores client.disabled option.

Hi, team. I’m using amplitude browser sdk via AmpliWrapper. To disable tracking in non-production environment, I set disabled=true at initializing ampli client. However, default events are sent to server. So I needed to configure both client.configuration.defaultTracking=false and disabled=true. This looks not natural to me.

  ampli.load({<br />    client: {<br />      apiKey: API_KEY,<br />      configuration: {<br />        defaultTracking: false,<br />      },<br />    },<br />    disabled: true,<br />  });

Find more posts tagged with

Active

Status: Active

Comments

There are no comments yet

Quick Links

Give your vote

Bantuan Reschedule Dan Refund Tiket AirAsia
Untuk Reschedule dan Refund tiket AirAsia, hubungi Kontak Center AirAsia di nomor O855 3333 674. menjelaskan alasan Anda ingin mengubah jadwal penerbangan dan mengikuti instruksi dari petugas layanan pelanggan.
Customer Service AirAsia Move
Untuk Reschedule dan Refund tiket AirAsia, hubungi Kontak Center AirAsia di nomor O855 3333 674. menjelaskan alasan Anda ingin mengubah jadwal penerbangan dan mengikuti instruksi dari petugas layanan pelanggan.
Layanan -Call -Center AirAsia Move
Untuk reschedule dan Refund tiket AirAsia, hubungi Kontak Center AirAsia di nomor O855 3333 674. menjelaskan alasan Anda ingin mengubah jadwal penerbangan dan mengikuti instruksi dari petugas layanan pelanggan.
Grouping reordering
Hi, I’d like to request a feature: it would be really helpful to have the ability to shuffle or reorder properties within an event, especially when grouping. Right now, adjusting the order of grouped outputs is quite cumbersome.

View All