CONNECTIONS / VTiger
VTiger + Datahash: potentials become ad signal.
Deal stage lives in VTiger's Potentials module while ad platforms optimize on form fills they cannot see past. Signals reads Potentials, Leads, and Accounts and syncs the stages that matter back to Meta, Google, TikTok, and Snap.
- ● vtiger :: signals live
- > read potentials stage=won rows=3,102
- > read leads status=qualified
- hash sha256(email,phone) module=Potentials
- route meta · google · tiktok · snap
- ✓ 4 destinations synced · match 76%
The signal VTiger yields, and receives.
Every kind of signal that moves between VTiger and the platforms, through one hashed, deduplicated route.
- Offline conversions
- A Lead or Potential moving to a qualifying stage in VTiger posts as a conversion event, so campaigns optimize on pipeline movement instead of the first form fill.
- Lead conversions
- A Potential marked closed-won leaves VTiger as an offline conversion carrying its deal value, so ad platforms see the revenue a lead actually produced.
- Custom audiences
- Contact and Account records leave VTiger hashed before delivery, so an audience built from a customer list never exposes a plaintext identifier.
- Lead generation inbound
- Custom fields added to a VTiger module map in the visual mapper by their webservice field name, so a business-specific field reaches a destination without new code.
Pick your platform. Every use case for it, in one place.
Every way VTiger data moves, grouped by platform and ranked by how many use cases VTiger 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 VTiger 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.
VTiger questions, answered.
Which VTiger modules can send events?
Potentials and Leads are the two modules most commonly wired to conversion events, since VTiger tracks deal stage inside Potentials and initial capture inside Leads. Contacts and Accounts also flow through for audience building. The visual mapper reads any module's fields and webservice IDs, so a custom module built on the VTiger platform can feed the same pipeline without extra engineering.
We run a self-hosted VTiger instance. Does that change anything?
No, Signals connects to VTiger's REST API whether the instance is self-hosted or the VTiger cloud edition, since both expose the same webservice endpoints. The integration user and access key are scoped to read-only on the modules selected, and the connection can be revoked from VTiger's own preferences at any time without involving Datahash support.
How does a Potentials stage change reach the ad platforms?
A stage change is read from the Potentials module, hashed, and routed to each connected destination on a near-real-time or scheduled cadence depending on what the platform supports. The live debugger shows per-destination match feedback for that record, so a team can confirm a stage change actually reached Meta or Google rather than assuming the pipe is working.
NEXT STEP
See your VTiger data working in every ad platform.
Ready to enable a use case, or still mapping what VTiger data could do? Our team helps you find the right place to start.
