Lead Sources

Overview#

Lead Sources is where you connect the places your leads come from: your website, Meta lead ads, webhooks and more. Connect a source once and new leads arrive in Gene App on their own.

Lead Sources is its own item in Settings, next to Calendars and Communication, with one tab per source: Website, Meta Ads, Google Lead Ads, TikTok Lead Ads, Portals and Webhooks. This page covers them; Google Lead Ads, TikTok Lead Ads and Portals also have their own pages: Google Lead Ads, TikTok Lead Ads and Portals.

The channels you message leads on (WhatsApp, Email, Messenger, Instagram, Telegram, Phone, CloudTalk and Providers) are a separate item, Settings > Communication, covered in Communication channels. Until October 2026 both were one item called Integrations, and CloudTalk was a Lead Sources tab; old links to it open its tab under Communication. See CloudTalk.

Each tab only shows when its area is enabled for your account, so your page may have fewer tabs than this list. Portals (JamesEdition) is off by default and appears only when Gene Support switches it on.

Where things live#

• There is no Sources, Ad Accounts or Tracking tab.
• Each network's tab holds both its lead-ad connection and its ad account.
• The tracking script lives on Website.
• Your custom email sending domain lives on the Email tab under Connect your domain.

Every card is named after the thing you are connecting, the way that product names itself. Where more than one route connects the same product, the provider follows it: WhatsApp via Meta, WhatsApp via Twilio, WhatsApp via 360dialog.

Connecting versus what Gene says#

Connecting a source is a one-time job, which is why it lives in Settings. What Gene App then says to a lead from that source (the welcome flow, the language rules, the per-source Gene AI switch and routing) stays under Flows > Inbound. The Connected sources note at the foot of each lead-source tab links you there.

Website tab#

The Website tab holds everything your site feeds in: the tracking script, plus Google Analytics and URL Redirects where those are enabled for your account.

The tracking script puts a small script on your site so visits and form fills flow into Gene App:

• Page views land on the matching contact's timeline.
• Form submissions create a contact automatically (or match an existing one) from the submitted email or phone.
• Forms are captured when they contain an email or phone field.
• Password fields are never captured.
• Visitors, page views, top pages and where visitors came from add up on the Website card in Analytics.

The tab has three sub-tabs: Installation, Settings, and Troubleshoot. This tab is the only place the snippet lives. Flows > Inbound > Website links here rather than showing its own copy, so there is one script, one set of install instructions, and one place to change what it captures.

Install on WordPress#

1. On the Installation sub-tab, under On WordPress?, click Download plugin.
2. In WordPress, go to Plugins, Add New, Upload Plugin, and upload it.
3. Click Activate. There is nothing to configure, and it survives a theme change.

What the plugin does:

• It adds the tracking script to every page.
• It sends every entry from Gravity Forms, Elementor Pro forms, Contact Form 7 and WPForms to Gene App from your site's own server. A lead still arrives when the visitor's browser blocks scripts (ad blockers, privacy browsers, cookie tools).

If someone else looks after your site, copy the link under the button and send it to them. It downloads the same plugin with no Gene App login.

Note

Installed the plugin before October 2026 (version 1.0)? It only adds the script. Download it again and upload it over the old one (WordPress offers Replace current with uploaded) to get form capture on your server.

Install the script by hand#

• Tracking Script: the embed snippet (it carries your unique tracking ID) with a Copy button.
  • Paste it on every page you want to track, ideally just before the closing body tag.
  • Keep every data- attribute exactly as written. They stop cookie-consent and caching plugins (Cookiebot, CookieYes, Complianz, WP Rocket, Cloudflare Rocket Loader) from holding the script back, which would lose leads without any error.
  • The install check reports a tag without them as outdated.
• Let your AI agent install it: Copy prompt copies a ready install instruction, with your snippet in it, to paste to whoever builds your site.
• Events Tracked: on/off toggles for the two event types, Page Views and Form Submissions.

Check the install#

Check now (on the Installation sub-tab) opens every website your workspace runs and reports each one separately: the sites saved under Allowed Domains, the sites visits have come from this week, and the sites where the WordPress plugin has checked in. A site that has gone quiet is still checked. It says in plain words what it found:

• live
• missing from the page
• an older version of the tag
• a tag that reports to a different Gene App workspace

For a site that runs the WordPress plugin, the answer also gives the plugin version, when it last checked in, and how many form entries it delivered in the last 30 days. If the plugin has gone quiet, it says so and asks you to check it is active in WordPress.

