Backfill Meters and Customers

backfill meters you can backfill as many meter events as you like each event must include a customerid backfill customers amberflo supports customer backfilling at any time, allowing you to ingest as many customer records as needed, independently of meter data the customer backfill pipeline runs separately from meter ingestion you can run the customer backfill ingestion pipeline before, after or in parallel to meter backfill to ensure meter events are correctly associated with the ingested customers the customerid field in your meter events must match the customerid of a customer ingested via the backfill pipeline the customer object contains the customerid (required) and additional attributes (name, email, currency, and custom properties) meter data older than 24 hours can take up to 24 hours to process when working with historical meter data (i e events older than 24 hours), you may notice a delay in visibility data in this category can take up to 24 hours to appear in the usage and billing dashboards realtime processing meter data that is less than 24 hours old is handled by amberflo’s real time pipeline this means the data is processed, transformed, aggregated, time sliced, and grouped by dimension almost instantly as a result, you’ll see real time updates reflected in your running invoices—including line item breakdowns—immediately after ingestion up to 24 hours delayed processing in contrast, meter events that are more than 24 hours old are processed periodically, outside of the real time pipeline while this introduces a temporary delay, the data will still be processed and reflected in your dashboards within 24 hours amberflo is continuously working to reduce this lag window even further 📘 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