Luria's API surface

Step 1: Load the tag, with the queue lineCopy Anchor Link

<script>window.luria=window.luria||function(){(luria.q=luria.q||[]).push(arguments)}</script>
<script async src="https://luriart.com/snippet.js" data-luria-site="YOUR_SITE_ID"></script>

Put both in <head>. The first line is optional: it lets you call luria(...) before the tag has loaded, and the calls run once it has. Without it, guard every call with if (window.luria).

Two optional attributes on the tag switch on extras:

• data-luria-spa: one page view per route change on single-page apps (React Router, Next.js client navigation, Vue Router). Query-only changes are not new pages.
• data-luria-carriers: stamps the visitor's session ID onto Stripe Payment Links (client_reference_id), Calendly links and inline embeds (utm_content), Typeform links and embeds (hidden field luria_sid) and any form input named luria_sid. That is how a payment, booking or form answer that reaches Luria later by webhook credits the version this visitor saw. A value you set yourself is never overwritten.

Step 2: Record your goalCopy Anchor Link

luria("goal", "purchase", { value: 129.0, currency: "USD", id: "ORDER-1042" });
luria("goal", "lead");

A goal counts as a conversion only when it is your site's main goal (sales, leads, booked calls, app installs). Any other name is kept as a funnel step and never moves a test. Aliases work: call_booked, optin, closed_won, webinar_registered and friends map to the goal they mean.

Pass the order or booking id whenever you have one. A reload, a second call, or your server reporting the same order all land on one conversion, and the server's amount wins.

On Shopify the order webhook is the one purchase source: a goal call there is recorded as a step. The older luria.convert("purchase", 129) still works everywhere.

Step 3: Mark funnel stepsCopy Anchor Link

luria("track", "add_to_cart", { sku: "TEE-BLK-M" });
luria("track", "begin_checkout");
luria("track", "pricing_view");

Names are letters, digits and _ . : -, up to 60 characters. Properties are kept flat: up to 12 keys with string, number or true/false values. Steps feed your funnel view; they are never a test result.

Step 4: Tell Luria who the visitor is (optional)Copy Anchor Link

luria("identify", { email: "jane@example.com", phone: "+14155550100", userId: "u_829" });

The tag hashes each value (SHA-256) in the visitor's browser before anything is sent; the plain email, phone or user ID never leaves the page. Emails are trimmed and lowercased. Phones must be in international format (+ and country code), otherwise they are skipped rather than guessed.

This is what lets a lead or sale that arrives days later from your CRM or payment provider, carrying only an email, credit the version the visitor saw.

Step 5: Send conversions from your server (optional)Copy Anchor Link

curl -X POST https://luriart.com/api/events \
  -H "content-type: application/json" \
  -H "x-luria-key: YOUR_SERVER_KEY" \
  -d '{"site":"YOUR_SITE_ID","session":"VISITOR_SESSION_ID","events":[{"id":"ORDER-1042","type":"goal","goal":"purchase","value":129,"currency":"USD","order_id":"ORDER-1042"}]}'

session is the visitor's session ID: the luria_sid value your form, Stripe client_reference_id or Calendly utm_content carried back (Step 1, data-luria-carriers). With the server key you may send goal, conversion and identify items without a browser origin; exposure and link_visit items are refused with a 403, and the server key adds nothing for other types. Identify items take hex SHA-256 hashes: {"id":"...","type":"identify","email_hash":"<sha256 of the trimmed, lowercased email>"}.

Step 6: Leave exposure aloneCopy Anchor Link

window.luria.exposure(test, arm) is what the tag calls when it shows a version. Calling it yourself with invented values corrupts the numbers the engine promotes and stops tests on.