CONNECTIONS / HubSpot / HubSpot to Snap Custom Audience
Snap audiences that follow your HubSpot lists.
Pick the HubSpot active list once. From then on the Snap audience shadows it, receiving hashed adds and removals for whatever changed since the previous sync and nothing else.
- ● hubspot → snap.custom_audience :: live
- > sync list won_customers rows=16,890
- hash sha256(email,phone)
- route snap.custom_audience upsert
- ✓ audience refreshed · 12,836 matched
WHAT THIS ENABLES
HubSpot to Snapchat Custom Audience
HubSpot to Snapchat Custom Audience treats a HubSpot active list as the single definition of a Snap audience, applying hashed adds and removals every refresh so suppression and lookalike targeting never drifts from the CRM.
- The Snap audience simply follows the HubSpot list; nobody exports anything.
- High-value cohorts, already curated in HubSpot, doing double duty as lookalike seeds.
- Acquisition spend on Snap that stops reaching people HubSpot just marked as customers.
WHAT FLOWS WHERE
HubSpot to Custom Audience, mapped.
Every membership change on the nominated HubSpot list passes through Signals for hashing before landing on the Snap Custom Audience as an add or a removal.
Every membership change on the nominated HubSpot list passes through Signals for hashing before landing on the Snap Custom Audience as an add or a removal.
Built for the teams that own the number.
Anyone whose Snap audience refresh currently involves a CSV and a calendar reminder.
From kickoff to verified events.
-
Connect
Read-only token access to the single list the segment lives in.
-
Segment
The list's own membership rules stand in as the segment definition; identifiers hash at upload.
-
Sync
Snap receives the push on a schedule, with each refresh sending only the incremental change.
What ships with this use case.
Won customers filtered out of Snap prospecting before the next auction sees them.
Snap lookalikes that start from the customers HubSpot already rates as most valuable.
An audience that never needs someone to re-upload it by hand.
What Custom Audience actually receives.
- ● signals :: audience upload
- > POST /audience_match source=hubspot.list
- schema ["EMAIL_SHA256","PHONE_SHA256"]
- external_audience_id "snap_won_customers"
- id_list_size 16,890 · matched 12,836
- ✓ accepted match=76%
Adjacent moves on the same stack.
from HubSpot
HubSpot to Meta Custom Audience
HubSpot to Meta Custom Audience mirrors membership of a chosen HubSpot list into a Meta…
Learn more
from HubSpot
HubSpot to Google Customer Match
HubSpot to Google Customer Match rebuilds a Google Customer Match audience from a HubSpot…
Learn more
same use case
ActiveCampaign to Snap Custom Audience
ActiveCampaign to Snapchat Custom Audience: Signals reads your ActiveCampaign contacts and…
Learn moregeneric
Snap Custom Audience
Build and refresh Snap audiences from your CRM, warehouse, or SingleView with hashed…
Learn moreAsked on almost every call.
Does Snap match a HubSpot audience on more than just email and phone?
Whatever identifiers the source HubSpot list actually has populated. Email and phone are the two Datahash hashes by default, and a mobile advertising ID gets added to the payload automatically when the contact record carries one. Nothing reaches Snap unhashed, so the audience upload only ever contains what the underlying HubSpot property already stores in hashed form.
If we already sync this HubSpot list to Meta, does adding Snap mean building the segment logic twice?
No, the list stays defined once, inside HubSpot. Signals reads that same active list for every destination it feeds, Snap included, applying each platform's hashing and upload format on its own schedule. The maintenance burden stays where it should: one list, one place, HubSpot.
NEXT STEP