> For the complete documentation index, see [llms.txt](https://docs.revenium.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.revenium.io/monetize-your-ai/strict-ingestion-mode.md). # Strict Ingestion Mode Strict ingestion mode is an optional, per-account setting that requires every metering payload to reference objects — products, subscribers, credentials, organizations, and subscriptions — that already exist in your account. It is turned off by default. When you turn it on, Revenium stops creating new objects automatically from incoming metering data, so any record that references something unrecognized is held for your review instead of quietly entering your account. *** ## How strict ingestion works By default, when a metering event refers to one of those objects that Revenium hasn't seen before, Revenium creates it automatically so no usage is lost. Strict ingestion mode changes that trade-off for accounts that want tighter control over what enters their data. When strict ingestion mode is on: * Every incoming metering event is checked against those objects that already exist in your account. * Events whose references all resolve are ingested normally. * Events that reference something unknown — or whose name and identifier point at different objects — are not ingested. Each is recorded as an ingestion failure with a specific reason, so you can see exactly what needs fixing. When a record is held back, it and the reason it failed are kept so you can correct it and resubmit it. Held records are retained for 30 days; if a record is not corrected within that window, it is permanently deleted — so review and resubmit held records before then. {% hint style="info" %} Strict ingestion mode is off by default. While it is off, Revenium continues to create unrecognized references automatically, so no configuration is required to keep metering flowing. Turning it on is a deliberate choice for accounts that prioritize data governance and want to prevent unrecognized data from entering automatically. {% endhint %} ## Turning it on Strict ingestion mode is controlled per account and can be enabled by an administrator with permission to manage your account settings. Turn it on when you want incoming metering data validated against your existing objects, and turn it off at any time to return to automatic creation. The setting applies to metering events received after it is enabled. ## What gets held back When strict ingestion mode is on, a metering event is held back if any of the objects it references can't be matched in your account. Each held record is labeled with the reason it failed: * **Product not found** — the payload references a product that doesn't exist in your account. * **Product name/ID mismatch** — the product name and identifier in the payload point to different products. * **Subscriber not found** — the payload references a subscriber that doesn't exist. * **Subscriber name/ID mismatch** — the subscriber name and identifier point to different subscribers. * **Credential not found** — the payload references a subscriber credential that doesn't exist. * **Organization not found** — the payload references a consuming organization that doesn't exist. * **Organization name/ID mismatch** — the organization name and identifier point to different organizations. * **Subscription relationship not found** — no subscription links the referenced subscriber to the referenced product. * **Required reference missing** — the payload leaves out a reference that strict ingestion requires. Each reason is a stable, named category, so you can filter and triage held records by exactly what went wrong. ## Reviewing and resubmitting held records From the ingestion failures list for your account, you can: * See held records, newest first, and filter them by failure reason. * Identify what's missing or mismatched — for example, a product or subscriber that needs to be created, or a payload that referenced the wrong identifier. * Correct the underlying object or the sending integration, then resubmit the affected metering so it ingests cleanly. Because each held record keeps its original details and its failure reason, reviewing and resubmitting is a routine cleanup step. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.revenium.io/monetize-your-ai/strict-ingestion-mode.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.