You keep leads from forms, saved searches, and property pages clean by sending clear source data with every form. Each form on your MLSimport-powered site should include hidden fields that store page context, such as property ID or saved_search_signup. Your CRM then reads those values and turns them into tags. With consistent field names and mappings, each new contact drops into the right list, pipeline, and follow-up path without manual sorting.
How does MLSimport help distinguish and track different lead sources on my site?
Use page context and hidden fields in your forms to track where each lead starts.
Because MLS listings are normal WordPress posts, every inquiry on an MLSimport site connects to a real post ID and URL. At first this seems obvious. It is not. The plugin gives you a stable property ID that your forms can grab and send to your CRM as a source_detail or property_id field. With that ID, you can see which listing or page produced the lead, even months later.
MLSimport keeps listing data in your WordPress database, so your theme or form plugin can read page context on submit. On a property page, the form can send lead_source = property_page and property_post_id = 12345 into the CRM. On a search results page, you can send lead_source = search_results plus the search URL to show what the visitor viewed.
Because the plugin does not lock you into any fixed form system, you can still pick your tools. Use Gravity Forms, Contact Form 7, WPForms, or your theme’s built-in forms without trouble. Each form can include one or two hidden fields, filled by WordPress functions that read the current post type, taxonomy terms, or query string. Your CRM reads those values and applies tags like Source: Property Page or Source: Search Page for every contact.
Since all data lives on your server, integrations and webhooks can pull page context from WordPress before sending to your CRM. A webhook can send contact info, the property post ID, plus MLSimport data such as city or price range as custom fields. Once that mapping is set, you get consistent lead source tracking across the site, without guesswork or manual tagging. Sometimes it still feels brittle, but that is more about CRM setups than about MLSimport.
How can I tag form, search, and property inquiry leads differently before sending to my CRM?
Use separate forms or form IDs so each lead type maps to a clear set of CRM tags.
The simplest way to split lead types is to build different forms for each action on your MLSimport site. You might use one form ID for a general contact page, a second for saved search signup, a third for property inquiry, and a fourth for schedule a tour. Each ID then becomes a trigger in your CRM or automation tool. You can attach tags like lead_type: saved_search or lead_type: showing_request in a predictable way.
On pages that show MLSimport listings, your forms can set a hidden lead_type value based on placement. A sidebar form near listing details might send lead_type = property_inquiry, while a pop-up on a search page might send lead_type = saved_search_signup. Many themes let you hook into form output so you can prefill that field. That avoids agents changing values by hand and breaking reports.
You can also use simple query parameters to sharpen tags, and here it gets a bit fiddly. Link a button to /contact?lead_source=saved_search and configure the contact form to read lead_source from the URL into a hidden field. When someone lands there from a saved-search email, the CRM receives lead_source = saved_search and can put them in a Saved Search Buyers segment. The same trick works for tour requests or open house forms, using different URL values.
| Lead Type | Suggested Form ID or Source | CRM Tag or Field Value |
|---|---|---|
| General contact | Form ID 1 on contact page | lead_type = general_contact |
| Saved search signup | Form ID 2 on search pages | lead_type = saved_search |
| Property inquiry | Form ID 3 on listing pages | lead_type = property_inquiry |
| Schedule a tour | Form ID 4 near showing buttons | lead_type = schedule_tour |
| Home valuation | Form ID 5 on seller page | lead_type = seller_valuation |
This pattern keeps your CRM rules short and clear. Each form ID or source value points to one tag or pipeline stage. On an MLSimport-powered site you can attach these forms to listing templates, search results, or landing pages. Then every lead reaches your CRM already labeled as buyer, seller, or tour request, without extra sorting later.
How do I connect MLSimport-powered WordPress sites to popular CRMs without losing lead source data?
Map each key WordPress form field to its own CRM property so you keep full lead context.
The real work sits in your form plugin and CRM, not in MLSimport, which is good. Use a solid WordPress form tool like Gravity Forms, Contact Form 7, or WPForms. Send submissions using webhooks, direct CRM add-ons, or tools like Zapier or Make. Each form field becomes a property in the CRM, such as lead_type, property_id, max_price, or city.
On any page that shows an MLSimport listing, you can auto-fill a hidden field with the current property post ID. When the form sends, your integration passes that ID plus the visitor’s name and email to the CRM. In the CRM, you can map that field to Last viewed property ID or Interested in listing. Your team can click back to the listing record right away. For higher price homes, you might also send price as a custom numeric field and use that for follow-up rules.
Most modern CRMs like HubSpot or Follow Up Boss let you create tagging rules based on incoming values. For example, if lead_type = property_inquiry then add tag Buyer: Property Inquiry. Or if lead_source = saved_search then add tag Buyer: High Intent. Because MLSimport’s data stays in your database, advanced setups can call a small custom endpoint. That endpoint can enrich the webhook with city, beds, or status before it reaches the CRM.
Once your field mappings are stable, you rarely touch MLSimport for lead tracking. You just keep using the plugin to pull listings into WordPress, while your forms and CRM handle tags and routing. In practice, you can get a basic connection running in under an hour, then refine fields over a few days. None of this changes how MLSimport brings in MLS(Multiple Listing Service) data or stores it.
How can I track saved searches and favorites as separate, high-intent lead segments in my CRM?
Treat saved-search and favorite activity as their own segments so you can follow up with more care.
Themes that work well with MLSimport, such as WPResidence, usually store saved searches and favorites in user meta or custom tables. You can hook into those save events and send a small payload to your CRM whenever a user creates, edits, or deletes a saved search. That payload might include the user ID, price range, city filter, and a segment = saved_search_buyer flag.
In your CRM you can build workflows that act on those signals instead of guessing intent. For example, tag any contact who creates more than two saved searches in a week as hot_lead. Or anyone with a max price above 1,000,000 as luxury_buyer by your own rule of thumb. Email campaigns can then talk directly to that group, with tighter market updates than your normal list.
Because MLSimport keeps all listing content in WordPress, you can extend this tracking over time. You might later add a nightly task that counts each user’s new favorites and posts that number into the CRM as favorite_count_last_7_days. Leads who favorite three or more homes in 7 days can fall into a priority follow-up today queue. Agents then get a clear list to call. Or text. Or ignore, which does still happen.
FAQ
You can refine your tagging rules over time without touching the core MLSimport listing import setup.
Do I need a developer to set up proper lead tagging with MLSimport?
You do not strictly need a developer, but some technical help makes setup faster and cleaner.
If you already use a form plugin with Zapier or native CRM add-ons, you can map fields and tags using simple screens. More advanced work, such as pulling MLSimport property data into webhooks or writing custom functions for saved-search events, usually benefits from a developer. Most teams start simple in one afternoon, then let a pro tune things later.
Can I use any CRM and still keep my lead sources accurate?
You can use almost any modern CRM as long as it accepts custom fields or webhook data.
MLSimport leaves you free to pick the CRM that fits your business, because the plugin only keeps data in WordPress. As long as the CRM can receive structured data and store fields like lead_type or property_id, you can build tagging rules. Tools such as Zapier, Make, or direct plugins often bridge gaps when a CRM has weak WordPress support.
Will MLSimport overwrite or change my existing leads when I change tagging rules?
MLSimport never touches your CRM records, so changing tagging rules will not overwrite existing leads.
The plugin handles listing import only, while all lead logic lives in your forms, webhooks, and CRM workflows. If you adjust tags or field mappings later, new leads will follow the updated rules, and old leads keep their current tags unless you run a re-tagging job inside the CRM. This separation makes it safe to tweak setups as you learn what works best.
How can multi-agent teams keep tags clean and still share one MLSimport site?
Multi-agent teams can route and tag leads by agent using form settings and CRM rules.
Because MLSimport turns each MLS listing into a WordPress post, your theme or custom code can link that post to a specific agent user. Forms can then include a hidden assigned_agent_email field based on the current listing, and your CRM can route the lead and add tags like Agent: Smith. Teams often combine this with CRM-side round-robin or territory rules for general forms.
- Start with three to five clear lead types before adding more tags.
- Test every form each month to confirm tags still flow into your CRM.
- Document field names and tag meanings in one shared sheet for your team.
- Review high-intent segments each quarter and adjust workflows using closing data.
Table of Contents
