CONNECTIONS / Zithara
Zithara + Datahash: repeat buyers become ad signal.
Store visits, orders, and loyalty activity sit inside Zithara while ad platforms only see the first click. Signals reads that retail activity and syncs repeat-purchase and redemption events back to Meta, Google, and TikTok.
- ● zithara :: signals live
- > read orders channel=pos+online rows=1,964
- > read loyalty_events type=redemption
- hash sha256(phone,email) scope=customers.read
- route meta · google · tiktok
- ✓ 3 destinations synced · match 74%
The signal Zithara yields, and receives.
Every kind of signal that moves between Zithara and the platforms, through one hashed, deduplicated route.
- Offline conversions
- A POS or online order captured in Zithara posts as a purchase event, so campaigns see the sale a store visit or a click actually produced.
- Lead conversions
- A redeemed loyalty reward leaves Zithara as a repeat-purchase signal, letting ad platforms tell a returning customer apart from someone buying for the first time.
- Custom audiences
- A segment built on Zithara's RFM filters becomes a scheduled, hashed audience, so recency and frequency thresholds set inside Zithara decide who is included without a manual export.
- Lead generation inbound
- Phone numbers and emails captured across WhatsApp, Instagram, and in-store channels leave Zithara hashed, so no plaintext identifier crosses into a destination.
Pick your platform. Every use case for it, in one place.
Every way Zithara data moves, grouped by platform and ranked by how many use cases Zithara supports.
Google 5 
Meta 4 
Snap 4 
TikTok 4 
LinkedIn 3 
OpenAI 1 - 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 Zithara with a scoped, reversible integration user.
-
Map
Select the records and stage changes to sync, and map fields in the visual mapper.
-
Verify
Choose destinations and verify sample events in the live debugger.
-
Go live
Go live with per-destination delivery status and match rate reporting.
Zithara questions, answered.
What Zithara data can become an ad signal?
Store visits, POS and online orders, and loyalty point redemptions are the events most retail brands on Zithara send as conversions. A repeat purchase or a redeemed reward can be mapped to its own event, so campaigns learn the difference between a first-time buyer and a returning customer instead of treating every checkout the same way.
Can we build audiences from RFM segments?
Yes, any customer segment built in Zithara, including RFM-based groups, can be scheduled as a hashed audience on Meta, Google, or TikTok. The segment definition stays inside Zithara, so updating the recency or frequency thresholds automatically changes who is included the next time the audience syncs, with no separate export step required.
Does this work for offline, in-store purchases?
Yes, that is the primary use case, since Zithara captures POS transactions and store visits alongside online orders in one customer record. An in-store purchase is read the same way as an online order and hashed before delivery, letting ad platforms optimize toward buyers who convert in a physical store as easily as ones who convert on a website.
NEXT STEP
See your Zithara data working in every ad platform.
Ready to enable a use case, or still mapping what Zithara data could do? Our team helps you find the right place to start.
