Custom Vendors
If a third-party service on your site isn't in the ConsentForge vendor library, create a custom vendor.
When to create a custom vendor
- A proprietary or internal script that tracks users
- A niche SaaS tool not yet in the library
- A client-specific integration
Creating a custom vendor
- Go to Property → Vendors → Add Vendor → Custom Vendor
- Fill in the required fields:
| Field | Required | Notes |
|---|---|---|
| Name | Yes | Shown in Preference Center |
| Provider | Yes | Company name |
| Category | Yes | necessary, analytics, marketing, or functional |
| Purpose | Yes | Plain-language explanation for users |
| Cookie names | No | Patterns this vendor sets (used by scanner) |
| Privacy policy URL | No | Link to vendor's privacy policy |
- Add translations for DE (and any other active locales)
- Save
Adding cookie/script patterns
In the Cookie names field, add patterns that the scanner should associate with this vendor:
_mycookie
_myapp_*
myapp.tracking.*
Supports exact names and wildcard patterns (*).
Script blocking for custom vendors
To block scripts from your custom vendor, add the data-consent-category attribute to the script on your page:
<script
type="text/plain"
data-consent-category="analytics"
src="https://tracking.myapp.com/tracker.js"
></script>
See Script Blocking for full details.
Submitting to the library
If your custom vendor would be useful to other ConsentForge users, submit it for inclusion in the library via Vendors → Custom Vendors → Submit to Library.