For SponsorsUpdated May 2026

Sponsor Leads and Campaign Attribution

Where leads come from, the Leads inbox, campaigns, the analytics tag, and CRM reference fields.

How leads reach your inbox

Every block you attribute to your sponsor account is wired to capture leads. When an audience member opts in to a speaker's fanflet and then engages with one of your blocks, Fanflet records a lead and attaches the full context to it. You see the lead in your Sponsor dashboard within seconds of the engagement.

A lead is not a raw click. The audience member must already be a subscriber on the speaker's fanflet, which means they entered an email address and granted consent. Anonymous traffic stays anonymous.

Plan requirement

Lead capture turns on at the Sponsor Connect tier and up. Campaigns, analytics tags, and the CRM reference editor are Sponsor Studio features. CRM integrations like HubSpot and Zapier sit on Studio as well.

Which interactions create a lead

The track endpoint records a lead when three conditions hold at once: the visitor is a known subscriber, the engagement targets a specific resource block, and the engagement falls into one of three event types.

resource_click the audience member taps a sponsor-attributed link block.
resource_download they download a sponsor-attributed file or PDF.
info_request they submit an info-request form on a sponsor-attributed block.

Page views, QR scans, and bot traffic do not create leads. Subscriber opt-ins land in the speaker's subscriber list first, and roll up to your dashboard once they touch a sponsor-attributed block.

The Leads inbox

Open Sponsor → Leads to see every lead attributed to your account, newest first. Each row shows the audience email, name, fanflet, speaker, resource title, engagement type, and timestamp.

The filter box matches across email, name, fanflet title, and speaker name in real time. Use it to slice leads by a single fanflet or by one speaker without leaving the page.

The Export CSV button pulls every lead in your account into a single file with seven columns: Email, Name, Fanflet, Speaker, Resource, Engagement, Date. Hand the file to your sales team or load it into your CRM.

Lead status lifecycle

Leads are append-only records of an engagement event. The inbox tracks one row per qualified interaction, so the same person hitting two of your blocks produces two leads under one subscriber. The audit lives in Fanflet. Status changes live in your CRM after the lead syncs across. Pair the two with the analytics tag to keep both sides aligned.

What context every lead carries

A lead is a snapshot of the moment of engagement. It carries the fields your CRM needs to score, route, and follow up.

The audience email and display name from the subscriber record.
The fanflet title where the engagement happened.
The speaker who carries the block on their fanflet.
The specific resource block, with its display title.
The engagement type (resource_click, resource_download, or info_request).
The timestamp of the click, download, or form submit.
The active campaign names and analytics tags at the time of capture.

Campaigns: scoping attribution

A campaign groups related leads under one name so you see them as a set. Campaigns hold a name, an optional description, a start date, and an optional end date. Status is one of draft, active, or ended.

Open the campaigns page

Go to Sponsor → Campaigns and click New campaign.

Name the campaign

Pick a short, recognizable label like Spring 2026 Launch. Set a start date and an end date if the push has a hard cutoff.

Pick the speakers in scope

Toggle All speakers to include every connected speaker, or pick a subset. Leads from blocks placed on those speakers' fanflets roll up under this campaign.

Add an analytics tag (optional)

Set a value like q2-2026-launch. The tag flows into webhook payloads and CRM contact properties for segmentation.

Set the status to active

Activate the campaign so new engagements attach to it. Move it to ended when the push wraps.

CRM reference: key-value pairs

The CRM reference editor on a campaign holds up to ten key-value pairs. Each pair flows out with every lead webhook so your downstream systems pick up the right contact properties without a separate lookup.

A common pattern: store your HubSpot campaign ID, your Salesforce source code, or a UTM parameter set on the campaign itself.

hubspot_campaign_id = abc123
salesforce_source = fanflet-spring-2026
utm_medium = speaker-event

Keys are limited to 100 characters, values to 500. The full payload arrives in your integration along with the lead context.

The analytics tag

The analytics tag is a short string set on the campaign and stamped onto every lead captured during its active window. The HubSpot integration writes it to the fanflet_campaign_tags contact property so you segment lists, build views, and trigger workflows from one field.

Allowed characters: letters, numbers, spaces, hyphens, underscores, dots, colons, and slashes. Maximum 200 characters. Pick something a marketing analyst reads at a glance.

Speaker-level vs resource-level attribution

Every lead carries two attribution keys at once. The speaker key is the speaker who hosts the fanflet where the click happened. The resource key is the specific block the audience member touched. Slice your leads by either dimension.

Speaker view: which of your connected speakers drives the most leads. Compare conversion across the network.
Resource view: which asset (the case study, the demo video, the calendar link) closes the most engagements.

The filter on the leads page covers both. The CSV export keeps both columns so your CRM or BI tool segments however you need.

From inbox to CRM

The Leads inbox is the source of truth inside Fanflet. To move leads into your sales motion, connect an integration. Each lead fires a lead.captured event. Connected integrations receive the payload within seconds.

HubSpot integration upserts contacts by email and writes Fanflet fields (source, speaker, sponsor ID, event type, campaign names, campaign tags, resource name) to a dedicated property group.
Zapier integration sends the same payload to any Zap. Route it to Salesforce, ActiveCampaign, Mailchimp, or a Slack channel.

Test the end-to-end loop

Subscribe to one of your speakers' fanflets with a personal email, then click a sponsor-attributed block. The lead lands in your inbox immediately. If you have HubSpot or Zapier connected, the same lead appears there, with the campaign name, analytics tag, and CRM reference pairs attached.