Skip to main content

​
Frequently Asked Questions

​
Does the Experro pixel / Analytics SDK slow down my site?

No. The SDK bundle is small, served from Experro’s CDN, and loaded asynchronously. It hooks into the page via non‑blocking event listeners and streams events in the background, so it doesn’t pause the main thread or delay your page from rendering.

​
Can we add the SDK before our full product catalog or models are ready?

Yes. You can deploy the SDK at any time. For high‑quality commerce attribution (products, variants, categories, collections), it works best once your catalog and models are wired into the storefront so event payloads contain stable IDs/SKUs. If you only need behavioral tracking (sessions, clicks, custom events), you can start immediately with your tenant, workspace, environment, channel IDs, and app_key.

​
Who is responsible for wiring events on our site?

Experro ships the core tracker and a set of built‑in commerce events. Your team decides where in the codebase to call those events (for example, search results pages, PDP templates, cart components). If you’d like help mapping your UX to the SDK, Experro can provide best‑practice guidance and sample implementations.

​
How does the SDK know when a user searches or adds to cart?

The SDK exposes a queue‑style API (ExpAnalytics.q.push([...])). You invoke the appropriate built‑in keys (such as product_searched, product_added_to_cart, checkout_completed) at the right moments in your UI—for example, after search results load, when an item is added to cart, or when an order completes. The SDK then wraps that payload and sends it to your analytics endpoint with your Experro headers (x-tenant-id, x-workspace-id, x-env-id, x-channel-id, x-channel-locale).

​
Which events are available out of the box?

Experro covers the full shopper journey:
  • Discovery: ac_impression, ac_click, product_searched, search_no_results, ac_zero_impression
  • Browse & PDP: category_viewed, collection_viewed, widget_viewed, product_viewed, product_variant_viewed
  • Cart & Checkout: product_added_to_cart, product_remove_from_cart, cart_viewed, checkout_initiated, checkout_completed
  • Identity: auth_events (change_id, user_details)
  • Custom: Any add_event you define, with your own counts, sums, durations, and segmentation fields.

​
Is anything else required beyond adding the script?

In most cases, no. You include the script tag and initialize it with your IDs and analytics URL. Additional server‑side work is only needed if your Content Security Policy (CSP) currently blocks Experro’s CDN or your analytics endpoint (see the CSP section below).

​
What data is sent from the browser? Do you store PII?

Every event contains an anonymous identifier, timestamp, page URL, your Experro context headers (tenant/workspace/env/channel/locale), and the payload you choose to send (SKUs, facets, totals, etc.). IP information is transmitted for transport and security purposes but can be truncated or discarded according to your data policies. We recommend not sending raw PII inside segmentation; instead, rely on stable user IDs managed through change_id and user_details. Example event payload (request body): 
{
  "key": "product_searched",
  "sum": 24,
  "segmentation": {
    "search_term": "running shoes",
    "search_location": "page",
    "sku": ["RS-001", "RS-002"],
    "facets": [{"field": "size", "value": "10"}],
    "currency": "USD"
  }
}

​
Do we need different snippets for staging and production?

You use the same script bundle in all environments. Environment separation comes from configuration: envId/environmentId, analyticsUrl, and your app key. For testing, point the SDK at a staging base URL and staging environment ID; for go‑live, deploy the same snippet with production values.

​
What storage mechanisms does the SDK rely on?

By default, the SDK uses local or session storage to maintain identifiers and to buffer events if needed. Cookie usage is optional and can be enabled based on your requirements and policies.

​
Should we QA before rolling out to production?

Yes. While the core tracker is well tested, it’s important to verify your specific event hooks. Run through key flows—search, product view, add‑to‑cart, checkout—and confirm that events appear in the browser network panel and within your Experro Analytics dashboards as expected.