Integration Guides
- Bayut → Bitrix24: capture options, reference mapping, community routing
- Dubizzle → Bitrix24: sales vs leasing routing, duplicate storms on launches
- Property Finder → Bitrix24: lead types, listing context, response SLAs
- Meta Lead Ads → Bitrix24: real-time delivery and campaign attribution
- Website forms and WhatsApp: closing the non-portal capture gaps
The Normalization Layer
Portal payloads differ, so we normalize before CRM: phone numbers to E.164, references matched against your inventory (SPA) where one exists, sources standardized, raw payloads preserved as attachments. This layer — PortalSync in our product terms — is why a portal format change becomes an alert to fix, not a week of silently lost leads.
After normalization, routing and automation are portal-agnostic: one set of assignment rules, one first-touch flow, one response-time dashboard across every source.
Choosing an Integration Method per Source
Use an official API or lead feed wherever a portal offers one: it is the most reliable and carries the most data. Where only email notifications exist, structured email parsing works well if the parser is monitored, because portals change email formats without notice. For ad platforms, use real-time webhooks rather than scheduled exports, so speed-to-lead is not limited by a sync interval.
Whatever the method, every source should pass through the same normalization layer, so a Bayut lead and a Meta lead look the same to routing rules and reports.
Testing Before Go-Live
- Send test leads from every source and confirm field mapping
- Send the same lead twice and confirm de-duplication
- Confirm routing for each project, community, and language rule
- Break a credential on purpose and confirm the failure alert fires
- Check that the source survives conversion from lead to deal