Skip to content

Analytics: setuid passes raw uid to analytics reporters with only the TCF check #4718

Open

Description

@patmmccann

🤖 This issue was written by an AI agent (Claude Code) on behalf of @patmmccann.

What happens

/setuid puts the raw uid on the SetuidEvent and sends it to the analytics reporters:

final TcfContext tcfContext = setuidContext.getPrivacyContext().getTcfContext();
final SetuidEvent setuidEvent = SetuidEvent.builder()
.status(statusCode)
.bidder(cookieFamilyName)
.uid(uid)
.success(uidsCookieUpdateResult.isUpdated())
.build();
analyticsDelegator.processEvent(setuidEvent, tcfContext);

The only analytics privacy check it gets is the host-level TCF Purpose 7 enforcement in processEvent(event, tcfContext) (L107-L142). SetuidEvent has no account or ActivityInfrastructure (model), so isAllowedAdapter uses its default branch with a null infrastructure (L218-L224). That means reportAnalytics, transmitUfpd and transmitEids are never evaluated for this event.

The handler already builds the account's ActivityInfrastructure (L192-L199) and uses it for syncUser (L242-L249), but it doesn't pass it to analytics.

Why it matters

Privacy. The bidder UID is a persistent per-user identifier. Where TCF doesn't apply (e.g. US state privacy through GPP/activity controls), a publisher who has denied reportAnalytics, transmitUfpd or transmitEids to an analytics reporter could still have that reporter receive bidder UIDs from /setuid.

To reproduce

  1. Enable a reporter (e.g. logAnalytics or pubstack).

  2. Account acc1:

    { "privacy": { "allowactivities": { "reportAnalytics": { "default": false } } } }
  3. GET /setuid?bidder=<any>&uid=abc123&account=acc1 with no GDPR signal.

Expected: the reporter receives nothing, or at least no uid. Actual: it receives SetuidEvent{uid="abc123", ...}.

Expected behaviour

Before a reporter receives a setuid event, the account's reportAnalytics rule is checked for that reporter. When transmitUfpd or transmitEids is denied for it, uid is removed from the event.

Suggested fix

Add account/activityInfrastructure to SetuidEvent, handle it in isAllowedAdapter (REPORT_ANALYTICS with an analytics component payload), and in updateEvent null out uid for each reporter when TRANSMIT_UFPD or TRANSMIT_EIDS is denied. The same plumbing would also fix the missing enable checks in #4717.

References

🤖 Generated with Claude Code

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions