How pixel firing works on smart links
When someone clicks a smart link on 1smart.link, any tracking pixels you have assigned need to fire before the visitor reaches the destination URL. This article explains how that happens under the hood — the interstitial HTML page, the SDK wait window, the events that fire, and what happens when no pixels are assigned at all.
Understanding this mechanism helps you trust the data in your ad platforms and troubleshoot cases where conversions seem to go missing.
Why it matters
Every ad platform — Meta, TikTok, Google Analytics, LinkedIn, Pinterest — relies on its pixel SDK loading and sending an event back to its servers. If a visitor is redirected to the destination before the SDK has time to complete that round trip, the event is lost. No conversion is recorded, and your retargeting audiences never grow.
1smart.link solves this with a brief, nearly invisible interstitial step that gives every assigned pixel enough time to fire before the redirect happens. The result: your ad platforms see the conversion, your retargeting pools fill up, and your reporting stays accurate — all without noticeably slowing down the visitor's experience.
How it works
The entire process takes roughly one second. Here is what happens behind the scenes when a visitor clicks a smart link that has one or more pixels assigned.
Step 1 — The click
The visitor clicks your smart link (for example, www.1smart.link/my-offer). The request hits the 1smart.link server.
Step 2 — Interstitial HTML page
Instead of returning a standard 302 HTTP redirect, the server responds with a lightweight HTML page. This page is not a landing page — the visitor never interacts with it. It exists solely to load pixel scripts.
All assigned pixel SDKs are embedded in this HTML: Meta Pixel, GA4 tag, TikTok Pixel, LinkedIn Insight Tag, Pinterest Tag, or any combination you have configured.
Step 3 — SDKs initialise and events fire
Each pixel SDK initialises in the visitor's browser. Two things then happen in quick succession:
- PageView fires. This is the base event. It fires automatically for every pixel assigned to the link, every time. You do not need to configure it.
- Your chosen event fires on top. If you selected an event type — such as Lead, AddToCart, or Purchase — that event fires immediately after PageView. This means the ad platform receives both a PageView and your specific conversion event in a single visit.
Step 4 — Smart SDK wait
Pixel SDKs send events asynchronously. The browser needs a moment to open a connection and transmit the data. 1smart.link enforces a smart wait window to protect your conversions:
| Parameter | Value | Purpose |
|---|---|---|
| Minimum wait | 800 ms | Gives SDKs enough time to send events reliably on a normal connection |
| Maximum wait | 2,500 ms | Prevents holding the visitor if a pixel is slow, blocked, or unresponsive |
If all pixels report back before 800 ms, the page still waits until the minimum is reached — this guards against edge cases where an SDK appears done but has not fully flushed its event queue. If a pixel is still loading at 2,500 ms (perhaps due to a poor network or an ad-blocker), the page redirects anyway. Losing one slow pixel is better than losing the visitor.
Step 5 — Redirect
Once the wait window closes, the page automatically redirects the visitor to the destination URL. The entire interstitial step is fast enough that most visitors perceive it as normal link-loading behaviour.
The fast path — links without pixels
If a smart link has zero pixels assigned, the interstitial page is skipped entirely. The server returns a direct 302 HTTP redirect, sending the visitor straight to the destination as quickly as DNS and TLS resolution allow. There is no added latency.
This means you only pay the small time cost of pixel firing on links where you actually need tracking.
Widget default events on bio pages
On bio pages, each widget can fire a pixel event when a visitor interacts with it. If you have not explicitly chosen an event type for a widget, 1smart.link applies sensible defaults based on the widget type:
| Widget type | Default event |
|---|---|
| Button | Lead |
| Shop | AddToCart |
| Contact | |
| Smart Form | CompleteRegistration (fires on form submit, not on click) |
| Video / PDF / Gallery | Lead |
| All other widgets | PageView only |
These defaults align with what each interaction typically represents in an advertising funnel. A shop click signals purchase intent (AddToCart), a WhatsApp tap is a contact action, and a form submission is a registration.
Overriding defaults with custom events
You can override any default by explicitly setting an event type in the Pixels section of a widget's settings. The standard events available are:
- Lead
- AddToCart
- Purchase
- Contact
- CompleteRegistration
- Subscribe
- ViewContent
These standard events work across Meta, TikTok, LinkedIn, and Pinterest, so you configure once and all connected platforms receive the same event type.
When to use this knowledge
Understanding pixel firing is useful in several situations:
- Debugging missing conversions. If your ad platform shows fewer conversions than expected, check whether the pixel is assigned to the link. No pixel assignment means no interstitial, which means no event.
- Choosing the right event. Knowing that PageView always fires as a base event helps you avoid redundancy. You do not need to manually select PageView — pick the conversion event that matters instead.
- Evaluating page speed concerns. If stakeholders ask about the redirect delay, you can explain that the wait is capped at 2.5 seconds maximum and typically completes in under a second.
- Planning bio page funnels. The widget default events let you set up basic tracking without configuring every widget individually. Override only where the default does not match your funnel logic.
Related articles
- Article #26
- Article #4
- Article #20