Sponsor Lead Export
Generate per-sponsor lead reports from branded activations. Each sponsor at an event gets their own filtered set of leads from their specific Komo cards.
Use Case
You're running an event with multiple sponsors. Each sponsor has their own branded Komo activations — Sponsor A has a trivia card, Sponsor B has a spin-to-win, Sponsor C has a poll. After the event, each sponsor needs a report of the leads who engaged with their activation — not everyone else's. You need to segment and export leads by sponsor.
Approach
The key pattern is: sponsor-branded cards → tagged entries → filtered export. Each sponsor's activations are separate cards. Entries are automatically scoped to the card they came from. Workflows, manual exports, or the API can filter by card or tag.
Sponsor A Card ──► Entries tagged "sponsor-a" ──► Export: Sponsor A Leads
Sponsor B Card ──► Entries tagged "sponsor-b" ──► Export: Sponsor B Leads
Sponsor C Card ──► Entries tagged "sponsor-c" ──► Export: Sponsor C LeadsImplementation Steps
1. Create Sponsor-Branded Cards
In the Komo Portal, create separate cards for each sponsor. Name them clearly (e.g., "Sponsor A Trivia", "Sponsor B Spin-to-Win"). Each card can have its own branding, cover image, and data capture form. The card itself serves as the natural segmentation boundary.
2. Tag Entries by Sponsor
Use Komo Workflows to automatically tag contacts when they engage with a sponsor's card:
Workflow: Tag Sponsor A Leads
- Trigger: Gameplay.DataCaptured (scoped to Sponsor A's card)
- Action: Update Contact → Add tag "sponsor-a"
Repeat this workflow for each sponsor. Tags make it easy to filter contacts in the portal and via the API.
3. Export Options
There are multiple ways to get the per-sponsor lead data out of Komo:
Option A: Manual Export from Portal
Go to Contacts in the Komo Portal, filter by tag (e.g., "sponsor-a"), and export as CSV. Quick and simple for one-time reports.
Option B: Workflow to Sponsor's CRM
Create a workflow that triggers on the sponsor's card and sends the data directly to the sponsor's CRM or webhook endpoint. Real-time — leads flow as they're captured.
Option C: API Export
Use the Komo API to programmatically pull contacts filtered by tag or card. Automate the export on a schedule or trigger it from your own system.
4. Workflow: Route Leads to Sponsor Webhook
For real-time lead delivery to sponsors, set up a workflow that forwards data to their endpoint:
Workflow: Route Sponsor A Leads
- Trigger: Gameplay.DataCapturedQualified (scoped to Sponsor A's card)
- Action 1: Update Contact → Add tag "sponsor-a"
- Action 2: HTTP Request → POST to sponsor's webhook URL with contact data
Key Pattern
The core pattern for sponsor lead segmentation:
┌───────────────────────────────────────────────────────────┐
│ Competition entries are scoped by card │
│ │
│ Card A (Sponsor A) ──► Entries A ──► Tag "sponsor-a" │
│ Card B (Sponsor B) ──► Entries B ──► Tag "sponsor-b" │
│ Card C (Sponsor C) ──► Entries C ──► Tag "sponsor-c" │
│ │
│ Filter contacts by tag → Export per-sponsor report │
└───────────────────────────────────────────────────────────┘Tips
Naming convention: Use consistent tag formats like sponsor:acme-corp or sponsor:brand-name. This makes API queries and portal filtering predictable.
Multi-sponsor engagement: A single contact can interact with multiple sponsor cards. They'll get multiple tags. Each sponsor's export will include them — this is usually what sponsors want (their reach).
Extension data: If you're embedding cards in an event app, set extension data with the sponsor ID. This flows into webhook payloads and can be used for additional segmentation.