ACTION_ID: person_ad_audience_ids_using_versium
NAME: Versium: hashed profile data
CATEGORY: Person Enrichment
CREDITS: 1

Turn a person's identity into hashed advertising identifiers for
Facebook, Google, LinkedIn, TikTok and AdRoll, so a Floqer list can be
uploaded as a matched custom audience.

1. INPUTS

email (type: email, optional)
  Email. Email address of the person

phone (type: string, optional)
  Phone. Phone number of the person

linkedin_url (type: url, optional)
  LinkedIn URL. LinkedIn profile URL of the person

first_name (type: string, optional)
  First Name. First name of the person

last_name (type: string, optional)
  Last Name. Last name of the person

full_name (type: string, optional)
  Full Name. Full name of the person

city (type: string, optional)
  City. City of the person

state (type: string, optional)
  State. State of the person

zip_code (type: string, optional)
  ZIP Code. ZIP code of the person

address (type: string, optional)
  Address. Street address of the person

business_name (type: string, optional)
  Business Name. Business name associated with the person

company_domain (type: string, optional)
  Company Domain. Business domain associated with the person

2. OUTPUTS

adroll (json) — AdRoll audience identifiers

facebook (json) — Facebook audience identifiers

google (json) — Google audience identifiers

linkedin (json) — LinkedIn audience identifiers

tiktok (json) — TikTok audience identifiers

generic (json) — Generic audience identifiers

original (json) — Original audience identifiers

3. HOW TO CONFIGURE

Every field is optional — supply whatever the row has. Configure
Action body:

{
  "inputs": {
    "email": "{{person_work_email_waterfall_01ab.work_email}}",
    "first_name": "{{input.first_name}}",
    "last_name": "{{input.last_name}}",
    "linkedin_url": "{{input.linkedin_url}}",
    "company_domain": "{{input.company_domain}}",
    "city": "{{enrich_person_linkedin_profile_01cd.city}}",
    "state": "{{enrich_person_linkedin_profile_01cd.state}}"
  }
}

Field-by-field:
  - email / phone / linkedin_url  The strongest match keys.
  - name + address fields         Versium's fallback identity graph —
                                  more of them raises the match rate.

4. KEY NOTES

- Every output is a `json` object of platform-specific hashed
  identifiers. Reach into them from a `formula` with the bracket form;
  dotted nested references resolve to empty.
- The identifiers are hashed by design — they are for uploading to an ad
  platform's custom-audience importer, not for reading.
- No field is required, but a call with no identifying value burns a
  credit and returns nothing. Gate with `run_if` on at least the email
  being non-empty.
- Coverage is US-centric. Non-US people frequently return no platform
  matches.

5. WHERE IT FITS IN A WORKFLOW

Pattern: enrichment chain -> filter (ICP match) ->
person_ad_audience_ids_using_versium -> google_sheet_add_data, then
upload the sheet to the ad platform.

6. WHEN TO USE

Use person_ad_audience_ids_using_versium to build a matched ad audience
from an outbound list, so paid and outbound hit the same accounts.

7. WHEN NOT TO USE

Need contact data for outreach rather than ad targeting
  -> action-detail/person_enrich_by_floqer.txt

Need company-level advertising signals
  -> action-detail/website_traffic_using_semrush.txt

Last updated: 2026-08-03.