Update warehouse-connectors.mdx#1820
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
| | **Event table column additions** | Billed for non-NULL values | Adding a column with NULL values does not count as an update across all supported warehouses, each affected row counts as a billable event otherwise | | ||
| | **Event table deletes** | Billed when the delete occurs | Deleting events or properties will generate billable events for each affected row | | ||
| | **User table standard operations** | Not billed | In standard mode, user profile inserts, updates, and deletes are not billed | | ||
| | **User table history mode** | Billed for updates and deletes | With history sync enabled, each profile update or delete generates a billable event, including the initial historical import | |
There was a problem hiding this comment.
my understanding is that history/mirror mode user profile syncs will be billed exactly like a mirror event sync so from a historical import perspective, we would only bill for profile history where the timestamp (start_time) is in the current month, similar to how events work. Can maybe double check with Sowmya/Deepak to confirm if this was something that came from conversation with them
ishamehramixpanel
changed the title
| | | Append | ✅ | ✅ | | ||
| | | Mirror | ✅ | ✅ | | ||
| | **Historical events (backfills)** | One time | ✅ | ❌ | | ||
| | | Append | ❌ | ❌ | |
There was a problem hiding this comment.
curious as to the logic here. As i understand it there's no reason you could not import historic data with an append sync as long as you have different event time and inset time columns right?
There was a problem hiding this comment.
@mherrman true but in an ongoing way, once u create a sync and want to backfill whole data again ..its not effectively possible.
There was a problem hiding this comment.
I added some wording in the other comment on how we can add it.
|
|
||
| **Note on Deletes**: If you delete an event using the Mixpanel UI instead of Mirror, it will not be counted as a billable event. | ||
|
|
||
| **Note on Backfills**: If you already have an event in your Mixpanel project, and you sync in historical events for a past month with the same properties, it will not count towards billing. Otherwise, billing will occur at the time of the event update. |
There was a problem hiding this comment.
is this saying if you send a duplicate you won't be billed for it essentially?
There was a problem hiding this comment.
Can reword deletes and I think we can remove backfills. Anything in historical is not billed unless updated from mirror anyway right.
Note on Deletes: If you delete events using Mixpanel UI , those deletes are not counted towards billable events. Only Deletes coming from warehouse using mirror are billable.
There was a problem hiding this comment.
Note on backfills: You can also backfill using Append mode if you create a new sync. But for a ongoing sync you cannot backfill for older days with in the existing sync once the insert_time has moved past.
3 participants
No description provided.