SearchStax Source

Open Sources in app

Use this page to send on-site search activity from your SearchStax search experience into Ours Privacy. Once search and result-click activity flows in as events, you can build audiences like "searched more than 3 times" and optimize campaigns around what visitors are looking for.

This is a web-based source: SearchStax search activity happens in the visitor's browser, and the Ours Privacy Web SDK captures it directly from the page — no server-to-server connection required.

---

Before you start

• A live SearchStax search experience embedded on your site (the SearchStax search widget or a SearchStax-powered search page).
• The Ours Privacy Web SDK installed on the same pages, or the Ours Privacy Tag Manager.
• A web source in Ours Privacy to receive the events.

---

Setup

SearchStax publishes each search and result click to a global _msq queue on the page. You forward those interactions to Ours Privacy by wrapping that queue and calling ours('track', ...).

1. Add a tag via the Ours Privacy Tag Manager (or paste the snippet into your own tag manager / page), set to fire on the pages where SearchStax search runs.

2. Forward search activity to Ours Privacy. Wrap the SearchStax queue so every interaction is also sent as an Ours Privacy event:

   // Forward SearchStax search activity into Ours Privacy
   (function () {
     window._msq = window._msq || [];
     var originalPush = window._msq.push.bind(window._msq);
     window._msq.push = function (interaction) {
       try {
         // interaction[0] is the SearchStax action (e.g. a search or a result click);
         // interaction[1] carries the query and result details.
         ours('track', 'SearchStax ' + interaction[0], interaction[1] || {});
       } catch (e) {}
       return originalPush(interaction);
     };
   })();

   This keeps SearchStax's own analytics working and mirrors each interaction into Ours Privacy.

3. (Optional) Capture the search box directly. If your search page does not use the SearchStax widget's tracker, listen for search submissions and result clicks on the page instead, and send them with ours('track', 'Search', { query: '...' }). This is more durable because it does not depend on SearchStax's internal queue.

4. Verify by running a search on your site and confirming the events appear in your Ours Privacy source's recent events.

---

Event types

You'll typically capture search submissions and search-result clicks, along with the query text and result context SearchStax provides. Configure how each maps to your event names and properties in the app when setting up your mappings.

---

Next steps

• Web SDK Source - the underlying script that captures these events.
• Tag Manager - manage the forwarding tag without code changes.
• Data Mapping - shape search events into the names and properties you want.

Need help?

Contact support@oursprivacy.com if you need help connecting SearchStax.