How to create a webhook integration

Last updated: April 20, 2026

A webhook lets you automate Influ2 notifications to your CRM or third-party tools. It's perfect if your CRM isn't directly integrated with Influ2 and you want to get real-time alerts when prospects engage with your ads.

What is a webhook?

Think of a webhook like a motion sensor camera. Instead of constantly checking to see if a package has arrived at your doorstep, the sensor automatically sends you a notification when someone approaches. Similarly, a webhook lets one app notify another app when an event happens and what to do next. It's a way to automate processes and get real-time results.

Why use a webhook in Influ2?

Most teams set up webhooks to automate notifications when their CRM isn't directly integrated with Influ2.

Set up a webhook

  1. In your Influ2 account, go to SettingsIntegrations.

  2. Click Webhook.

  3. Make sure Send notifications in the upper-right corner is toggled on.

  4. Enter your webhook URL. This comes from any third-party automation platform you use (e.g., Zapier, Workato) or from your engineering team.

  5. Check which metrics (actions) you want to trigger notifications:

  • Clicks: Sends a notification when a target clicks an ad

  • Visits: Sends a notification when a target visits a website page from an ad

  • Impressions: Sends a notification when a target reaches a certain impression threshold (e.g., 20)

  • Prioritized for sales: Sends a notification when a target reaches the "Prioritized for sales" step of a Journey

  • Goals: Sends a notification when a target interacts with a key CTA on the website page

  1. For each metric selected, click Test to verify the connection.

  2. Repeat the same process to add Buying group notifications.

Keep in mind: The only metrics available for buying group members are Clicks, Visits, and Impressions.

  1. When you're done, click Save settings in the upper-right corner.

What you'll receive

Influ2 sends webhook payloads in real-time for events and once per day for aggregated metrics. Here's what data you'll get:

  • Target events: Clicks, visits, impressions, prioritized status, and goal hits include target details (name, email, company, title, LinkedIn URL), engagement details, and timestamps.

  • Target metrics: Sent once per day for each target, including impressions, clicks, visits, goals, and last-seen ad information.

  • Buying group metrics: Sent once per day for each company, including impressions, clicks, visits, and goals.

Metric type

What Influ2 sends

Target metrics
Once per day, Influ2 sends aggregated metrics about each targeted prospect.

{
"Target Id": "a0de71999edeba38a697f56f2e7b4039",
"First Name": "Donavon",
"Last Name": "Kerluke",
"Title": "IT Consultant",
"company_id": "97f2eb47843646d792f5438087a9b86d",
"Company Name": "Green Leaf Industries",
"email": "Donavon_Kerluke@influ2",
"Linkedin": "https://linkedin.com",
"account_owner_email": "TQyGrTv@SFBiQey.net",
"impressions": 39,
"impressions_30": 86,
"clicks": 4,
"clicks_30": 1,
"visits": 3,
"visits_30": 2,
"goals": 0,
"last_clicked_ad_id": "9595b0bd11e046f1a782cb7a4378b12a",
"last_clicked_campaign_name": "dolorem",
"last_seen_ad_name": "eum",
"last_seen_ad_link": "https://v2.influ2.com",
"last_clicked_ad_name": "excepturi",
"last_clicked_ad_link": "https://v2.influ2.com",
"first_impression_date": "2025-01-17",
"last_impression_date": "2025-01-17",
"first_click_datetime": "2025-01-17T12:17:57.790003218Z",
"last_click_datetime": "2025-01-17T12:17:57.790003218Z",
"last_visit_datetime": "2025-01-17T12:17:57.790003218Z"
}

Buying group metrics
Once per day, Influ2 sends aggregated metrics about each targeted prospect.

{ "company_id": "6e73e1cf11d64d64a3dd36f71f2343c9", "Company Name": "Blue Horizon", "impressions": 44, "impressions_30": 20, "clicks": 2, "clicks_30": 4, "visits": 2, "visits_30": 1, "goals": 1, "first_impression_date": "2025-01-17", "last_impression_date": "2025-01-17", "first_click_datetime": "2025-01-17T12:21:18.373024565Z", "last_click_datetime": "2025-01-17T12:21:18.373024565Z", "last_visit_datetime": "2025-01-17T12:21:18.373024565Z" }