Repository navigation
Contact lists: keep name, company, title and country for LinkedIn's people match - #49
Merged
Merged
Conversation
…eople match Contact uploads used to keep only the hashed email and drop every other column. LinkedIn's list upload also takes firstname, lastname, employeecompany, title and country as plain text, which lifts the match rate on work emails, and a row with a first and last name can match with no email at all. - The cleaner maps those columns (with common aliases) on contact lists, trims them to LinkedIn's length caps, and keeps only two-letter country codes. A list with first and last name columns but no email is a contact list. - The upload hashes the email, sends the other columns as text, keeps a row with an invalid email as a name match when it has both names, and dedupes on the email hash or name + company. - Email-only lists (CSV, Salesforce, HubSpot) upload exactly as before. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
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.
What
Contact list uploads kept only the hashed email and dropped every other column. LinkedIn's list upload also accepts
firstname,lastname,employeecompany,titleandcountryas plain text next to the hashedemail. These lift the match rate on work emails, and a row with a first and last name can match with no email at all ("People match" in the spec).Changes
audienceCsv.ts)First Name,Company,Job Titleand so on).nameis not treated as the company on a contact list, since there it is usually the person's name.audience.ts, newcontactListCsv)email\n<hash>CSV as before.docs/tools.md,docs/index.md, the README and the regenerateddocs/tools.json.LinkedIn API behavior relied on
DMP Segment List Uploads, Contact Lists (li-lms-2026-10):
email(SHA256),googleaid,googleuid,firstname,lastname,employeecompany,titleandcountry(the rest as plain text).Tests
packages/core/test/contactList.test.mjshas 7 new tests:pnpm -r typecheckis clean, andpnpm --filter @adwarp/core testpasses all 35 tests.🤖 Generated with Claude Code