Skip to content

Drop identifiers that are empty after normalization - #99

Open
jrosendahl-opt wants to merge 1 commit into
masterfrom
fix/drop-empty-identifiers
Open

jrosendahl-opt wants to merge 1 commit into
masterfrom
fix/drop-empty-identifiers

Conversation

@jrosendahl-opt

@jrosendahl-opt jrosendahl-opt commented Nov 10, 2026 •

Copy link
Copy Markdown
Contributor

Why

An identifier whose value is empty once normalized was still sent:

An identifier whose value normalizes to nothing, like .postalCode("   ")
or .custom(2, ""), was sent as a bare "prefix:". .emailAddress("") and
.phoneNumber(" ") were worse: they sent the SHA256 of an empty string,
which looks like a real ID. All of these now encode to an empty string
and are dropped from identify and targeting.

Targeting hids now skip empty identifiers, as ids already did, instead
of sending an empty hid=.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@jrosendahl-opt
jrosendahl-opt requested review from a team as code owners November 10, 2026 02:20
jrosendahl-opt added a commit that referenced this pull request Nov 10, 2026
An unknown type with a whitespace-only value, like "xyz:   ", was sent as
given. It's now dropped, matching #99, which drops typed identifiers that
are empty after normalization.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@jrosendahl-opt jrosendahl-opt changed the title Drop identifiers that are empty after normalization [BREAKING] Drop identifiers that are empty after normalization Nov 10, 2026
@jrosendahl-opt jrosendahl-opt changed the title [BREAKING] Drop identifiers that are empty after normalization Drop identifiers that are empty after normalization Nov 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant