Thank-you pages

Count a visit to your own thank-you or confirmation page as one conversion (Capture > Rules > Thank-you pages).

Set up

1. The OrcLink script is on the thank-you page (Conversions > Install) and form capture is on.
2. Add a rule: a name, a page pattern and, optionally, URL parameters.
   • Pattern: a path such as /thank-you*, or host and path such as www.clinic.com/booked*. * matches anything (also /). No other wildcards, no regular expressions; at most 4 *; matched in lower case; the query string is not part of the match.
   • Parameters: param=target pairs, targets email, phone, order_id, lead_id, value, currency. Example: oid=order_id, total=value. A value: the value on the page is recorded as a claim; revenue comes from your store, payment or CRM connection (or the revenue API).
3. Check with Capture > Test tool (kind "Thank-you page").

What happens

• With an order (or lead) id in the address: one conversion per visit. The visit's click id or session cookie ties reloads together, and the same order sent with orc.trackConversion on that visit is the same conversion.
• Without an id: one conversion per rule per visitor per day (UTC). A reload, or the browser restoring the tab later that day, is the same conversion and is not sent to ad platforms again. Click and iframe-form events work the same way. A rule that can really happen twice the same day for one visitor (a second booking, a second order) needs an id parameter (order_id or lead_id): each id is its own conversion.
• A visitor with no click id and no session cookie (for example analytics consent refused and no ad click in the address) has nothing that ties two page views together: each page view is a new, unattributed record. It is never sent to an ad platform and carries no revenue (a value in the address is only a claim). For the same reason an order sent with orc.trackConversion on one page and seen again on a thank-you page by such a visitor is recorded twice (with no store or payment source connected, it is counted twice; connect one, so that its order is the one counted). We do not key these records by your site and day instead: anyone could then guess the key.
• An email or phone parameter is read into memory and removed from the address bar (history.replaceState) as soon as the OrcLink script runs, before any consent decision and without a request. It is sent only after advertising consent, and hashed on our server.
• Limit: scripts that ran before the OrcLink script (a tag manager, analytics, a chat widget loaded earlier in the page) have already seen the full address, and the browser may have sent it as a referrer for resources that loaded first. Prefer an order id over an email or phone in the address; load the OrcLink script early in <head>.
• Kind and stage come from your rule, never from the page, except that an order_id parameter makes the conversion an order. An order is an order whatever it is keyed by: a rule of kind order with no order id parameter is an order too. With your store or payment source connected, every browser order is recorded as a duplicate of that source's order (the store's record is the one counted and sent to ad platforms); without one it is counted and sent by click id, with no value.
• If the stage the conversion reaches is set to relay and has a default value, ad platforms receive YOUR default value for that stage, never the number the page sent.

Known limits

• Connecting a store or payment source while a browser order is in flight can send that one sale to ad platforms twice.
• If your store's webhook is broken (the integration shows an error on the Integrations page), its orders are not counted until it works again; the browser copies stay marked as duplicates.