The control map
What each button on your site means, learned from what followed a click, never from its words.
On this page
The control map says what each button and link on your site means, so "clicked 'ADD TO CART'" becomes "clicked the add-to-cart button", and the funnel, the click comparison and the visit sentences speak in roles instead of strings. Nothing in it reads meaning from the word on a button.
A control, as an agent sees it
Browser agents do not see CSS. They read the accessibility tree and address a control by its role and its accessible name, the way Playwright's getByRole("button", { name: "Add to cart" }) does. So a control's identity in Parlox is exactly that: its accessibility role, its accessible name (computed as browsers compute it), and its structural path with sibling positions removed, so the same button on every product card is one control. Digits in a name are collapsed, so a cart badge is one control at every count. Names are masked like all other text. (Up to version 1.0.3, a control wrapping a larger block could carry that block's text as its name; since October 16, 2026 Parlox drops such names on arrival: Masking.)
Roles
add to cart, buy now, go to checkout, place order, choose a variant, quantity, apply a discount, search, filter or sort, navigation, account or sign-in, close a popup, cookie consent, CAPTCHA, other.
Where a role comes from
In order of trust. A decision of yours overrides all of them, and is never overwritten.
- Learned from confirmed events. A click followed within two seconds, on the same page, by a confirmed cart, checkout or search event (from the store's cart API, your
track()calls, the data layer or Shopify's pixel), or a form submit followed within a minute by a purchase from your server or Shopify's pixel, names the control. It needs at least two such follows, making up at least a third of the control's clicks, so one accidental click never names a button. - Platform markup. The exact hooks platforms document: Shopify's
/cart/addform andname="add"button, WooCommerce'ssingle_add_to_cart_buttonand#place_order, Magento's#product-addtocart-button, BigCommerce's#form-action-addToCart, Squarespace's.sqs-add-to-cart-button, quantity fields, consent banners, search forms and CAPTCHA containers. A button that only says "Buy" gets nothing from this source. - AI suggestion, awaiting your confirmation. For a control clicked at least three times that neither source above could name, an AI model proposes a role from what an agent sees of it. Below a fixed confidence the control stays unlabelled. A suggestion is shown to you as a suggestion, and counts only once you confirm it. Which model, and what it is sent: Which features use an AI model.
- You. In the Friction view's What each control means panel you can set, confirm or reject any role. "Not a funnel control" takes a control out of the funnel logic.
Learned and platform roles count at once; AI suggestions count only after you confirm them.
When it runs
The map is refreshed every ten minutes for every verified site whose browser part reported a visit in the last day, from the last two weeks of clicks. A site that is not verified has no control map, and no suggestions are made for it. With AI features turned off in the site's settings, the map is still learned from confirmed events and platform markup, and no AI suggestions are made (which features use AI).
Where roles appear
- The Friction view's click comparison labels each control with its role.
- Visit sentences say "the add-to-cart button" instead of quoting its text.
A custom store with no confirmed events and no platform markup keeps its controls unlabelled until you name them or confirm a suggestion; its visits still show the clicked text.