Use a Custom tracking pixel only for a provider that is not covered by the built-in types. Enter the configuration accepted by the editor and test it on a noncritical link first.
Custom tracking code can affect visitor privacy, page behavior, and security. Only add code from a provider you trust, keep it limited to the required tracking task, and follow applicable consent requirements.
If a provider is already listed in Biqli, use its dedicated type instead.
Review before saving
- Confirm the code or configuration came from the intended provider account.
- Check that it does not collect more visitor data than the campaign requires.
- Remove credentials, private keys, and unrelated scripts.
- Review consent and privacy obligations for the countries you target.
- Test on a noncritical link before broad assignment.
Diagnose a custom integration
Open the short URL in a clean browser session with developer tools or the
provider debugger. Check whether the expected network request runs and whether
browser privacy extensions blocked it. Compare with a built-in provider type
before assuming the redirect failed.
Custom code can stop working when the provider changes its script. Revisit the
configuration after provider migrations and remove integrations that are no
longer maintained.
Never place a workspace API key, payout secret, or customer credential in a custom tracking configuration.
Frequently asked questions
Should I use Custom for Google Analytics?
Use the built-in provider type when it matches the integration.
Can a browser block the custom tracker?
Yes. Consent settings, privacy extensions, and browser policies can block
third-party requests.
Who should review custom code?
Someone responsible for application security, privacy, and the provider account
should approve it before broad use. 
