Refining Client-Facing Questions on Mixpanel Raw Event Export API
Please can you refine this questions and answer, it's client facing email . I did some offline digging to clarify the 2 questions raised on the call centred around the Mixpanel (Raw Export Data API)
- 1.
Why does the Raw Event Export API ignore the from_date and to_date filters when the API is called? The behaviour observed is that it returns the first 100,000 events regardless from the start date until it hits the 100,000 limit per query?
- a.
ANSWER: The Raw Event Export API returns events in chronological order starting at from_date and stops when it hits either to_date or the limit whichever comes first. If your date window (even a single day) contains more than 100,000 events, the API will stop at the 100k cap before reaching to_date. This can make it appear as though the API is ignoring the date range, but it's truncating the response due to volume.
- b.
Options worth exploring:
i. Option 1: Paginate your exports using smaller windows (e.g., hour-by-hour or multi-day slices) to ensure full coverage. ii. Option 2: Raise or explicitly set limit to 100,000 if not already done some clients apply their own default caps.
- 1.
Can we use the “where” clause to control the date range?
- a.
ANSWER: No, the “where” query parameter is not a substitute for from_date/to_date. Narrow the from_date/to_date window further (e.g., multiple calls per day). Refer to documentation for guide: https://github.com/mixpanel/mixpanel-utils/blob/master/sample_scripts/exporting_varied_length_date_ranges/README.md
- b.
The “where” query parameter filters events based on event properties using Mixpanel’s selector expressions. It can be used to filter by:
i. String or numeric properties (eg where='properties["$browser"] == "Chrome"') ii. A custom timestamp property (if you send one)
- 1.
But it does not control the canonical event time window that’s strictly handled by from_date and to_date.
Ensure to fact-check my assumptions and responses to the questions answered. Use bullet points to call out points, easy to read along
