CONNECTIONS / Capsule
Capsule + Datahash: get a small CRM talking to ad platforms.
Capsule keeps a sales pipeline simple, with opportunities moving through tracks and contacts organized by tag. Signals reads that activity and turns pipeline movement and contact lists into conversion events and audiences on every platform you advertise on.
- ● capsule :: signals live
- > read opportunities track=sales stage=won rows=964
- > read parties tag=customer
- hash sha256(email,phone) scope=opportunities.read,parties.read
- route meta · google · tiktok · snap
- ✓ 4 destinations synced · match 74%
The signal Capsule yields, and receives.
Every kind of signal that moves between Capsule and the platforms, through one hashed, deduplicated route.
- Offline conversions
- An opportunity reaching the won stage of its track posts as a conversion event, so campaigns optimize on a closed sale rather than a form fill.
- Lead conversions
- Closed-won value attached to the opportunity reaches the ad platform as a valued offline conversion tied to the campaign that sourced it.
- Custom audiences
- Contact tags leave Capsule hashed and become scheduled audience segments, so a tagged list stays live instead of a one-time spreadsheet export.
- Lead generation inbound
- Custom fields on a Capsule opportunity or contact travel with the event, so a detail specific to your setup still lands where you need it.
Pick your platform. Every use case for it, in one place.
Every way Capsule data moves, grouped by platform and ranked by how many use cases Capsule supports.
- Offline conversions Google Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Offline conversions Google Store Sales Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Google Enhanced Conversions for Leads Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Google Customer Match Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Google Forms Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions Meta Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Meta Conversions API for CRM Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Meta Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Meta Lead Ads Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions Snapchat Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Snapchat Leads Conversions API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Snapchat Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Snapchat Lead Generation Ads Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions TikTok Offline Events API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions TikTok CRM Events API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences TikTok Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation TikTok Lead Generation Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions LinkedIn Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions LinkedIn Leads Conversions API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Lead generation LinkedIn Lead Generation Forms Campaign lead submissions created as records in real time, deduped before creation.
From authorization to delivered signal.
-
Connect
Connect with a scoped Capsule API token, revocable any time.
-
Map tracks
Map opportunity tracks and contact tags to platform events in the visual mapper.
-
Hash and consent
Identifiers are hashed and consent flags applied before anything leaves Capsule.
-
Deliver
Delivery runs on a schedule, with per-destination match reporting.
Capsule questions, answered.
Capsule is simpler than most CRMs we've connected. Is that a problem?
No, a smaller object model is usually faster to map, not harder. Capsule's opportunities, tracks, and parties cover the same conversion signals a larger CRM would, and the mapper works the same way regardless of how many custom objects a system has. Most Capsule setups take less time to configure than a CRM with dozens of custom fields.
How does Capsule's tagging system map to audiences?
Any tag applied to a party in Capsule can be pointed at an audience segment in the mapper, and membership updates as tags are added or removed. That means a manually curated list, like past customers or newsletter subscribers, turns into a synced audience without a recurring export step.
Do you support multiple pipelines, or just one track?
Capsule supports multiple tracks per account, and Signals maps each one independently, so a sales track and a separate renewals track can feed different events or the same one. You choose the mapping per track during setup, and it can be revised later without disrupting what is already live.
NEXT STEP
See your Capsule data working in every ad platform.
Ready to enable a use case, or still mapping what Capsule data could do? Our team helps you find the right place to start.