Documentation Integrations

Sale without the visitor identifier

Use this page when a Hubla or Lastlink sale shows in Events without the source of your visit, or when the Node records the purchase_without_stuid diagnostic. It explains what the sale loses, where the identifier usually gets lost and what you can check.

The visitor's identifier is the STUID: a 32-character code the Node assigns to the visitor the Loader identifies. With Hubla and Lastlink, it travels from the browser to the platform inside the checkout link and comes back to the Node in the sale notification. See Connect Hubla and Connect Lastlink.

What the purchase_without_stuid diagnostic is

The Node records purchase_without_stuid when it saves a sale (purchase) or a refund (refund) without the visitor's identifier and cannot recover one. It is one record per transaction, with the transaction id, the platform (hubla or lastlink), the value, the currency and whether the notification carried an e-mail or a phone.

The sale is still recorded, with its value and its buyer. Without the identifier, it loses:

  • The source session: the visit, the campaign and the page that brought the buyer.
  • Meta's external_id: Supreme only ever sends the visitor's identifier as external_id, never a CPF, a document or an e-mail. Without it, the sale goes to Meta with no external_id.
  • The visit's fbp and fbc.
  • The source URL.

When the Node still links the sale back: if the buyer's e-mail or phone was already seen by the Node together with an identifier (for example, on a lead form tracked by the Loader before the purchase), the Node uses that visitor's identifier, recovers that visit's data, and the diagnostic is not recorded. For a cold buyer, whose first contact is the checkout itself, there is nothing to link back to.

First: was the checkout link decorated?

This is the fastest check. Open your page with the Loader, right-click the checkout link and copy the link address, or click it and look at the address bar on the checkout page.

  • The link carries src or sck with a 32-character code (letters a to f and digits): it was decorated, and the identifier left your page. If the sale still arrives without the source, use the direct checkout link (on Lastlink, the …/checkout-payment one), see the Safari section and gather what is listed in "What to gather before asking for help", at the end of this page.
  • The link does not carry that code: check, in this order, that the platform's module is on, that the Loader is on this page and that the link is on a recognized domain. With Initiate Checkout on, a click on a recognized link shows in Events; if it does not, the Loader did not run on that visit or the link is not recognized. Then see your platform's case, just below.

The Hubla case: src and sck already taken in your link

On Hubla, the identifier goes into the checkout link's src and, when src is already yours, into sck. The script never overwrites a value of yours. So if your link already carries both, it is not decorated, and the sale arrives without the identifier.

  • How to check: copy the checkout link from the page. If it already has src= and sck= with values of yours (for example, ?src=instagram&sck=bio), this is the case.
  • Who takes them: the link you built yourself, or another script on the page that writes src and sck into checkout links (UTM propagation scripts can do this). If another script writes one of these parameters after Supreme, its value stays, and the identifier moves to the other parameter if that one is free.
  • How to fix it: leave one of the two free. Keep your own tracking in just one of them (for example, only in src), and the identifier goes into the other. If a script fills both, adjust its configuration.

The Lastlink case: src and sck already taken in your link

On Lastlink, the rule is the same: the identifier goes into src and, when src is already yours, into sck. If the link already uses both, it stays as it is, and the sale arrives without the identifier.

  • How to check: copy the checkout link from the page and see whether it already has src= and sck= with values of yours.
  • How to fix it: leave one of the two free. The other parameters do not count and are never touched: the UTMs, the af of affiliate links and VTurb's vtid can stay in the link.

Out of coverage: what the script cannot decorate

The script can only write the identifier into a real link (<a href="…">) that points to a recognized checkout. These are left out:

  • A checkout button that redirects through JavaScript, with no href: there is no link to decorate.
  • A checkout embedded in the page, in an iframe, or opened in a pop-up window by a script: the page cannot write into that checkout's address.
  • A checkout on your own domain: only pay.hub.la (Hubla) and lastlink.com/p/… (Lastlink) are recognized. Hubla's shortened link (hub.la/r/…) and www.lastlink.com are left out too.

In these cases, the click's Initiate Checkout does not fire either. To cover the sale, replace the button or the embedded checkout with a plain link to the platform's direct checkout: https://pay.hub.la/<offer-id> or https://lastlink.com/p/<code>/checkout-payment.

Safari private browsing

What changes: in Safari's private browsing (and in Safari set to apply advanced tracking protection to all browsing), the browser removes from links the parameters it recognizes as tracking before opening the page, and blocks resources from known trackers. The parameter list is Safari's, not Supreme's. Whether Safari removes src and sck from Hubla and Lastlink links has not been confirmed yet.

What you can check:

  1. Make the proof sale in a Safari private window. When you reach the checkout page, look at the address bar: if the src (or sck) with the 32-character code is still there, Safari did not remove it.
  2. Repeat the proof sale in another browser's private window. If the sale arrives with the source of the visit in the other browser and without it in Safari private browsing, the cause is the browser, not your setup.

Nothing in the Node or the Console changes what Safari does to links. What is within your reach is what the other sections of this page cover: a plain link, on a recognized domain, with src or sck free.

What to gather before asking for help

  • The transaction id and the platform (Hubla or Lastlink).
  • The checkout link exactly as it appears on your page (copied from the browser).
  • The checkout page's address, as it appears in the address bar after the click.
  • The browser used and whether the window was private.
  • Whether that click's Initiate Checkout showed in Events.

Do not send the platform's token or your Node's address URL: the URL is secret, and anyone who has it can send events to your Property.

Read also