Connect Lastlink

This guide connects Lastlink to your SupremeTracking Node. When you finish, Lastlink's sales, refunds and abandoned carts reach the Node by webhook, and the Loader writes the visitor's identifier into the checkout link, so each sale can be tied to the visit that brought it.

Two pieces work together:

• The webhook: Lastlink notifies the Node, server to server, for each event you tick. On Lastlink, the webhook is set up inside each product.
• The checkout link: while the module is active, the script served by the Loader writes the visitor's identifier into the lastlink.com/p/… link, and Lastlink returns that parameter in the sale notification.

The visitor's identifier is the STUID: a 32-character code the Node assigns to the visitor the Loader identifies. It is what ties a sale to the click, the campaign and the session it came from.

Labels from Lastlink's panel are given in English, followed by the Portuguese label in parentheses.

Before you start

• A Node on version 4.2.0 or newer. On an older Node, the module's Webhook tab says the Node must be updated.
• A Property created in the Console. The Property is what receives the sales.
• The Loader installed on the pages that carry Lastlink checkout links. See Install the Loader.
• A Lastlink account with access to the integrations of each product you sell.

1. Install and turn on the Lastlink module

1. In the Console, open Integrations › Manage Modules, click Install module and install the Lastlink module.
2. When the install finishes, the Console asks whether you want to activate it now. Click Activate now: the module starts receiving sales and the checkout script goes into the Loader. Then the Lastlink modal opens, with the Webhook, Checkout and Setup guide tabs.
3. If you click Not now, the module stays off and the modal does not open. To come back to it, open Manage Modules, click Configure on the Lastlink module and use Turn on at the top of the modal.

Turning the module on or off applies to every Property on this Node. While the module is off, link decoration and Initiate Checkout do not run, and webhook deliveries are refused.

2. One webhook per product, a single address

On Lastlink, the webhook lives inside the product: each product has its own webhook, and each webhook has its own Token, generated by Lastlink. On Supreme, each Property has a single address. So:

• the URL is the same in every product webhook of the Property;
• each webhook's token goes into the same address, all together, separated by commas.

The Node only accepts deliveries that carry one of the tokens saved on the address. A delivery with no token, or with a token that is not there, is refused and nothing is recorded.

For the first product:

1. In Lastlink, open the product › Integrations (Integrações) › Lastlink - Webhook › Turn on (Ativar).
2. Click New webhook (Novo webhook) and copy the Token shown on the screen.
3. In the Console, on the Webhook tab of the Lastlink modal, click Create address. Choose the Property, paste the token into the Lastlink webhook tokens field and click Create address. The field shows how many tokens you pasted.
4. Copy the URL labeled All events. Treat this URL like a password: anyone who has it can send events to this Property.
5. Back on Lastlink's New webhook, give it a name (for example, Supreme), paste the URL and tick the events from section 3.
6. Click Test (Testar), then Save (Salvar). Section 6 shows what the test proves.

For each further product, repeat steps 1, 2, 5 and 6 with the same URL, and add the new webhook's token to the address: in Integrations › Webhooks, open the address, click Credentials and save the tokens field with every token, from every product, separated by commas (token1, token2). The saved value is the whole list.

3. The events to tick

In each product webhook, tick Purchase completed (Compra Completa), Renewal payment made (Pagamento de Renovação Efetuado), Payment refunded (Pagamento Reembolsado), Payment charged back (Pagamento Estornado), Abandoned cart (Carrinho Abandonado), Invoice created (Fatura Criada) and Subscription canceled (Assinatura Cancelada).

What each one becomes in Supreme:

Lastlink's other events can stay ticked: they are accepted and ignored by design. Lastlink itself recommends turning on only the events you use.

4. src and sck: where the identifier goes

While the module is active, the script served by the Loader looks for Lastlink checkout links on the page and writes the visitor's identifier into them:

• If the link has no src, the identifier goes into src.
• If you already use src, it goes into sck.
• If you use both, the link stays as it is, and a sale that comes from it arrives without the identifier. See Sale without the visitor identifier.

The script never overwrites a value of yours, never leaves the same parameter twice in the link and does not change links to other domains. It does not touch the UTMs, the af of affiliate links or vtid (VTurb's parameter). And it only decorates once the Loader has identified the visitor.

Recognized links: https://lastlink.com/p/<code> links, both the offer link and the direct checkout link. On your pages, use the direct checkout link, https://lastlink.com/p/<code>/checkout-payment: it takes the buyer, with the identifier in the link, straight to the payment step. Links on www.lastlink.com or on a checkout domain of your own are not decorated. The modal's Checkout tab shows the list under Recognized domains.

5. Initiate Checkout on the link click

The module also fires an Initiate Checkout when the visitor clicks a Lastlink checkout link. In the Loader configuration, it shows as Initiate Checkout · via Lastlink.

• It is turned on and off per Property: on the modal's Checkout tab, choose the Property and use the Initiate Checkout switch. It comes on.
• Turning it off does not affect link decoration: the sale can still be tied to the visit.
• The change reaches new visitors within 1 hour.

6. Test deliveries: IsTest and the ignored delivery

Lastlink's Test button (Testar) sends simulations to the webhook URL, with fictitious data. One click can produce several deliveries at once. All of them arrive flagged as a test (IsTest: true).

The Node accepts these deliveries but records nothing: the test never becomes a sale, does not show in Events and is not forwarded to any destination. On the modal's Webhook tab, the last delivery reads: Last delivery: ignored — a platform test or an event Supreme does not record. The URL and token are correct.

What the test proves: the URL and that webhook's token are correct. What it does not prove: that a real sale comes back with the visitor's identifier. Only the proof sale shows that (section 8). If the test does not show up within a minute, check that the product's token is on the address.

7. Lastlink's native pixel, CAPI and GA4: double counting

Lastlink also has native advertising and analytics integrations. Through Meta's pixel and Conversions API (CAPI), it sends, among others, InitiateCheckout (when the buyer fills in a checkout field, such as the e-mail) and the purchase. Through its native GA4, it sends begin_checkout and purchase.

If your Property also forwards these events to the same Meta account, or to the same GA4 property, through Supreme, the destination receives two purchases for the same sale. The two cannot be deduplicated: Lastlink's webhook does not carry the id its native integrations used for the event. Pick one side:

• turn off Lastlink's native Purchase and Initiate Checkout (and the native GA4 purchase, if you forward to the same GA4); or
• accept the double count.

The two Initiate Checkouts do not even describe the same moment: Supreme's is born on the link click, on your page; the native one, when the buyer fills in a field in the checkout.

8. Prove a sale end to end

The proof sale is the test that confirms, on your account, that a Lastlink sale comes back with the visitor's identifier and is tied to the visit:

1. Open your page with the Loader in a private window.
2. Click the checkout link and check the Initiate Checkout in Events.
3. Pay a low-value Pix.
4. Check the purchase in Events, with the source of your visit.
5. Refund the full amount and check the refund.

If the purchase arrives without the source of the visit, follow Sale without the visitor identifier.

Next steps

• Also selling on Hubla? See Connect Hubla.
• For the general model of modules and connections, read Integrations overview.