HeyReach + Midbound integration guide

Table of contents

HeyReach + Midbound integration guide

Published:

April 9, 2026

April 14, 2026

You've spent real money getting people to your website. Some of them are exactly the kind of prospects you'd cold outreach to anyway — right title, right company, right intent. They found your pricing page. They came back twice this week. Three people from the same account were poking around your docs.

And then they just... leave.

Without the right tooling, that signal disappears. You move on, they move on, and nobody ever has the conversation that was clearly worth having. That's the gap this integration closes.

When you connect Midbound with HeyReach, qualified website visitors don't just get tracked — they get reached out to on LinkedIn, automatically, with context. This guide walks you through how to make it work.

The building blocks: What's what?

Midbound is a website visitor intelligence platform built for B2B teams running intent-based outbound. It identifies the real people visiting your site — name, company, role — and captures the behavioral signals that matter: which pages they viewed, how many times they came back, whether multiple people from the same account showed up, and where they came from (ads, organic, GPT search, you name it). Crucially, it doesn't just tell you that someone visited — it tells you why it matters, using ICP filtering, intent scoring, and suppression logic to ensure only the right people make it downstream.

HeyReach is a LinkedIn automation platform built for scale. It lets you run personalized outreach campaigns across multiple LinkedIn accounts, manage sequences with smart delays and conditions, and track every connection request, message, and reply. Whether you're an agency managing dozens of client accounts or a sales team running high-volume prospecting, HeyReach handles the LinkedIn side — safely, efficiently, and at scale.

What they solve together

Without this integration, intent data sits in one place and outreach tooling sits in another. With it:

High-intent visitors become LinkedIn prospects automatically — no manual CSV exports, no copy-pasting between tools.
Your outreach is contextual from the first touch — you know they visited the pricing page, explored your docs, or came in from a paid campaign. That context shapes your messaging.
ICP filtering happens before outreach — Midbound suppresses existing customers, recent contacts, and out-of-ICP visitors before they ever reach HeyReach. You only reach who you should.
Buying group visibility turns into multi-threaded outreach — when multiple people from the same account visit, HeyReach can run coordinated sequences across the whole group.
The loop is fully automated — from pixel fire to LinkedIn message, no human needs to be in the middle.

Setting up the integration

There are three main phases: capturing intent in Midbound, defining your routing rules, and pushing qualified prospects into HeyReach campaigns.

Phase 1 — Install the Midbound pixel and start capturing visitors

Step 1: Install the Midbound tracking pixel

Log into your Midbound account and navigate to Settings → Tracking Pixel. Copy the pixel snippet and paste it into the <head> of every page on your website. If you're using a tag manager (Google Tag Manager, Segment, etc.), you can deploy it through there instead.

💡 Pro tip: Make sure the pixel fires on your highest-intent pages — pricing, demo request, product docs, and case studies. These are the pages Midbound uses to score visitor intent.

✅ Confirmation: Once installed, visit your own site and check the Visitors tab in Midbound. If your session appears within a few minutes, the pixel is working.

Step 2: Verify visitor resolution is working

Midbound uses high-confidence, consent-based identity signals to resolve visitors to real people. Give it 24–48 hours of traffic to validate resolution rates before setting up downstream routing.

⚠️ Watch out: If you're running a staging environment, make sure the pixel is only live on your production domain. Visitor data from staging can pollute your intent feed.

Phase 2 — Define your ICP filters and routing rules in Midbound

This is where you control exactly who gets pushed to HeyReach. Midbound lets you filter on a range of criteria before anyone touches your outreach campaigns.

Step 3: Configure your ICP filters

In Midbound, navigate to Routing and define your inclusion criteria:

Job title / seniority — e.g., VP Sales, Head of Growth, Founder
Company size — e.g., 50–500 employees
Industry — e.g., SaaS, professional services, B2B tech
Geography — limit to regions you actively work

Step 4: Set your intent thresholds

Define what counts as a qualifying visit. Common thresholds include:

Pricing page visit (any visit)
Repeat visits (e.g., 2+ sessions in 7 days)
Account spike (3+ people from the same company in a short window)
Campaign source (e.g., visitors who came in via paid ads or GPT-referred traffic)

💡 Pro tip: Start conservative. It's better to push 20 highly qualified prospects per day into HeyReach than to flood campaigns with noise. You can always loosen thresholds once you've validated the workflow.

Step 5: Add suppression rules

Configure Midbound to exclude:

Existing customers
Leads already in active HeyReach campaigns
Competitors
Any domains on your internal blocklist

🚨 Do not skip this step. Reaching out to existing customers via LinkedIn automation is the fastest way to damage relationships. Midbound's suppression logic is your safeguard — use it.

Phase 3 — Connect Midbound to HeyReach and push qualified prospects

There are three ways to route qualified visitors from Midbound into HeyReach. Choose the one that fits your stack.

Option A — Native API integration (recommended)

This is the cleanest, most reliable path. Midbound pushes prospects directly into HeyReach in real time via the HeyReach API, with retry logic, deduplication, and suppression baked in.

Step 6: Get your HeyReach API key

In HeyReach, go to Settings → Integrations → API and copy your API key.

Step 7: Connect Midbound to HeyReach

In Midbound, navigate to Integrations → HeyReach. Paste your HeyReach API key and authenticate the connection.

Step 8: Map your data fields

Tell Midbound which fields to send to HeyReach. At minimum, you'll want:

LinkedIn profile URL
First name, last name
Company name and role
Intent context field (e.g., "Pricing page visitor — 2 visits in 5 days")

