Five fields on an import task restrict it to one agent or one office: ListAgentKey, ListAgentMlsId, BuyerAgentMlsId, ListOfficeKey and ListOfficeMlsId. Which of them work depends on your MLS, because feeds differ in what they populate.
Start by finding out which identifiers your feed actually carries. Filtering on a field your MLS leaves empty returns nothing, and looks identical to a wrong identifier.
Find the identifiers your feed uses
The reliable method is to import one known listing and read the values off it.
- Find one listing belonging to the agent and copy its MLS number.
- Create an import task with a single filter: ListingId set to that number. Leave every other filter empty.
- On the Select Import fields tab, make sure
ListAgentKey,ListAgentMlsId,BuyerAgentMlsId,ListOfficeKeyandListOfficeMlsIdare among the imported fields. They can be marked private so they never show publicly. - Run the import, then open the imported property in wp-admin and read the values in its custom fields.
- Note which ones hold a value. Those are the identifiers you can filter on.
A typical result has some fields filled and others blank. A feed might return a long hexadecimal ListAgentKey and a short office code in ListOfficeMlsId, while leaving ListAgentMlsId empty. In that case filter by ListAgentKey, and treat the empty fields as unavailable on that MLS.
Keep the single listing task after the discovery run. Clearing ListingId and entering the identifier you found converts it into the production task, and you have already proved the fields exist in your feed.
Listing agent and buyer agent are separate tasks
A listing carries the listing agent in one field and the buyer agent in another. A single listing is rarely both, so a task filtered on a listing agent identifier and a buyer agent identifier at once returns zero results. Every filter has to match at the same time.
- Task one filters on ListAgentMlsId or ListAgentKey. It returns the listings where that agent represented the seller, across the statuses you selected.
- Task two filters on BuyerAgentMlsId only. It returns the transactions where that agent represented the buyer.
Two tasks give two counts that add up correctly. One task with both fields set gives zero, which reads like a broken connection and is not.
Excluding an agent or an office
Four fields exclude instead of include: Exclude listings with ListOfficeMlsId, Exclude listings with ListOfficeKey, Exclude listings with ListAgentMlsId and Exclude listings with ListAgentKey.
The main use is separating tasks that would otherwise collide. If one task imports your own office by ListOfficeMlsId, add that same value to the exclude field of your general market task. Each listing then belongs to exactly one task, which keeps the agent assignment and the counts consistent.
Build one task per agent when you are creating agent pages. Counts that disagree with the agent’s own totals almost always come from a listing that an earlier, broader task imported first and still owns.
If it does not work
- The task finds zero listings. Remove every filter except the agent identifier. If the count is still zero, that field is empty in your feed. Go back to the single listing method and read which fields have values.
- The count is far lower than expected. Check Select Status. A task set to
Activeonly will not count that agent’s pending and closed transactions. - The agent’s page shows listings owned by another task. The listing was imported first by a broader task. Delete those properties from the Tools tab and re-import them with the agent specific task.
Frequently asked questions
Where do I get the agent or office identifier if importing a listing is not an option?
Ask your MLS. They issue the values and can tell you which identifier your feed publishes for agents and offices. We cannot look them up, because they belong to your MLS account rather than to the plugin.
Does filtering by agent create an agent profile on my site?
No. The filter decides which listings are imported. Whether a property links to an agent profile depends on your theme and on the agent settings of the import task.
Can one task import two agents?
Not through these fields, since each takes one value and all filters must match together. Create one task per agent, which is also the setup that keeps counts and assignment correct on agent pages.
The office filter works but the agent filter does not. Is that normal?
Yes, it happens often. Feeds vary in which identifiers they populate, and office fields are filled more consistently than agent fields on some MLSs. Filter by office and, where you need one agent, narrow further with a status or city filter.
Related
- Controlling which listings are imported
- Avoiding overlapping import tasks
- Title format, property status and owner
- What an import task is
If the identifiers are populated and the task still returns nothing, send us the task and we will run the query against your feed.