Skip to main content
Open the short link, go to Retargeting, and select the tracking pixels that should run for its visits. Save the link, then test its short URL with the provider’s debugging tools. You can attach more than one pixel. Each selected configuration is independent, so avoid attaching duplicate provider identifiers unless that is intentional. Detaching a pixel stops it from running on future visits to that link. It does not remove historical data held by the provider.
  1. Open the short link and select Retargeting.
  2. Find Pixels and choose one or more existing workspace pixels.
  3. Save the link.
  4. Retrieve or reopen it and confirm the expected pixel IDs are attached.
  5. Visit the short URL with provider debugging enabled.
The key or member needs link write access and read access to the referenced tracking pixel for equivalent API operations.

​
Multiple pixels

Biqli can run several selected providers for one visit. Each can have different loading, consent, filtering, and deduplication behavior. Avoid duplicate identifiers unless the provider explicitly requires them. To stop a provider, detach it from the link. To replace every attachment through an API update, send the complete intended pixel ID list, including an empty list when the endpoint documents clearing behavior.

​
Frequently asked questions

​
Does detaching remove provider history?

No. It stops future use on the link and does not control data already held by the provider. The role or API key can be missing Tracking pixels Read access. Yes. Test for duplicates, consent, and provider-specific behavior.