The problem
An enterprise technology client running its flagship annual customer conference needed one thing above all: registration and upsell activity flowing into its own Salesforce instance continuously. Manual exports and spreadsheet handoffs weren’t going to cut it — sales and customer-success teams needed to act on conference engagement without waiting on a data pull. The integration originally lived inside the account-management partner’s shared portal on the platform. That worked fine for the partner’s day-to-day operations, but it left the client itself without a dedicated, independent front door into its own event data.
The approach / solution
- Built a bidirectional Salesforce sync service — an auto-sync scheduler, batch logging, and a manual “run sync” trigger — that upserts registration and upsell activity into a purpose-built custom object inside the client’s own Salesforce org. It follows the same pattern used across the platform’s other Salesforce, HubSpot, and NetSuite integrations.
- The client eventually needed independent portal access instead of sharing the account-management partner’s portal. We stood up a new portal on its own dedicated subdomain — a new front door wired to the exact same backend Salesforce-sync module, not a duplicated codebase.
- Both portals stayed live on the same shared backend: the account-management partner’s original portal for its own operations, and the client’s own portal for direct access. One verified integration, two access points.
- Confirmed the live cross-domain connection between the client’s dedicated portal and its own Salesforce environment with a direct CORS check, instead of assuming the sync worked from backend logs alone.
Outcome / result
The Salesforce sync runs in active production against the client’s own Salesforce org. Both portals — the account-management partner’s original one and the client’s own dedicated build — stay live on the same verified backend module. We checked the cross-domain connection between the client’s portal and its Salesforce environment directly. It works.
Why it matters for enterprise event-tech
This is direct evidence of enterprise-grade CRM integration work: a real bidirectional Salesforce sync serving a client’s flagship conference, plus the architectural judgment to extend access to a new portal without duplicating or destabilizing an already-verified integration. That’s the platform-engineering depth an Event-Tech Architect or MarOps Engineer role gets evaluated on.
