Personalization Methods and Data Sources

Personalization in Flint happens at two levels:

• •Visitor-level: Adapt what a visitor sees based on who they are or how they arrived (query parameters, IP identification)
• •Page-level: Generate a dedicated page for each account, prospect, or segment (CSV upload, Clay, Relay.app, Airtable, PDF, A/B testing)

The methods below are not mutually exclusive. Many teams combine them -- for example, using Clay to generate pages at scale and then passing query parameters for additional per-visitor customization.

Personalize what visitors see based on values passed in the URL. For example, linking to yoursite.com/demo?company=Acme can render "Welcome, Acme!" in the headline without creating a separate page for that account.

Best for: Campaign tracking (UTM), light per-visitor personalization, passing attribution data into form submissions.

Data sources: Any system that can append URL parameters -- ad platforms (Google, Meta, LinkedIn), email tools, marketing automation.

Key features:
- UTM parameters pass automatically to Google Analytics and GTM
- Hidden form fields can capture parameter values for CRM attribution
- Ad platform click IDs (gclid, fbclid, msclkid) are preserved for conversion tracking

Read the Query Parameters docs

Identify which companies are visiting your pages without requiring them to fill out a form. Tools like RB2B, Clearbit Reveal, 6sense, Demandbase, Leadfeeder, or ZoomInfo match visitor IP addresses to company databases and send the results to your CRM or sales team.

Best for: Surfacing buying intent, triggering sales outreach when target accounts visit, enriching CRM records with page visit data.

Data sources: Visitor IP addresses matched against provider databases -- no form submission required.

Key features:
- Identifies company name, domain, industry, and company size
- Integrates with Salesforce, HubSpot, Slack, Outreach, and Salesloft
- Added via a lightweight head script in Flint's Custom Code settings

Read the IP-Based Identification docs

The fastest way to bulk-generate personalized pages inside Flint. Upload a CSV with one row per account -- including company name, a short page description, and account-specific context -- and Flint generates a fully branded, personalized page for each row.

Best for: Sales and marketing teams that maintain a target account list and want branded ABM pages without writing code.

Data sources: Any spreadsheet you can export as a CSV. Common sources include Salesforce, HubSpot, Outreach, or a manual account list.

Key features:
- Launch directly from the Flint dashboard or AI chat using Prompt Templates
- Use an existing page as the template or let Flint design one from scratch
- Add any number of columns to pass richer context and further personalize each page

Read the ABM Workflow Play guide

Connect Clay's prospect enrichment capabilities to Flint's page generation API. Add a company domain to a Clay workbook and the workflow automatically enriches the record with company data, then calls the Flint API to generate a personalized landing page -- with outbound email copy included.

Best for: Outbound sales teams running high-volume personalized campaigns who already use Clay for prospect research.

Data sources: Clay's built-in enrichment (company data, industry signals, contact information) combined with any other enrichment columns you add to the workbook.

Key features:
- Pre-built Clay workbook template to duplicate and configure
- Webhook callback delivers the generated page URL back into Clay
- Auto-generates personalized outbound email copy alongside each page
- Test with a small batch before scaling to hundreds of prospects

Read the Clay + Flint guide

After a sales call, Relay.app automatically picks up the transcript from Attio and passes it to Flint. Flint reads the transcript -- what pain points came up, which features were discussed, what the prospect cares about -- and generates a personalized follow-up page. The result is a unique URL you drop into your follow-up email instead of linking to a generic homepage.

Best for: Sales teams that record calls and want to send tailored follow-up pages instead of generic decks or emails.

Data sources: Sales call transcripts stored in Attio, triggered automatically when a new transcript is saved.

Key features:
- No manual work after the call -- the page is generated automatically
- Personalization is grounded in what was actually discussed, not just account firmographics
- Works end-to-end with Relay.app's workflow builder

Read the Relay.app Follow-Up Pages guide

Every time a new prospect is added to your CRM, Relay.app kicks off a workflow that researches the company, pulls LinkedIn posts from key contacts, generates personalized ABM talking points with AI, and calls the Flint API to create a custom landing page -- then posts everything to a Slack channel for your sales team.

Best for: Teams that want a fully automated ABM system where pages are ready before reps even reach out.

Data sources: CRM records from Attio, HubSpot, or Salesforce as the trigger, enriched with web research and LinkedIn data.

Key features:
- Trigger on any new CRM record, with optional filters for company size or funding stage
- AI research steps enrich the page with LinkedIn posts, company background, and ABM techniques
- Slack notification delivers the page URL and a personalized playbook to the sales team

Read the Relay.app CRM Records guide

Manage Flint pages directly from an Airtable spreadsheet. Each row represents one page, and four button-triggered scripts handle the full lifecycle -- create, publish, and unpublish -- through the Flint API. Teams that prefer a spreadsheet-style interface over the Flint dashboard can use Airtable as their primary page management layer.

Best for: Operations teams or agencies that manage many pages and prefer a tabular view with structured data columns.

Data sources: Airtable rows, where each column can hold any page data or metadata you want to pass to Flint.

Key features:
- One row per page with button-triggered scripts for create, publish, and unpublish
- No-code setup using Airtable's Scripting Extension
- Full lifecycle management without opening the Flint editor

Read the Airtable Page Generator guide

Upload any PDF to the Flint AI chat and ask it to turn the document into a landing page. Flint reads the content -- datasheets, one-pagers, case studies, event agendas, brochures -- and generates a fully designed page that matches your brand.

Best for: Repurposing existing sales and marketing collateral as web pages without manually reformatting content.

Data sources: Any PDF document you can upload to the Flint chat.

Key features:
- Works with any PDF: datasheets, case studies, one-pagers, event agendas, brochures
- Flint extracts structure and content automatically and maps it to your brand's design system
- Review, refine, and add images before publishing

Read the Create a Page from a PDF guide

Run controlled experiments across your Flint pages using third-party testing platforms. Connect Statsig, LaunchDarkly, or Eppo to serve different page variants to different visitor segments and measure which version drives more conversions.

Best for: Growth and CRO teams that want to test headlines, layouts, CTAs, or entire page designs against each other.

Data sources: Visitor segments defined in your testing platform, with variant assignment handled client-side.

Key features:
- Works with Statsig, LaunchDarkly, and Eppo
- Variant logic lives in your testing platform; Flint renders the page
- Combine with query parameters for additional segmentation

Read the A/B Testing docs