Backfill Meters and Customers

backfill meters you can backfill as many meter events as you like each event must include a customerid backfill customers you can backfill as many customers as you like the customer backfill pipeline is run separately from meter ingestion you can run the customer backfill ingestion pipeline before, after or in parallel to meter backfill the customer ingestion pipeline enables you to enrich the customer object to automatically associate meter events with customers being ingested via the customer backfill pipeline, the customerids must match to the meter events the customer object contains the customerid and additional attributes (name, email, currency, and custom properties) meter data older than 24 hours can take up to 24 hours to process expect up to 24 hours for historical backfill data that is older than 24 hours to show up on the usage and billing dashboards realtime processing meter data that is up to 24 hours old (but not older) is processed, transformed, aggregated, time series sliced, and grouped by dimension in real time the real time pipeline runs end to end all the way from ingestion through pricing and invoicing, whereby, you see running invoices total with line items breakout in real time up to 24 hours delayed processing historical events older than 24 hours are processed periodically out of turn of the real time pipeline over time we will further shrink this duration (lag) window 📘 jump to java sample to backfill customers in stripe and amberflo from postgres java sample to backfill meters from postgres java sample to backfill meters from mongodb