SG5 InsightHub

External services

This plugin connects to the InsightHub service, a cloud service operated by SG5 Digital Solutions, to provide AI-powered search, search analytics, chat, reviews, lead capture and abandoned-cart recovery. The plugin cannot provide these features without it: the matching, ranking and AI responses are produced by the service, not in WordPress. An InsightHub account and API key are required.

All requests go to over HTTPS. Nothing is transmitted until you enter an API key and switch on the feature that sends it — every feature below is off by default.

What is sent, and when:

• Connecting your site — your site URL, site name and administrator email address, sent once when you connect the plugin to an InsightHub account and whenever it verifies the API key.
• Search — sent on a front-end search when Search Tracking or Search Refinement is on: the search term, the number of results, a snapshot of the matching products and content, the page number, and the visitor’s IP address. An anonymous visitor id, or a logged-in customer’s id, name and email address, are included only when the corresponding settings and visitor consent allow.
• Content sync — sent when you save or delete a post, page or product while sync is on: its title, URL, content, and for products the price, stock, attributes and variations.
• Orders — sent at checkout when order tracking is on: order total, currency, line items, the order id, and the customer’s name, email address, phone number, company, billing and shipping address, and IP address. When conversion tracking is on, the customer’s browser identification (user agent) is included as well, so InsightHub can link the order to the visit it came from.
• Abandoned carts — sent when cart capture is on and the shopper has consented: cart contents and the shopper’s email address, so the service can send a recovery email. The resolve call exchanges a token from that email for the saved cart.
• Post-purchase banner — sent when a shopper answers the banner: their answer and the related order id. When the banner is shown, the survey or form embed script is loaded from the service and a shopper who opens the survey or form submits their answers to it; a form receives the order’s email address, name and order number through its personal link.
• Form leads — sent when a visitor submits a Bricks or Elementor form carrying the InsightHub action: the fields you mapped, which typically include the name, email address, phone number, website and message, plus the page and campaign the submission came from and the visitor’s IP address. When conversion tracking is on, the visitor’s browser identification (user agent) is included as well.
• Campaign visits — sent on page load for pages carrying such a form, while conversion tracking is not set up: an anonymous visitor id, the page URL, the referring URL and any UTM parameters.
• Conversion tracking — when the Conversion tracking setting is on: the plugin reads your site’s conversion settings from InsightHub (the API key only, cached for 10 minutes). If those settings count visits or link clicks, the InsightHub script is loaded on every page and sends each visit — the page URL, the referring URL and any UTM parameters — and clicks on the links you track as goals (WhatsApp, phone, email, booking, download, outbound or your own). When WhatsApp chats are linked to visits, links to your WhatsApp number add a short reference code to the message the visitor sends. How a returning visitor is recognised is chosen in InsightHub: without cookies (by IP address and browser identification), for the browser tab only (a session cookie), or with a cookie set only after statistics consent.
• Reviews — sent when the [sg5ih_reviews] shortcode renders: your public widget id, to retrieve approved reviews for display.
• Chat widget — when the widget is on, its script is loaded from the service and shopper messages are processed by it.
• Booking calendar — when the Booking calendar setting is on, on pages that use the [sg5ih_booking] shortcode, the InsightHub booking block or the InsightHub booking element in Bricks or Elementor: the plugin asks for your site’s booking pages (the API key only, cached for 10 minutes), and the embed script is loaded from the service to show the booking page from book.sg5.biz. A visitor who books enters their name, email address and the details the form asks for on that page, which belongs to the service.
• Forms — when the Forms setting is on, on pages that use the [sg5ih_form] shortcode, the InsightHub Form block or the InsightHub Form element in Bricks or Elementor: the plugin asks for your site’s published forms (the API key only, cached for 10 minutes), and the embed script is loaded from the service to show the form from insighthub-gateway.sg5host.com. A visitor who sends the form submits the details it asks for to the service, together with the address and campaign parameters of the page it sits on.

About the service, its terms and its privacy policy:

• InsightHub product information
• Terms and conditions
• Privacy policy
• Data processing agreement (Art. 28 GDPR)
• Legal notice