💡 Pro tip: Pass intent context as a custom field in HeyReach. You can use it as a personalization variable in your campaign messaging — e.g., {{intent_context}} — so your outreach references what the prospect actually did on your site.

Step 9: Map prospects to the right HeyReach campaigns

In Midbound's routing logic, specify which HeyReach campaign each prospect segment should land in. For example:

Pricing page visitors → "High Intent — Pricing"
Docs visitors → "Product-Led — Docs Engaged"
Account spike (3+ from same company) → "ABM — Buying Group"

✅ Confirmation: Trigger a test visitor (e.g., visit your own pricing page from a different browser) and confirm they appear in the correct HeyReach campaign within minutes.

Option B — Webhook via middleware (Zapier, Make, n8n, Workato)

If you're not ready for the native API connection, or you want to add logic between Midbound and HeyReach (e.g., enrichment steps, CRM lookups, Slack notifications), you can route through a middleware layer.

Step 6 (Option B): Create a webhook in Midbound

In Midbound, go to Integrations → Webhooks and create a new outbound webhook. Copy the webhook URL endpoint.

Step 7 (Option B): Build your Zap / Scenario / Workflow

In your middleware tool:

Trigger: Midbound webhook fires when a qualified prospect is identified
Action: Add lead to a HeyReach campaign via the HeyReach API action

In Zapier, search for the HeyReach integration and use the "Add Lead to Campaign" action. In Make or n8n, use an HTTP module pointing to the HeyReach API endpoint.

💡 Pro tip: If you're using n8n or Make, this is a great place to add a CRM lookup — check whether the contact already exists in HubSpot or Salesforce before sending to HeyReach, as an extra suppression layer.

Option C — CSV sync (fallback)

If you need to get started before your API or webhook setup is finalized, Midbound can export qualified visitors as a CSV that you import directly into HeyReach.

⚠️ This is a manual process. You'll need to export and import on a regular cadence (daily at minimum). Use this only as a bridge while you set up Option A or B.

Step 6 (Option C): In Midbound, filter your visitors to your ICP/intent criteria and export as CSV.

Step 7 (Option C): In HeyReach, go to the target campaign and use Import Leads → CSV Upload to add the list.

Common workflows

Workflow 1: Pricing page visitor → immediate LinkedIn outreach

A prospect visits your pricing page for the first time. Midbound resolves them to a person, confirms they're in-ICP, checks they're not an existing customer, and pushes them to your "High Intent" HeyReach campaign. Within minutes, a connection request goes out with a message like:

"Noticed you've been exploring our pricing — happy to share some benchmarks or answer any questions before you make a decision."

This is your highest-converting segment. Keep this campaign tight — short sequences, fast follow-up timing.

Workflow 2: Account spike → buying group outreach

Three people from the same 200-person SaaS company visit your site in a 48-hour window. Midbound's buying group detection fires and pushes all three into HeyReach — each into your "ABM — Buying Group" campaign. You run a multi-threaded sequence that reaches each stakeholder with messaging tailored to their likely role (the economic buyer, the champion, the technical evaluator).

💡 Pro tip: In HeyReach, tag all three leads with the company name and use campaign conditions to coordinate timing — you probably don't want connection requests going out to all three simultaneously.

Workflow 3: Repeat visitor → re-engagement sequence

A prospect who visited your site two months ago (and maybe slipped through without contact) is back — and they've now been on your docs pages three times this week. Midbound detects the repeat behavior and pushes them to a "Re-engagement — High Activity" campaign in HeyReach. The messaging acknowledges familiarity without being creepy: "Looks like you've been spending some time in our docs — is there anything I can help clarify?"

Workflow 4: Campaign-sourced visitor → attribution-aware outreach

A prospect arrives via a paid LinkedIn ad, visits your site, and qualifies on ICP. Midbound captures the UTM/referrer source and passes it as a custom field to HeyReach. Your outreach can now reference the ad campaign context, close a loop, or just inform your messaging strategy — giving you real data on which ad audiences convert to pipeline.

Troubleshooting

Visitors identified but not in HeyReach: Check ICP filters in Midbound, verify your API key, and ensure the campaign is active
Duplicate leads in campaigns: Enable deduplication in Midbound and avoid multiple push paths (API + CSV)
Intent context not showing as a variable: Match field names exactly (case-sensitive) and check field mapping
Pixel installed but no visitors resolved: Wait a few days; if still zero, confirm pixel is live and not blocked by CSP
Customer received a connection request: Update suppression list (domain + email) and sync “Closed Won” CRM data regularly

Quick-start checklist

In Midbound:

Pixel installed on production site (all key pages)
Visitor resolution verified (your own session appears in the dashboard)
ICP filters defined (title, company size, industry, geo)
Intent thresholds set (pricing page, repeat visits, account spikes)
Suppression rules configured (customers, competitors, already-contacted)

Connecting Midbound → HeyReach:

HeyReach API key generated and saved in Midbound (Option A) — or —
Webhook configured and middleware workflow live (Option B)
Data fields mapped (LinkedIn URL, name, company, role, intent context)
Prospect segments routed to the correct HeyReach campaigns
Test prospect verified end-to-end (from site visit to campaign enrollment)

In HeyReach:

Target campaigns created and active
Personalization variables set up (including {{intent_context}} or equivalent)
Campaign messaging reviewed for intent-aware framing

That’s it. Every qualified visitor to your site is now one step away from a LinkedIn conversation — automatically, in context, and without anyone having to lift a finger.

Try it for free