Data Planning and Governance

Hello how are you? is it possible to do automatic provisioning with azure?

I have a simple react application using amplitude-js to send payloads to our API. Our API controller accepts and parses json message (application/json;charset=utf-8) but amplitude-js sends data in format data.I tried below code in my react application where I initiate amplitude intance but it doesn't work, it still sends the data in application/x-www-form-urlencoded format which is default:const amplitudeInstance = amplitude.getInstance("test").init("21e0fe6c98573ae71d209cb8ec4e85eb", null, { // optional configuration options saveEvents: false, forceHttps:false, headers: { 'Content-Type': 'application/json;charset=utf-8'}, apiEndpoint:'localhost:8080/events/publish', logEvent:'test data'})So my question is why can't I change amplitude-js's content-type as they mention in docs:https://developers.amplitude.com/docs/javascriptdeoland (Configuring HTTP Headers)Thanks

The Ampli CLI, Ampli SDK, and Amplitude SDK work together to bring a tracking library into your project.Developers use a Tracking Plan in the form of a type-safe autogenerated code.Iteratively can generate a tracking library for all popular platforms and programming languages. The autogenerated library, the Ampli SDK, is a lightweight wrapper over the Amplitude SDK that provides type-safety, supports linting, and enables features like input validation. The code replicates the spec in the Tracking Plan and enforces its rules and requirements. :::noteVisit the ampli-examples GitHub repo for example applications that use the Ampli SDK.::: Ampli CLI The Ampli CLI is how you download the Ampli SDK for your current tracking plan ampli pull.Verify implementation status of event tracking in your project by using ampli status. Ampli SDK The Ampli SDK is a dynamic, code-generated SDK. It contains strong types for the events in your tracking plan, and provides autocomplete and static type checkin

We have a gatsby website that I am trying to track events. We have defined a tracking plan using Iteratively. So I believe the steps are next to generate the sdk using that tracking plan. I have followed the steps in the documentation - https://developers.data.amplitude.com/browser. This generates a src/itly/index.js file which has methods for my track events. It also export itlySdk.However I am unable to get this file properly included and working in our gatsby website. I have tried making a plugin but cannot get it to work.My first question is the 2 different types of Browser - Javascript sources. I cannot find these mentioned anywhere in the docs. So should I be using Browser - Javascript or Browser - Javascript (Itly).Secondly the file generate when using Browser - Javascript (Itly) exports itlySdk. Whereas the documentation steps talk about importing itly. https://developers.data.amplitude.com/browser#import-into-your-app. I don’t have itly defined in the generated javascript.Thir

Hello everyone!Can I create a user segment based on another?I already created Segment A and Segment B and want to create Segment C such that C = ALL - A - B. Is it possible? Thanks =)

The HTTP API v2 is a great tool to ingest data into Amplitude via server-side. You can use Shell, HTTP, JavaScript, NodeJS, Ruby, Python, Java, and Go to hit the HTTP API v2 endpoint(https://api2.amplitude.com/2/httpapi).  I will demonstrate how to ingest data from the HTTP API v2 endpoint using a curl command using Terminal on a Mac laptop. The HTTP API v2 endpoint expects the event data to be formatted in JSON. Here is an example call:  curl -H 'Content-Type: application/json' -d '{"api_key": "INSERT_API_KEY","events":[{"device_id":"5f9fbb3b-8b65-5a35-8ec1-699f5cfb2998", "event_type":"test_event", "event_properties": {"button_clicked_name": "Subscribe"},"user_properties": {"is_subscribed": true},"ip":"127.0.0.1"}]}' https://api2.amplitude.com/2/httpapi  The breakdown of the call above: You will need the API Key of your Amplitude project (only members with manager and admin permissions can see this information) The Device ID or User ID of the unique user. (In the call we are u