CONNECTIONS / monday
monday + Datahash: board status becomes ad signal.
monday CRM has no fixed Opportunity object, only boards, items, and the status columns a team designs itself. Signals reads whichever status change means a deal closed and turns it into conversion events and audiences on the platforms you buy on.
- ● monday :: signals live
- > read items board=sales_pipeline status=won rows=3,140
- > read columns type=status,people,numbers
- hash sha256(email,phone) scope=boards.read
- route meta · google · tiktok · snap
- ✓ 4 destinations synced · match 76%
The signal monday yields, and receives.
Every kind of signal that moves between monday and the platforms, through one hashed, deduplicated route.
- Offline conversions
- A status column change on a deal board, whatever label a team gave it, posts as a conversion event once mapped, no fixed schema required.
- Lead conversions
- Closed-won item value leaves monday hashed and matches back to the campaign that sourced the item.
- Custom audiences
- Contact and company items become hashed, scheduled audiences without an export leaving the board.
- Lead generation inbound
- A status change made by a monday Automation recipe reaches Signals the same way a manual drag between columns would.
Pick your platform. Every use case for it, in one place.
Every way monday data moves, grouped by platform and ranked by how many use cases monday 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 monday with a scoped API token limited to the boards you choose, revocable from account admin at any time.
-
Map columns
Match each board's status column labels, however a team has renamed them, to platform events in the visual mapper.
-
Hash and consent
Hashing and consent checks run before an item leaves monday.
-
Deliver
Mapped destinations receive events on delivery, with per-status match reporting.
monday questions, answered.
monday CRM has no fixed deal stage object. How does mapping work?
The visual mapper reads your actual board structure instead of assuming a schema, since no two monday boards look the same. You point it at the status column that represents your pipeline and match each label, custom ones included, to the platform event it should fire.
We use monday Automations to move items between statuses. Does that still sync?
Yes. Signals reads the resulting status change on the item, not the automation recipe that caused it, so a rule-driven move reaches a destination exactly as a manually dragged item would. Nothing about the mapping changes based on what triggered the update.
Can we sync more than one board, for example separate boards per region?
Yes. Each board maps independently, so regional or team-specific boards with their own status labels and columns can feed the same destinations without forcing every board into one shared structure. A status named Won on one board does not have to match the label on another.
NEXT STEP
See your monday data working in every ad platform.
Ready to enable a use case, or still mapping what monday data could do? Our team helps you find the right place to start.