You do not need to save domains first. When none are saved, the check looks at visits that arrived in the last week, names each site they came from, and opens those sites. If visits are arriving but a site cannot be opened, it still tells you the tracker works there.

The quickest way to confirm an install: press Check now under Installation, or open the Troubleshoot sub-tab, visit your site in another browser tab, and watch for the page view to appear within a few seconds.

Form capture on your server#

This card on the Installation sub-tab shows one row per site running the plugin (version 2.0 or later). Each row shows:

• when it last checked in
• how many form entries it delivered in the last 30 days
• how many of those arrived only through the plugin, because the visitor's browser blocked the script
• entries waiting on the site to be sent again

Until a site checks in, the card says it is not connected yet.

If the row turns red, the site counted entries that never reached Gene App, and the row says how many. They are still in your form plugin, and the Gene team is alerted.

If a site has not checked in for over two days, it gets a warning. Check that:

• the plugin is still active in WordPress
• the site is on your allowed domains
• you uploaded the plugin again, if you regenerated the tracking ID

Settings sub-tab#

• Allowed domains: restricts which hostnames may send events with your tracking ID. Leave it empty to accept events from any domain. A hostname you type is added when you press Enter, click Add, or click out of the box.
  • If the WordPress plugin sends from a site that is not on the list, its form entries are held on that site for three days and arrive once you add the domain. The Gene team is alerted.
• Regenerate tracking ID: mints a new ID.

Warning

Regenerating the tracking ID stops every existing install until you paste the new snippet. Visits and form fills the script sends to the old ID in the meantime are not kept.

On WordPress after regenerating, download the plugin again and upload it over the old one, without deleting the old one first. The plugin holds the form entries it could not deliver for three days, so they still arrive.

Troubleshoot sub-tab#

• Installation Status: a live panel showing the last page view, the last form submission, and the event count for the past 24 hours.
  • It refreshes every few seconds while the tab is open. Select Check now to refresh immediately.
  • Form entries the WordPress plugin sends count there too.
• Recent Events: the latest paths as they arrive, a few seconds after each visit once the script is installed.
• If nothing arrives: make sure the snippet is on every page you track, just before the closing body tag; test in a private window with extensions off, since ad blockers can stop the script loading; and check the site is on your allowed domains, if you set any.

Cookie banners and ad blockers#

Cookie banners. If your site runs a cookie banner from Cookiebot, CookieYes, Complianz or OneTrust, the script follows the visitor's answer:

• Until they accept analytics or marketing cookies, it stores nothing on their device and records no page views.
• A form somebody fills in and sends is always captured.
• A site without one of those banners works as before.

Ad blockers. Visitors running an ad blocker are captured too:

• With the default filter lists in uBlock Origin and Brave, the script's page views and form submissions get through, so a lead who browses with one of those switched on still arrives.
• A stricter list can still stop the script from loading at all. That is why testing with extensions off is the first troubleshooting step.
• On WordPress, the plugin closes that gap for forms, because it sends each entry from your server and the visitor's browser never sees that send.

How the WordPress plugin sends form entries#

• No slowdown. The send happens after your site has already answered the visitor, so forms are no slower.
• Retries for three days. If Gene App cannot be reached, or turns the entry away because of a setting (the site is not on your allowed domains, or the tracking ID was regenerated), the entry waits in a small queue on your site. It is retried for three days, so it arrives once that is fixed.
• Deleting the plugin clears that queue. To update or reinstall it, upload the new zip over the old one.
• Daily check-in. The plugin checks in once a day, so a site that stops sending is noticed rather than read as a quiet week.
• Left out: entries the form plugin marks as spam, password fields and file uploads.
• Field names. Each answer arrives under the question the form shows. A Gravity Forms field with no label is named by its admin label, or else its placeholder (plugin 2.0.1 or later), so it does not show as "Input 6" on the contact.
• Works alongside the script. The script keeps running: it records page views and catches forms the plugin cannot see, such as another form builder. When both deliver the same submission, Gene App pairs the two copies, so it becomes one lead, not two.
• The Form Submissions switch applies to the plugin's entries too. While it is off, they are not captured.

How answers show on the contact#

