Airgentic Help
Airgentic can support common Funnelback-style URLs during migration projects when Funnelback compatibility is enabled for the service.
This feature is a compatibility layer. Funnelback URLs are not the default Airgentic URL format, and not every Funnelback parameter is expected to have a one-to-one Airgentic equivalent.
Airgentic can parse common Funnelback parameters such as:
| Funnelback parameter | Purpose |
|---|---|
query |
Search query text |
collection |
Search collection or service hint |
start_rank |
First result number |
num_ranks |
Number of results per page |
sort |
Sort option |
f.Display|field=value |
Filter using Funnelback facet syntax |
meta_<field>=value |
Metadata filter |
meta_<field>_gte / meta_<field>_lte |
Date or numeric range filter on a Search Field |
meta_url |
URL or host constraint |
scope |
Airgentic search scope (written on new URLs) |
clive |
Funnelback live collection; still accepted as an alias for scope |
Start by allowing Airgentic to read existing Funnelback-style deep links.
Test real URLs from analytics, bookmarks, and search result pages.
Some customers may want Airgentic to continue writing Funnelback-style URLs. Others may prefer Airgentic-native URLs or no URL state.
Basic search:
search.html?query=engineering
Pagination:
search.html?query=engineering&start_rank=11&num_ranks=10
Filter using Funnelback facet syntax:
search.html?query=engineering&f.Format|format=Online
For filter URLs to work, the referenced Airgentic field must exist as a Search Field in Search Configuration > Fields and be enabled as a filter.
Host or URL constraint:
search.html?query=engineering&meta_url=engineering.example.edu
Scope:
search.html?query=engineering&scope=programs
Event date range:
search.html?query=workshop&meta_event_dates_gte=2026-02-01&meta_event_dates_lte=2026-02-28
For range URLs to work, the referenced Airgentic field must exist in Search Configuration > Fields, be enabled as a filter, and have been indexed after HTML Processing (for Date range (events) fields) or the appropriate reprocess job for other field types.
During migration, map the Funnelback field names you want to preserve to Airgentic Search Fields. For example, a Funnelback delivery filter should map to an Airgentic delivery field that is populated from the relevant HTML metadata and enabled as a filter in Fields. Some Search Field and URL compatibility options may initially be configured by Airgentic support.
Use Search Configuration > Scopes to map Funnelback-style scopes or clive values to Airgentic scopes (scope= in the URL; inbound clive= still works). A typical scope filters one page_type value and controls which filters are shown in that tab. Use each scope's Visible toggle to show or hide tabs, including All.
For sorting, common Funnelback values such as date and adate can map to Airgentic date sort options. Other sort IDs can be passed through when matching Airgentic sort options exist for indexed Search Fields.
Funnelback result display rules usually migrate to Airgentic result cards. Use Search Configuration > Result Cards to recreate important result metadata as badges or custom layout blocks.
Existing Funnelback or search-page CSS may also be reusable. See Styling Site Search for the recommended styling layers and selector approach.
Some Funnelback features may need project-specific work, including:
profile behaviourquery_and, query_or, and query_notAirgentic support can help review which Funnelback parameters are used by your current search.