Skip to main content

Organise and Parse Data

Before you start​

Use tenant-administrator access for configuration. First decide whether you are sending structured events or raw transport input. Ordinary structured events use registered schemas; a raw parser does not replace their event schema.

Sites, labels and environments​

Use Admin → Sites to manage site records and their tracking configuration. For a browser integration, create a site with a name, environment and allowed origins, for example your actual https://app.example.com origin. Use Copy snippet when a usable write key is available and install the supplied snippet in your site. If the key is unavailable, rotate it through the explicit control and update existing snippets. Visit one test page and verify its accepted event and query result before assuming tracking works. Never substitute a confidential OAuth client secret for the site's browser tracking key.

Use Data Labels to define and manage tenant vocabulary and assignments, and Environments to inspect or curate environment values. Select the intended tenant and use the fields offered by each form; retain the returned identifiers.

For example, keep production and staging activity distinguishable by sending the corresponding environment through your producer's supported SDK configuration. Then inspect Environments, send a small valid batch, and verify its labels in the resulting query. Existing event label assignments are frozen at ingestion; editing vocabulary does not reinterpret historical events.

Missing environment metadata may appear as unclassified. Automatic creation of new environment values depends on tenant policy and the active-value limit. Check the per-item ingest error before retrying a value rejected by policy.

Owned data spaces​

Admin → Data Spaces manages the spaces available under an approved parent account. The parent must already have the relevant entitlement; creating a data space is not the same as creating an unrestricted platform tenant. Choose your parent, create the intended owned space using the offered form, and retain its identifier. Admin → Producers exposes reservation and claim controls; use the returned identifiers and the producer guide for credential handoff.

For example, a broker can dedicate one owned space to one customer, provision its producer, then verify a small event is visible only in that space. If entitlement or ownership is rejected, correct the parent/configuration shown in the error; do not substitute a system-admin tenant-creation endpoint.

Create a parser for raw input​

  1. Open Parsers (/parsers) and choose the parser type required by your source.
  2. Enter a stable code and name, the regex pattern if using a regex parser, the timestamp format, and a JSON object of string-to-string field mappings.
  3. Save the parser and verify it appears in the list. Select it to edit existing configuration. Review consumers before using the explicit delete confirmation.

Example regex definition: code simple-message, name Simple message, pattern (?P<message>.+), field mapping {"message":"message"}. This captures a message from one input line. It is a configuration example, not a complete transport setup or proof that input has been processed.

Expected result: a persisted parser definition. Attach it through your supported raw-input configuration, test one representative input, and inspect processing results before sending volume. Invalid mapping JSON or missing regex patterns are rejected; correct the form error. Saving a parser alone does not start a listener, attach it to a source, or rewrite existing stored data.