Add individual text fields for all 4 user ID types#19
Open
ZLeventer wants to merge 2 commits intolinkedin-developers:mainfrom
Open
Add individual text fields for all 4 user ID types#19ZLeventer wants to merge 2 commits intolinkedin-developers:mainfrom
ZLeventer wants to merge 2 commits intolinkedin-developers:mainfrom
Conversation
…in-developers#7) Use getCookieValues to read the li_fat_id cookie when the LinkedIn first-party ads tracking UUID is not provided via user overrides, event model, or GA4 user properties. Adds get_cookies permission scoped to the li_fat_id cookie name.
Resolves linkedin-developers#6. Adds userId_sha256email, userId_lifatid, userId_acxiomid, and userId_moatid as dedicated TEXT fields in the User Ids Override group, giving users a simpler alternative to the SIMPLE_TABLE for configuring each identifier directly. The JS resolution order checks these text fields first, then falls back to the table overrides and auto-detected values. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This was referenced Apr 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #6.
Problem
The existing User Ids Override group only exposes IDs through a SIMPLE_TABLE, which requires users to pick an ID type from a dropdown and enter a value per row. This is cumbersome for the most common case where a user just wants to hard-wire one specific ID.
Solution
Adds four dedicated
TEXTfields inside the User Ids Override group — one per supported identifier:userId_sha256emailuserId_lifatiduserId_acxiomiduserId_moatidThe text fields are checked first in each resolver function, before the table override and auto-detection fallbacks, so explicit configuration always wins. The existing SIMPLE_TABLE is preserved for backwards compatibility.
Resolution priority (example for SHA256 Email)
data.userId_sha256email(new text field) ← highest priorityuserIdsOverride.email(existing table override)user_data.sha256_email_address(auto-detected from event data)user_data.email/eventModel.email(plaintext → hashed)