[Dashboard API] Segmentation for users, who performed another event

Hi, everyone. I didn’t find the answer either in docs or community.

The desired result is:

How to create the request?

My event data is:

const eventData = {<br />  "event_type": "_all"<br />};

What segment definition should be?

I’ve found some information about segments here. So, my definition looks like this:

const s = [{<br />    group_type: "User",<br />    prop: "gp:state",<br />    prop_type: "user",<br />    op: "is",<br />    type: "property",<br />    values: ["verified"]<br />},{<br />    op: ">=",<br />    type: "event",<br />    event_type: "landing.test",<br />    filters: [],<br />    value: 1,<br />    time_type: ???,<br />    time_value: ???<br />}, {<br />    op: ">=",<br />    type: "event",<br />    event_type: "test.open_app",<br />    filters: [],<br />    value: 1,<br />    time_type: 'forEachInterval',<br />    time_value: 30<br />}]

I’m not sure about this construction.

What are all the available values for “time_type”?
Why I should specify 30 for the “forEachInterval”?

Can someone tell me more about “group_type”, ‘prop_type’, ‘type’, ‘event_type’? This parameters are not specified in docs.

Thanks for any help!

Find more posts tagged with

Event Segmentation

API

Accepted answers

eddie.gaona

Hello gapon2401 happy to help!

There are a couple of ways to get the results you are looking for that could save you cost as the Dashboard Rest API has restrictive limits:

Use the Results from an Existing Chart endpoint. Since the chart is already created in the Amplitude UI you can pull the information programmatically using this endpoint. As mentioned, the main reason I present this option is that it will save you cost on the Dashboard Rest API limits.
You can definitely try building out the chart as an API call and it will have a higher cost than the above option. I will be using this Demo chart that is setup similar to the screenshot you provided: https://analytics.amplitude.com/demo/chart/new/xj3emx2
- The Segment definition would be as follows:
  - Purchase Song or Video: {op: ">=", type: "event", event_type: "Purchase Song or Video", filters: [], value: 0, time_type: "forEachInterval, “time_value”: 30}
    - The reason for the 30 is because the chart is looking at the last 30 days.
  - Play song or video: {op: ">=", type: "event", event_type: "Play Song or Video", filters: [], value: 1, time_type: "absolute",
    time_value: [1642377600, 1642982399]}
    - The time_value is the time in epoch “in between Jan 17 - Jan 23, 2022.

In summary using your example,

{<br />    op: ">=",<br />    type: "event",<br />    event_type: "landing.test",<br />    filters: [],<br />    value: 1,<br />    time_type: absolute,<br />    time_value: [1642377600, 1642982399]<br />}

Hope this helps!

All comments

eddie.gaona

Hello gapon2401 happy to help!

There are a couple of ways to get the results you are looking for that could save you cost as the Dashboard Rest API has restrictive limits:

Use the Results from an Existing Chart endpoint. Since the chart is already created in the Amplitude UI you can pull the information programmatically using this endpoint. As mentioned, the main reason I present this option is that it will save you cost on the Dashboard Rest API limits.
You can definitely try building out the chart as an API call and it will have a higher cost than the above option. I will be using this Demo chart that is setup similar to the screenshot you provided: https://analytics.amplitude.com/demo/chart/new/xj3emx2
- The Segment definition would be as follows:
  - Purchase Song or Video: {op: ">=", type: "event", event_type: "Purchase Song or Video", filters: [], value: 0, time_type: "forEachInterval, “time_value”: 30}
    - The reason for the 30 is because the chart is looking at the last 30 days.
  - Play song or video: {op: ">=", type: "event", event_type: "Play Song or Video", filters: [], value: 1, time_type: "absolute",
    time_value: [1642377600, 1642982399]}
    - The time_value is the time in epoch “in between Jan 17 - Jan 23, 2022.

In summary using your example,

{<br />    op: ">=",<br />    type: "event",<br />    event_type: "landing.test",<br />    filters: [],<br />    value: 1,<br />    time_type: absolute,<br />    time_value: [1642377600, 1642982399]<br />}

Hope this helps!

gapon2401

Thank you eddie.gaona! Everything works as expected!

Is it possible to enlarge the request limits to dashboard API?

Quick Links

Unanswered Questions

Guide and Survey Analytics not Working
Hey there I've been playing around for a couple of hours with the guide and analytics which fires properly on the UI but wouldn't give me any analytics. I read that there is another script that should be installed for the analytics part of things. Would anyone be able to guide me towards the potential script or some…
How can I connect my Google Analytics Data with Amplitude
All my data is being collected through Firebase I want to export all this data in Amplitude and keep it synced with GA4, I tried adding data sources as BigQuery and GA4 both but for some reason it only partially imported the data and now its not working, I cant even see connected sources. Any help will be appreciated.
Auto Capture Configuration Option does not exist for the React Native SDK
Auto Capture is a very prominent feature for the Browser SDK and the Native SDK's i.e. the IOS and the Android SDKs. It allows us to capture the basic [Amplitude] events like Button clicks, Navigation to pages, Pages Viewed, etc. The project that I am currently working on already has a web version on which we use the…
Import data from one amplitude account to another
How do I transfer data from one amplitude account to another? It seems all the community chats about this have completely broken links. Easy to export, no way to import, very frustrating. :(
@amplitude/plugin-web-vitals-browser build fails on CRA v4 (react-scripts@4.0.3)
When using @amplitude/plugin-web-vitals-browser with Create React App v4 (react-scripts@4.0.3), the build fails with: ./node_modules/@amplitude/plugin-web-vitals-browser/node_modules/web-vitals/dist/web-vitals.js<br /><br />SyntaxError:…