Intelligems

Set up, inspect, or evaluate Intelligems experiments on Replo pages. Analyze existing Intelligems data and build split URL tests, content variations, or price tests on or including Replo pages.

Use this guide when a merchant wants a Replo page in an Intelligems test, wants variations on one Replo URL, or asks about an Intelligems experience or its results. For site implementation, read the building-replo-pages skill; for local editing and publishing, use the public local-development and publishing skills. Discover the connected Intelligems operations in your available public MCP tools and follow their schemas. If the required operation is unavailable, ask the merchant to provide the experiment IDs or perform that step in Intelligems; do not assume access to internal Replo tools.

To use Intelligems on a Replo site, always install @intelligems/headless in that site and configure its provider and tracking hooks. This applies to on-page tests, Replo URLs in Split URL tests, pricing and custom events. For journeys crossing Replo and Shopify hosts on a shared domain, apply the required 1.2.19 package patch and set its cookieDomain prop, or verify a vendor-fixed release before proceeding.

The connected Intelligems External API token gives management and reporting tools. It does not install visitor assignment or tracking on a published page. First identify the tested origin, each variation URL or section, the store's domain, and whether attribution must include cart and checkout.

During implementation and before publishing, run the code audit against the site source and local dev server. When asked to verify the published setup, or before declaring a test ready for traffic, run the separate live experiment audit. Report the two results separately; a code pass or HTTP 200 alone does not prove order attribution. For quiz, lead, or selected CTA goals, read Intelligems’ headless custom-events documentation. Do not track every click by default.

Replo URL as a variation

1. Publish the Replo destination on a merchant-owned subdomain such as lp.brand.com when the origin is www.brand.com. Intelligems does not support redirect tests or persistent assignment across unrelated registered domains; a *.replosites.com destination will not carry the origin's assignment.
2. Configure an Intelligems Split URL (content/url) experience with the entry page as the origin and the Replo page as a variation destination. The Replo connection can create a pending test shell, but URL routing still needs to be configured in Intelligems. Have the merchant finish those fields in Intelligems before starting the test.
3. Keep Intelligems installed on the origin. Install @intelligems/headless on the Replo destination and configure its provider and tracking hooks. The Replo connection alone does not load a script or SDK. Check existing tags first; do not run the standard Intelligems script and the headless SDK on the same Replo page.
4. In a fresh browser session, visit the origin, follow the redirect, verify the assigned variation and destination page view, complete a test checkout, and verify the order appears under the correct variation. Visiting the destination directly may not join that redirect test.