Enrich 6.13.0

[Benjamin BENOIST (benjben)]

Documents Enrich 6.13.0, covering the range 6.12.0..6.13.0.

Changes

• Bump enrich to 6.13.0 in src/componentVersions.js.
• Referrer parser enrichment — document the new utm_source classification (enrich#260):
  • New "Identifying referrers from utm_source" section: why it exists (AI chatbots send traffic with utm_source and no Referer header), built-in chatbot coverage in the hosted database, the utm_referrer derived entity, and how it relates to refr_* parsing and the campaign attribution enrichment.
  • New utm_sources field documented in the referrers custom-mapping table and both config examples.
  • Self-hosted config example bumped to referer_parser 2-0-2, with a note that 2-0-0/2-0-1 reject utm_sources.
  • Added a pointer in the database/uri section that the chatbot category and utm_sources entries require the actively-maintained referers-5.3 file, not the frozen referers-latest.

Not documented

The rest of the release range is internal and has no user-facing surface:

• Bump common-streams to 0.25.0 — verified no reference config changes between 0.24.0 and 0.25.0 (schema-ddl bumps + zstd compression-context reuse only).
• Add new Metadata dimensions (#220) — extra dimensions on the internal metadata reporting, no configuration or output change.
• Reuse a single long-lived compressor across batches (#253) — internal performance.
• CVE remediation workflow/skills, Snyk removal, sbt CI caching, bot detection enrichment refactor — repo internals.

No reference config changes in Enrich itself in this range (git diff 6.12.0..6.13.0 -- '*.conf' 'config/' is empty), so no configuration reference updates were needed.

Prerequisites before merging

This documents behavior whose supporting pieces are not all live yet:

• Enrich 6.13.0 is not released — only 6.13.0-rc1..rc5 tags exist.
• iglu-central schemas are unmerged — com.snowplowanalytics.snowplow/utm_referrer/jsonschema/1-0-0 and referer_parser/jsonschema/2-0-2 exist only on the utm_referrer branch. The page links to the master path for utm_referrer 1-0-0, and tells self-hosted users to declare 2-0-2; both need that branch merged.
• The hosted referer database has no utm_sources entries yet — they exist only on the utm_sources branch of snowplow/referer-parser. The page states chatbot sources work out of the box with referers-5.3, which requires that branch merged and the hosted file regenerated. (Adding utm_sources to referers-5.3 is backwards compatible: the pre-4.0.0 referer-parser decoder ignores unknown keys, so no new versioned database file is needed.)

🤖 Generated with Claude Code

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
🔵 In progress View logs	documentation	10c5a0f	Commit Preview URL Branch Preview URL	Jul 29 2026, 08:28 AM