EP Lead Source
EP Lead Source tells you which marketing brings you customers. Every enquiry, booking and newsletter sign-up is recorded with where that person came from, and the answer goes straight into the email you already get.
Published by ElmsPark Studio.
Overview
Section titled “Overview”- Every conversion, with its source. EP Email enquiries, EP Booking bookings and EP Newsletter sign-ups.
- Channels you can act on: paid search (Google Ads, Microsoft Ads), AI assistants (ChatGPT, Perplexity, Claude, Gemini, Copilot and others), search, social, email, your own other sites, another site, a tagged campaign, or direct.
- In your enquiry email. A “Lead source” line, such as
Google Ads (paid search) · campaign "spring" · first page /physio/. - In your webhooks. The same line reaches EP Connect’s “Email Form Submitted” trigger, and a new trigger, “Lead recorded, with its source”, carries every detail.
- Back to Google Ads. A click-conversion file Google Ads can fetch on a schedule, or that you download.
- A report in the settings screen, and the same figures for an AI assistant connected over MCP.
Requirements
Section titled “Requirements”- PageMotor 0.11.5 or later.
- EP Email for enquiries. Its JSON forms (the
[ep-contact-form name="..."]kind) are covered, and so are the enquiry forms Page builds, which send through EP Email. The older built-in form is not. - EP Connect for bookings and newsletter sign-ups. It carries those events to EP Lead Source.
- EP GDPR is recommended. EP Lead Source reads the visitor’s cookie choice from its banner.
Installation
Section titled “Installation”ep-lead-source.zipcomes with an EP Suite licence. ElmsPark supplies it directly (see EP Suite plugins); after install it updates through your site’s Updates screen.- Upload via Plugins → Manage Plugins. Activate.
- Open Plugin Settings → EP Lead Source and add your other sites, if you have any.
Nothing else is needed: the source starts appearing on the next enquiry.
How a source is worked out
Section titled “How a source is worked out”A small script on each page looks at how the visitor arrived:
- Campaign tags in the address:
utm_source,utm_medium,utm_campaign,utm_term,utm_content. - Ad click IDs that ad platforms add: Google’s
gclid(andgbraid/wbraid), Microsoft’smsclkid, Meta’sfbclid. - The site they came from.
- The first page they saw.
An ad click ID wins over everything else. Then your own campaign tags count, then the site they came from.
Consent
Section titled “Consent”Remembering where a visitor came from, until they send a form on a later page, needs a cookie.
After consent (the default):
- Campaign details are kept once the visitor accepts Analytics in the EP GDPR banner.
- Ad click IDs are kept once they accept Marketing.
- Only click IDs kept with Marketing consent are ever sent to Google.
Always, without asking keeps both without a banner choice. Use it only where you do not need consent.
A form on the page the visitor landed on gets the source either way, because nothing has to be stored.
Settings
Section titled “Settings”| Setting | What it does |
|---|---|
| Remember the source across pages | After consent (EP GDPR banner), or Always. |
| Your other sites | Visitors from these count as “Your other sites”, not as another site sending you visitors. |
| Add the source to EP Email enquiries | Adds the “Lead source” line to notifications, EP Connect and EP Email Leads. |
| Conversion action name | The name of your “Import” conversion action in Google Ads, spelt exactly as there. |
| Value per lead / Currency | Optional. Sent to Google Ads with each conversion. |
| Feed password | Turns on the scheduled feed for Google Ads. At least 16 characters. |
Google Ads
Section titled “Google Ads”In Google Ads, create a conversion action of the Import kind (“Conversions from clicks”). Then either:
- Download the file from the EP Lead Source settings screen and upload it under Goals → Conversions → Uploads, or
- Schedule it. Save a feed password, then in Google Ads add a schedule with source HTTPS, the address shown in the settings screen (
https://yoursite/ep-lead-source/google-ads.csv), usernamegoogleand your feed password.
The file holds the last 90 days of leads that carry a Google click ID the visitor allowed. Times are in UTC. Google ignores duplicates, so the same lead sent twice counts once.
Google now recommends Enhanced Conversions for Leads, which also matches by email. That is planned for a later version.
EP Connect
Section titled “EP Connect”The Lead recorded, with its source trigger sends: what it was (enquiry, booking or newsletter), the form, service or list, the email address, the channel and source, campaign, keyword, content, the first page, the referring site, the ad click IDs (when allowed), and a one-line summary.
Use it to send leads with their source to a CRM, a spreadsheet or Google Ads through Zapier or Make.
The report
Section titled “The report”The settings screen shows the last 30 days: leads by channel, by source and campaign, and the latest leads with their first page and whether an ad click was kept.
An AI assistant connected to your site can ask the same through two read-only actions, leads-by-source and list-leads.
Personal data
Section titled “Personal data”Each record holds the person’s email address and where they came from. EP GDPR’s data requests include them: an export lists them and an erasure deletes them.
Troubleshooting
Section titled “Troubleshooting”“Every lead says Direct”
Section titled ““Every lead says Direct””Most often the visitor moved to another page before the form, and has not accepted Analytics in the banner, so nothing could be remembered. Forms on landing pages are not affected. Check that EP GDPR’s banner is on.
“Bookings or sign-ups are not recorded”
Section titled ““Bookings or sign-ups are not recorded””EP Connect must be active: it carries those events. Bookings made by staff in the admin are not counted, as they are not marketing conversions.
“Google Ads says the feed cannot be reached”
Section titled ““Google Ads says the feed cannot be reached””Check the feed password is at least 16 characters and matches the one in Google Ads, with the username google. After 20 wrong passwords in an hour from one address, the feed stops answering that address for the rest of the hour.
Feedback and corrections
Section titled “Feedback and corrections”For a quick question about this plugin, EP Support inside your admin is the fastest option. The chat widget sits on every EP plugin settings page and knows which one you’re on, with starter questions and links preloaded for that exact screen.
For anything bigger — a bug report, a feature request, or a “how do I…” that needs a real reply — open a ticket at help.elmspark.com. A real person, helped by AI, writes the reply. Usually within a few hours. Tickets don’t disappear into the void.
Changelog
Section titled “Changelog”- Changing this plugin’s settings over the API now needs an admin token. Producer tokens and AI apps connected through a producer account can still read the settings. Saving from the Admin screen works exactly as before.
- The lead feed password is now stored encrypted. A password you saved before keeps working and is re-saved encrypted the next time the plugin loads.
A security update. Please install it.
- One Google Ads conversion per ad click. The upload file now lists each click once, at its first lead, so resubmitting a form cannot report one click as many conversions.
- Hand an advert’s details to your buy button. Two names your page’s own script can rely on from now on:
window.epLeadSourceCartAttributes()gives a flat list of text values ready to attach to a cart (Shopify cart attributes, for example):utm_source,utm_medium,utm_campaign,utm_term,utm_content,referrer,landing_pageandarrived_at. Ad click IDs (gclid,gbraid,wbraid,msclkid,fbclid,ttclid,li_fat_id) andclicked_atare included only when the visitor accepted Marketing in the EP GDPR banner, or you chose “Always, without asking”. Empty values are left out. Pass a short prefix, such as"_", to put it in front of every name.window.epLeadSourceCurrent()gives everything the plugin knows about the visit. It includes the click IDs from the page address whatever the visitor chose, because the plugin applies consent when it stores a lead; if your script sends them anywhere else, use the cart helper above or check consent yourself. It now returns a copy, so changing it in your script no longer changes what your forms send.
- TikTok and LinkedIn ad clicks are recorded. A visitor who arrives from a TikTok or LinkedIn advert now counts as paid social (“TikTok Ads” or “LinkedIn Ads”), and the click ID is kept with the lead, under the same Marketing consent rule as Google’s. The settings screen, the “Lead recorded” EP Connect trigger and the leads list for your AI assistant show them too. Your existing leads are kept as they are when the plugin updates.
- See which advert brought each lead. The settings report adds two tables for the last 30 days: leads by the page the visitor first landed on, and leads by campaign and
utm_contenttag. With one landing page or oneutm_contentvalue per advert, that is your per-advert result. Your AI assistant can ask for the same through “leads by source”. - Pages built as full HTML documents keep up by themselves. Such a page keeps the head it was saved with, so a plugin your host switched on for you, a plugin update, or a setting changed for you never reached it until someone saved a setting by hand. The plugin now notices on the next visit and updates every such page once. That is also how your existing pages get this version’s helper.
- Nothing changes on themed pages, or where you switch the plugin on yourself in the admin. Requires PageMotor 0.11.5.
- A contact form that sends itself now carries its source too. Some pages send their form from their own script, for example a page an AI wrote for the site. There is then no form field for the capture script to fill.
- The campaign, ad click ID and arrival site were lost on those pages unless the visitor was still on the page they landed on. The script now adds the source to the request itself.
- It touches only enquiry requests to your own site. Searches, other posts and other sites are left alone.
- Nothing changes for forms that already worked. Requires PageMotor 0.11.5.
- Enquiry forms built by Page now carry their source in full. A visitor who lands straight on a Page-built contact page from ChatGPT, Perplexity or another site, with no campaign tags, was recorded as Direct. The form now gets the source like any other.
- Ad clicks and tagged links were already recorded on these forms. Nothing else changes.
- Requires PageMotor 0.11.5.
- See where every enquiry came from. Each EP Email enquiry and EP Newsletter sign-up is recorded with its source: Google Ads, an AI assistant such as ChatGPT or Perplexity, search, social, email, one of your other sites, another site, a tagged campaign, or direct.
- EP Booking bookings too, when EP Connect is active.
- The source goes in the enquiry email. EP Email notifications gain a “Lead source” line, such as
Google Ads (paid search) · campaign "spring" · first page /physio/. The same line reaches EP Connect webhooks and EP Email Leads. - A new EP Connect trigger, “Lead recorded, with its source”, sends the full detail to Zapier, Make or your own endpoint: channel, source, campaign, keyword, landing page, and the Google or Microsoft ad click ID when the visitor allowed it.
- Google Ads can fetch your conversions by itself. Set a feed password in the settings and Google Ads collects a click-conversion file on a schedule. You can also download the file from the settings screen.
- Leads by source, in the admin and for your AI assistant. The settings screen shows the last 30 days by channel, by source and campaign, and the latest leads. Over MCP, an assistant can ask which channels brought enquiries.
- Consent first. Remembering a source across pages needs a cookie. By default, campaign details are kept only once the visitor accepts Analytics in the EP GDPR banner, and ad click IDs only once they accept Marketing. Only those click IDs go to Google. A form on the page the visitor landed on gets the source either way. Data requests through EP GDPR include these records.
- Requires PageMotor 0.11.5.