For SponsorsUpdated May 2026

Your Sponsor Resource Library

Maintain reusable resources speakers drop into their fanflets. Branding, attribution, propagation, and per-resource analytics.

What the library is for

Your library is the curated set of resources you want connected speakers carrying into their fanflets. One canonical version lives with you. Speakers pick from it in their Add Block picker and the item lands on the audience page with your branding, your link, and your tracking already wired in.

Update an item in the library and the change flows to every fanflet using it. Archive an item and it stops appearing in new picks while existing placements show a tombstone to the audience.

Plan requirement

The Resource Library is a Sponsor Connect and Studio feature, gated by the sponsor_resource_library flag. Free sponsor accounts see an upgrade prompt on the page. Storage and per-file limits scale with your plan.

Item types

The library holds four kinds of items. Each one renders as a block when a speaker drops it onto a fanflet.

  • File for PDFs, decks, spreadsheets, Word documents, ZIPs, and images. Files upload to a private bucket and serve through signed URLs at download time. The cap is 100 MB per file.
  • Link for any external URL. Use this for landing pages, gated forms, scheduling links, and demo signups.
  • Video for hosted video embeds. Drop in a YouTube, Vimeo, or Wistia URL and the block renders the player inline.
  • Sponsor block for a branded banner with your logo, a short message, and a CTA button. Use this slot when you want speakers placing a thank-you panel at the top of the fanflet.

Adding a resource

Open sponsor library and click New resource. Pick the type, fill in the fields, then either save as a draft or publish straight to your connected speakers.

1

Pick the type

Choose file, link, video, or sponsor block. The form fields adjust to match the type. Files prompt for an upload. Links and videos prompt for a URL. Sponsor blocks prompt for CTA copy and an optional image.

2

Title and description

The title is what speakers see in their picker and what the audience reads on the public page. The description is the short line under the title. Keep both tight. Audiences scan, they do not read.

3

Image and brand assets

Add a thumbnail image to make the item stand out in both the speaker picker and the audience block. For sponsor block items, the image renders inside the banner alongside the CTA.

4

Save draft or publish

Drafts stay private to your team. Publishing flips the item to status published and makes it visible to every connected speaker the next time their dashboard loads.

File quotas

Storage usage and the per-file cap are visible at the top of the library page. Connect plans get the standard quota, Studio plans get a higher quota with larger per-file limits. Run out and the upload form blocks new files until you free space.

Branding controls

Library items inherit the brand fields from your sponsor profile. The logo, accent color, and company name set in your sponsor settings render on every block automatically. You do not configure branding per item.

Per-item, you control the title, description, thumbnail image, and for sponsor blocks the CTA button copy. The audience-facing block uses your sponsor brand wrapper around whichever fields apply to the type.

How connected speakers see your library

When a speaker has an active connection with you, your published items appear in their Add Block picker under a Sponsor Library section. Items group by sponsor first, then by campaign inside each sponsor. Speakers filter by type, search across titles and descriptions, and add an item to the current fanflet with one click.

The picker shows a thumbnail, the type label, the title, and a short preview of the description or URL. Items already placed on the fanflet show an Added badge so the speaker does not double up.

No connection, no library

A speaker with no active connection sees nothing from your library. Pending and declined connections do not grant catalog access. Read connecting with sponsors for the speaker side of the flow.

Attribution and tracking

A block placed from your library auto-attributes to your sponsor account. The speaker does not pick attribution from a dropdown, there is no separate setup step. Clicks, downloads, and lead captures on the block roll up to your sponsor analytics from the first scan.

File downloads run through a server route that signs a short-lived URL after the audience tap. The route also writes a download event tagged to the resource block, the fanflet, and the visitor hash. That event flows into both the speaker's analytics and your sponsor dashboard.

Per-resource analytics

Each library row shows a placement count, the number of times the item is currently dropped onto a live fanflet across your network. Click into the item to open the detail view with impressions, clicks, downloads, and lead captures broken out by speaker and by fanflet.

Use the per-resource view to see which speakers pull weight on a given asset and which assets land hardest with each audience. Studio plans get cross-speaker rollups in the same view.

Updating a library item

Edits to a published item flow to every fanflet using it. Change the title and the new title appears on every audience page on the next render. Replace the file and the next download serves the new version. Update the URL and the link block points to the new target.

The propagation model matches the speaker library. Read dynamic content for the underlying concept and the cases where a placement copies an item versus links to it.

Publishing a draft

A draft item is invisible to connected speakers. Move it to published when you want it in their picker. Publishing also sets the availability to all by default, so every connected speaker sees it.

Restricting an item to specific speakers

Availability on each item is one of three values. All sends the item to every connected speaker. Specific limits the item to a chosen list of connected speakers. Draft hides the item from everyone except your team.

Pick Specific when an asset is tied to a single account, a pilot, or a co-branded campaign. The picker only shows the item to speakers on the list. Remove a speaker from the list and the item stops appearing in their picker on the next dashboard load.

Deleting and archiving

Archive moves the item to status archived. It vanishes from the speaker picker and stops accepting new placements. Existing placements stay on the audience page using the stored copy until a speaker swaps them out.

Remove is the harder action. The item flips to status removed, the file is deleted from storage, and existing placements render a tombstone message to the audience explaining the resource is no longer available. Speakers see a warning on the affected blocks in their editor.

Use archive when the campaign ends but you want existing fanflets to keep working. Use remove when you need the file gone, for legal, compliance, or accuracy reasons.

Removal is permanent for files

A removed file leaves the storage bucket and is unrecoverable from inside Fanflet. If you need the file back, re-upload it as a new library item.

Plan note

Connect plans include the library with standard storage and connection caps. Studio raises the storage ceiling, the per-file cap, the connection cap, and turns on cross-speaker rollups in the per-resource analytics view. Compare both on billing.

Related reading