LupaSearch integration

Integration process steps

LupaSearch integration steps

Stage Questions & Steps LupaSearch Customer/ Integrator
Kick-off meeting Challenges and expectations:
# of monthly search sessions (Google Analytics)
of indexed entries, JSON file (field names explained)
# of languages used
# of domains
✔️
Demo #1 Data feed simulation in LupaSearch console ✔️
Feedback for Demo #1 ✔️
Agreement Contract preparation and signing ✔️ ✔️
Demo #2 Data feed simulation in LupaSearch console ✔️
Feedback for Demo #2 ✔️
Integration Integration method selection ✔️
Agreement what data to be indexed to LupaSearch and how often ✔️ ✔️
Front-end integration ✔️
Send search events to LupaSearch ✔️
Back-end integration ✔️
LupaSearch infrastructure preparation ✔️
Product feed preparation ✔️
Pre-configuring basic search settings ✔️
GA Analytics sync for advanced search statistics ✔️
Staging environment preparation ✔️
Validation in staging/testing environment ✔️
Lupasearch console user accounts set-up ✔️
Going live Production release ✔️
Onboarding session ✔️
Results optimization Bugs/improvements identification ✔️
Analytical data monitoring ✔️
Adding synonyms in LupaSearch console ✔️
LupaSearch automatically improves search ranking based on sent events along time ✔️

Integration Kick-off Checklist

  1. Key Contacts & Communication
  • Who are the key people for communication during integration?
  • Who will be the main contact for ongoing support after go-live?
  1. Business Goals & KPIs
  • What are your main business goals for implementing LupaSearch? (e.g. improve search conversion, decrease zero-results, increase average order value (AOV), enhance UX speed)?
  • Do you have baseline metrics? (e.g. current search conversion rate, Average order value (AOV) from search, Search speed or latency)
  • What are your target KPIs post-integration?
  1. Project Scope & Context
  • What is the full project scope (B2C, B2B domains)?
  • List all languages to be supported?
  • What is the estimated go-live date?
  1. Integration Method & Complexity
  • What is the preferred integration approach?
    • What is the preferred integration approach for products syncronization? (API / plugin for supported e-shop platforms / feed file synchronization)
    • What is the preferred integration approach for the front-end? API / plugin?
  • Are there any special implementation details to consider (e.g. different prices for customer groups, potential limitations due to selected integration method)
  • Product feed format
  • Use of LupaSearch for catalogue pages in addition to search (for performance and UX improvements)
  1. Data & Volume
  • What is the total product/SKU count per domain?
  • How frequent are data updates?
    • Scheduled imports (frequency, times)
    • Real-time updates (expected latency, triggers)
    • Approximate number of updates per day
    • Do your products have dynamic attribute fields added frequently?
    • Should new attributes be automatically included in search or filterable fields?
  • What are the languages in your store?
  1. Dashboard Access
  • Please provide a list of user emails for account setup.
  1. Merchandising & Ranking Strategy
  • Can you provide sales history data (e.g. product sales volume) for initial ranking optimisation before LupaSearch gathers live behavioural data?
  • What merchandising rules should we implement during the initial setup? For example:
    • Should out-of-stock products appear at the end of search results?
    • Should new products be prioritised at the top of search results?
    • Should sales or promotional products be boosted?
    • Any other specific ranking rules or business logic to reflect (e.g. margin attribute)?
  1. Analytics & Data Quality
  • Do you have internal IP addresses that should be excluded from analytics tracking (e.g. employees, warehouse, agencies)?
  1. Testing & Environments
  • What are the testing environment details?
  • Number of environments available (e.g. DEV, STAGE, UAT, PROD)
  • What is the testing process expectation? LupaSearch team would like to be included in the testing phase.
  • [For plugin] Will our LupaSearch script be supported in your system architecture (e.g. Angular compatibility)?
  • Are there any technical restrictions or requirements we should know in advance?
  1. Third-Party Integrations
  • Are there other third-party tools that interact with your product catalogue or search? (e.g. PIM, ERP systems, recommendation engines)
  1. Legal & Data Compliance
  • Are there any specific agreements with your product vendors or brands that affect how products are displayed in search or category pages? For example certain brands can only show their own products in results, with no alternative brands displayed.
  • Are there any specific industry regulations or legal requirements that we need to consider for your business (Omnibus directive)? For example pharmacy regulations restricting the display or searchability of certain products (e.g. prescription-only medicines, age-restricted items).
  1. Design & Front-end Implementation [OPTIONAL]
  • Do you have an internal design team involved or do you expect full design implementation support from LupaSearch?
  • What are the design expectations?
    • Desired front-end design outcomes
    • Approval process for design implementation (who approves, how, and estimated timelines)
    • Are there specific UI/UX requirements or brand guidelines to follow?
    • What are the realistic design possibilities based on the provided product feed structure and data availability?
    • Are there any desired customizations or dynamic components on search pages?

Contacts for assistance: [email protected]