The script sends the label your page shows for each field, hidden fields included (a property page's URL or project name, for example), so on the contact each answer reads the way your form asked it. Answers that are only the lead's name, email or phone are not listed a second time.

Google Analytics and URL Redirects#

These cards sit on the Website tab, where enabled for your account.

• Google Analytics: track website views, sessions, and conversion events from Google Analytics 4, for the Marketing and Ad Performance widgets on your dashboard.
• URL Redirects: a table of short links (Short URL with copy, Destination, Status, Clicks, Created) and an Add a Redirect button.

Meta Ads tab#

• Meta Lead Ads: Connect Meta opens the Facebook popup. Pick your Page and the lead forms to subscribe to, and new leads arrive on their own. Where your account uses Gene's managed Meta connection, this is a single Facebook approval instead, made by whoever manages your Page (copy the link and send it to them if that is not you). The connection can take a few minutes; you can close the window, and the Page shows up on the card once it is ready.
  • Once a Page is connected, the card lists every connected Facebook and Instagram lead source: the Page name, how many forms Gene listens to (or All forms), how many leads have arrived, and a badge (Connected, Paused, Check connection or Needs attention). The button then reads Connect another Page (with the managed connection it stays Connect Meta). The welcome flow, language and Gene AI for each source are still set in Flows, Inbound.
  • Each Page row has a Disconnect button. After a confirmation, new leads from that Page stop coming into Gene App and the Page leaves the card. The contacts and conversations it already brought in stay, and so does the source on Flows, Inbound (as Paused). When no other source uses the Page, Gene also asks Meta to stop sending its leads and forgets the Page's lead ads access. Only lead ads stop: Messenger, Instagram messages and posting on that Page keep working. To take leads from it again, use Connect another Page (or Connect Meta) and pick the same Page.
• Meta Lead Ads via Zapier or Make: Set up gives you a connection link for a Zapier or Make scenario, for when you would rather not log in with Facebook here.
• Meta Ads account card (where ad accounts are enabled): auto-sync ad leads, manage DMs, and handle reviews and comments across your Facebook Page and Instagram. It also feeds the Marketing and Ad Performance widgets on your dashboard.
• Meta Conversions API (where enabled): sends your warm, hot, booked and won leads (and the pipeline stages you pick) back to Meta, each as its own event. See Meta Conversions API.

Webhooks tab#

The other ways leads arrive from somewhere else:

• Webhook: Create webhook gives you a URL that a form builder, a landing page tool, a connector like Zapier or Make, or your own system can POST leads to. See Lead webhook.
• Property portals (where enabled): Zillow, Idealista, ImmobilienScout24 and other portals that email or post their leads.
• CSV import: a spreadsheet or a Meta Ads export, imported once.

Portals tab (JamesEdition)#

Shown only when switched on for your account, with its own setup on the tab: an on/off switch, the API token field, and once a token is saved Remove token, Sync now and the sync status. See JamesEdition.

Tips#

• Connect a lead source here once; change what Gene App says to those leads under Flows > Inbound.
• Looking for where to plug something in? Open the tab named after it: Website for your site's forms, Meta Ads for Facebook and Instagram lead ads, Webhooks for anything else that can send a lead.
• On WordPress, use the plugin rather than pasting the script: form entries then arrive even from visitors whose browser blocks scripts. To test it, submit a form on the live site; it shows up within a minute.
• Place the tracking script on every page with a form. If nothing arrives, press Check now, test with ad blockers off, and check that the site is on your allowed domains list (or that the list is empty).
• Which tabs you see depends on what is enabled for your account.

---

Details#

When each lead-source tab shows, and the few controls not covered above, for when you need to look something up.

When each tab shows#

• Website: where website tracking, the website form, URL redirects or ad accounts are enabled for your account. Where website tracking is not enabled, the tab holds a Website card whose Connect website opens the form webhook setup instead of the tracking script.
• Meta Ads: where Meta lead ads, the managed Meta connection or ad accounts are enabled.
• Google Lead Ads and TikTok Lead Ads: where each is enabled for your account.
• Portals: where JamesEdition is enabled. It is off by default.
• Webhooks: where the custom webhook, property portals or CSV import are enabled.
• None of them: there is nothing to connect, so the Lead Sources item does not show in Settings at all. Communication always shows.

There is no Sources, Ad Accounts, URL Redirects or Tracking tab. Old links to those sections open the tab that holds that content now.

Cards and buttons by tab#

• Website: each row of Form capture on your server also shows the plugin version and the site's form plugins. The Google Analytics card shows where ad accounts are enabled, and URL Redirects where redirects are enabled.
• Meta Ads: with the managed Meta connection, a single managed Connect Meta replaces the Meta Lead Ads and Meta Lead Ads via Zapier or Make cards. The Meta Ads account card shows where ad accounts are enabled.
• Webhooks: each card has one button. Webhook has Create webhook, Property portals has Connect portal, and CSV import has Import CSV.