> ## Documentation Index
> Fetch the complete documentation index at: https://learn.biq.li/llms.txt
> Use this file to discover all available pages before exploring further.

# Tracking pixels overview

> Understand how tracking pixels work with Biqli links.

Tracking pixels send supported visit data to an advertising or analytics provider when a visitor follows an assigned short link. Create the provider configuration once, then attach it to the links that should use it.

Pixels are separate from Biqli conversion tracking. A provider may record its own campaign event while Biqli records the link click and any configured lead or sale.

Only use tracking technology with the notices and consent required for your audience.

## Add a tracking pixel

1. Open **Tracking pixels** and select **Add pixel**.
2. Choose the provider type.
3. Enter a name and the provider identifier or configuration requested.
4. Save the pixel, then attach it to one or more short links.
5. Visit a test short URL and use the provider's own debugger to confirm the
   request.

The pixel belongs to the workspace and can be reused across supported links.
Updating its provider configuration affects future visits on every link that
uses it.

Tracking pixels do not make a destination's own analytics automatically match
Biqli. Providers can block, sample, deduplicate, or classify traffic
differently.

Remove the pixel from live links before deleting it when you want a controlled
shutdown.

## Frequently asked questions

### Does a pixel replace Biqli analytics?

No. It sends supported tracking to the provider while Biqli records its own
eligible activity.

### Why do provider totals differ?

Consent, blockers, filtering, deduplication, and attribution rules can differ.

### Does updating a pixel affect every attached link?

Yes for future visits using that shared workspace pixel configuration.