Prerequisites
Before connecting, make sure you have:- A Leadfeeder account with API access enabled (Leadfeeder Premium or a plan that includes the API)
- Your Leadfeeder API token (available under Profile → API Access in the Leadfeeder app)
- Admin access in your Stairoids workspace
Connect Leadfeeder
Copy your Leadfeeder API token
In Leadfeeder, click your profile icon and navigate to Profile → API Access. Copy the API token shown there.
Open Integration Settings in Stairoids
Navigate to Settings → Integrations and click Add Integration.
Select Leadfeeder
Choose Leadfeeder from the integration catalog. Paste your API token into the API Key field and click Connect.
Choose which visit events to import
Select the visit event types and filters you want Stairoids to import — for example, you can limit imports to visits from companies already in your Stairoids workspace, or import all identified company visits to discover new accounts.
Leadfeeder visit data is polled every 15 minutes by default. If you need real-time visit signals — for example, to trigger an immediate outreach action the moment a target account lands on your pricing page — use the Leadfeeder webhook method instead. Contact support@stairoids.com to enable webhook-based ingestion for your workspace.
Signal types imported
All Leadfeeder visit events are imported aspage_visit signals. Each signal includes the following properties:
| Property | Type | Description |
|---|---|---|
company.name | string | The identified company name |
company.domain | string | The company’s domain (used for account matching) |
pages_viewed | array | List of page URLs visited during the session |
visit_duration | integer | Total session duration in seconds |
referrer | string | The traffic source or referring URL |
visit_count | integer | Number of visits by this company in the past 30 days |
first_seen_at | ISO 8601 | Timestamp of the first recorded visit |
last_seen_at | ISO 8601 | Timestamp of the most recent visit in this session |
How account matching works
When apage_visit signal arrives, Stairoids uses the company.domain field to find a match:
- Existing account match — if an account in your Stairoids workspace already has a matching domain, the signal is attached to that account automatically.
- No match found — if no existing account matches the domain, Stairoids creates a new account record using the company name and domain provided by Leadfeeder.
- Ambiguous match — if multiple accounts share the same domain (common with large enterprise groups), Stairoids flags the signal for manual review in the Unmatched Signals queue.
Troubleshooting
No visitor data appearing in Stairoids
No visitor data appearing in Stairoids
- Confirm the Leadfeeder API token is still valid. If you’ve regenerated your token in Leadfeeder, update it in Stairoids under Settings → Integrations → Leadfeeder → Reconnect.
- Check that your Leadfeeder account has identified visits in the relevant time window. If your Leadfeeder dashboard also shows no identified companies, the issue is upstream — check that your Leadfeeder tracking script is installed correctly on your website.
- Verify your Leadfeeder plan includes API access. Leadfeeder’s free tier does not expose visit data via API.
- Allow up to 15 minutes after reconnecting for the first data pull to complete.
Duplicate accounts being created
Duplicate accounts being created
Duplicate accounts are most often caused by domain inconsistencies — for example, Leadfeeder reporting a company as both
example.com and www.example.com. To resolve this:- Go to Settings → Integrations → Leadfeeder → Matching Rules and enable Normalize domain on match. This strips
www.prefixes before matching. - If duplicates already exist in your workspace, use the Merge Accounts tool under Accounts to consolidate them.
- For companies with multiple subsidiary domains that should map to a single account, add all known domains to that account’s profile under Accounts → [account] → Domains.