BI
Batch import
Parquet or CSV in your bucket, loaded on a schedule you set.
Take the write key
Everything this install sends is tagged with it, so one key per environment keeps staging out of your production numbers.
Generating…Install
Nothing to install — the change is configuration.
No package neededAdd it to Batch import
Paste this where the request path is assembled. The account callback is the only part you have to fill in — it is what turns a request into a customer.
text
Bucket s3://acme-exports/clearplane/
Format Parquet, one file per hour
Schedule Every hour, at :10
Account Column `org_id`Name this install
Name it for the deployment rather than the framework. Two Next.js apps in one workspace is the normal case, and “Next.js” twice helps nobody.
Environment
Events land in events_batch_import and are queryable from Chat, models, and SQL.