Tired of your plugins getting leaked?
Now you can
fight back, silently.
[TRAK] injects traceable data directly into your distributed ZIP files at download time, tagging each user. Whether it's a plugin, a JS snippet, or PHP source — you'll know
who shared it,
when, and
how.
What It Does
Ever had one of your premium plugins end up on some shady warez site within 12 hours of release?
Yeah, same. That ends now.
With [TRAK], you can:
- Inject unique user data into PHP, JS, or other text-based files inside ZIP attachments
- Track leaks with simple comments like:
PHP:
// Downloaded by: {$visitor.username}
JavaScript:
const userId = "{$visitor.user_id}";
- Use encrypted variables for stealthy tracking:
JavaScript:
var licenseToken = "{$encA}";
var fingerprint = "{$encB}";
var shadowId = "{$encC}";
- Perform regex-based replacements or even run PHP callbacks for advanced logic
- Target specific files inside the ZIP by path and name
- Only apply rules to selected content types, file types, content IDs or attachment IDs
- Create your own tracking rules in the admin panel with full control over when and how content is modified
Features
Inject variables like {$visitor.username}, {$visitor.user_id}, and encrypted equivalents
Apply replacements only to specific ZIP file paths (e.g. upload/src/...)
Regex & PHP callback support for advanced modifications
Track downloads by user, timestamp, or other custom values
Set different rules per content type, extension, content ID, or attachment ID
Built-in encryption callbacks for obfuscating inserted values
Supports multi-rule configuration from ACP
Use Cases Beyond Tracking
- Add per-user license keys or version flags at runtime
- Inject custom code for feature toggles or debug hooks
- Tag releases with build metadata, usage scope, or client info
- Watermark files for customers based on plan or subscription
In Summary
Whether you want to catch pirates or personalize your downloads, [TRAK] gives you fine-grained control over attachment downloads
Once you know who did it, I'll leave the rest to you, good luck!
This works with attachments, so as long as your resource distributions also works with attachments, this should work for you (works well with TTUT, but not required)