Tags with Corbado Observe

​

1. Why use tags

• How does login conversion differ by country?
• Does auth success differ between experiment variants (auth_variant = A vs B)?

​

2. Send tags from the SDK

1. Globally via defaultTags in tracker initialization.
2. Per event by passing a tags object to a tracking call.

import { init, getTracker } from "@corbado/observe";

init({
  projectId: "<ProjectID>",
  apiBaseUrl: "<APIBaseURL>",
  defaultTags: {
    country: "de"
  },
});

getTracker().flowStarted({
  flowName: "login",
  touchpoint: "account",
});

import { getTracker } from "@corbado/observe";

getTracker().flowStarted(
  {
    flowName: "login",
    touchpoint: "checkout",
  },
  {
    country: "de"
  },
);

<script>
  Corbado.init({
    projectId: "<ProjectID>",
    apiBaseUrl: "<APIBaseURL>",
    defaultTags: {
      country: "de"
    },
  });

  Corbado.get().flowStarted({
    flowName: "login",
    touchpoint: "account",
  });
</script>

<script>
  Corbado.get().flowStarted(
    {
      flowName: "login",
      touchpoint: "checkout",
    },
    {
      country: "de"
    },
  );
</script>

​

3. Tagging best practices

• Keep tags short, predictable and business-relevant.
• Use strings for all values (for example is_new_user: "true").
• Avoid high-cardinality identifiers (for example raw user IDs) as tags.
• Prefer user references for identity mapping and tags for segmentation.

​

4. Next steps

• Continue with Flows to model complete journeys.
• Continue with Decisions to track explicit user and system choices.