Once a CRM is connected, PocketPass reads its audiences and lets you target by them - both when you send a notification and when you decide which template a customer gets. You don't rebuild your segmentation in PocketPass; you reuse it.
What each provider exposes
The audiences PocketPass can see depend on what the provider's API returns.
Klaviyo exposes lists and segments. Both come through, and both work everywhere PocketPass targeting does.
Mailchimp exposes lists (audiences), tags, and saved segments. In the notification audience picker these are grouped as Mailchimp audiences / Mailchimp tags / Mailchimp segments so you can tell them apart at a glance.
Me&u Connect has no lists or segments. Targeting for Me&u accounts is done with PocketPass's own group tags and pass templates instead.
Constant Contact exposes contact lists. Segments are deliberately not imported: Constant Contact's segment API can return results while a segment is still being computed, and PocketPass replaces local membership wholesale on each sync - so a partial read could quietly drop members and change which template a customer's pass uses. Lists have no such caveat.
Campaign Monitor exposes both lists and segments, for every list belonging to the client you nominated - not just the one you sync passes from. Membership refreshes hourly rather than every few minutes: Campaign Monitor limits how fast we can call it, and paging every list and segment more often would crowd out the work that actually gets install links to your subscribers.
ActiveCampaign exposes all three: lists, segments and contact tags. Tags appear alongside segments in the picker, since they do the same job of grouping people. Segment membership is worth one caveat - ActiveCampaign computes segments in the background and serves the result from a cache for up to an hour, so a contact who has just qualified for a segment may take that long to appear in one. Lists and tags are immediate.
HubSpot exposes contact lists in both flavours: static (manually curated) and active (rules-based, HubSpot's closest thing to a saved segment). Both come through and both work everywhere PocketPass targeting does - active lists are labelled to make them easy to tell apart from static ones in the picker.
Omnisend exposes segments. Tags exist too but aren't surfaced as pickable audiences - Omnisend accounts tend to have far more of them than segments, and every contact can carry any number of tags, so listing them all would drown the picker. If you want to target on a tag, build an Omnisend segment against that tag first and use the segment here.
The Mailchimp saved-segment gap
Mailchimp's Marketing API returns tags reliably, but does not expose newer saved segments built in Mailchimp's segment builder. PocketPass asks Mailchimp for saved segments and Mailchimp returns none - so those segments simply can't be imported, no matter how they're named or how many contacts they hold.
If a saved segment you expected is missing from PocketPass, this is why. The fix is to recreate that targeting as a tag. The reliable pattern is a Mailchimp automation that tags every contact matching the condition (for example, "tag lapsed-90d when a contact hasn't ordered in 90 days"). Tags always sync, and they work everywhere PocketPass targeting does - notifications and template rules alike.
Reach for a tag whenever you want a Mailchimp audience that PocketPass can act on. It's the one audience type that never surprises you.
Where these audiences show up
Notification targeting. Open /dashboard/notifications, choose New notification, and look under Who gets this. Your CRM's lists, tags, and segments appear alongside PocketPass's own pass-template and group-tag filters. Pick one to send only to the customers in it. See Choosing an audience for how filters combine, and Sending a notification for the full send flow.
Template rules. The same audiences drive which template a customer is enrolled onto. Map a CRM list or segment to a template and any customer in that audience gets that pass when they enroll. That's covered in Turn customers into passes.
CRM audiences and PocketPass group tags can be used together. A notification can target a Mailchimp tag and a PocketPass group tag at once - the filters combine, so you narrow to the customers who satisfy both.
Keeping audiences fresh
PocketPass re-reads your CRM's audiences on its regular sync, so lists and segments you create in the CRM show up here without any manual import. If something you just built in the CRM isn't listed yet, give the next sync a moment - or, for Mailchimp saved segments, remember the gap above and use a tag instead.
Where to go next
- Choosing an audience - how targeting filters combine.
- Sending a notification.
- Turn customers into passes - using these audiences as template rules.