ID Vault
Store GA4 / Meta / Ads IDs per domain, encrypted at rest.
The ID Vault is your per-domain registry of tracking IDs — GA4 Measurement IDs, GTM container IDs, Meta Pixel IDs, Google Ads Conversion IDs + Labels, LinkedIn Partner IDs, Microsoft UET Tag IDs. Store them once per domain, reuse them everywhere.
Why a vault?
- Auto-pre-fill in the wizard. When you start a new generation, TrackingCoder pulls the right ID for the channel + domain you're generating for. No copy-pasting your
G-XXXevery time. - Auto-import on scan. When the scanner finds an ID embedded on your site, it offers to save it to the vault for you.
- Authoritative source. If the scanner misses an ID (CSP-blocked, late-loaded), adding it to the vault tells TrackingCoder the ID is genuinely installed — so the "GA4 missing" warning on the dashboard stops showing.
Security
Values are encrypted at rest using AES-256-GCM (column-level encryption inside tracking_ids.value, never stored in plaintext). Keys are managed via ENCRYPTION_KEY in the server environment and rotated separately from application deploys.
Tracking IDs aren't secret by nature — they ship in your page source. We encrypt anyway because (a) defence in depth and (b) any DB dump shouldn't expose customers' entire analytics setup.
Sharing across a workspace (Pro)
On TC Pro, the vault is per-org rather than per-user. Every member sees the same IDs and the same domains. Useful for agencies handing client work between team members — the Measurement IDs follow the domain, not the person who scanned it.
Common questions
Can I edit an ID after generating with the old one? Yes. Edit in the vault. The generated codes that were already downloaded keep the old ID baked in — re-generate (and re-import into GTM) when you want the new ID to take effect.
What if I have two GA4 properties on one domain? TrackingCoder supports one primary ID per (domain, channel). For multi-property setups, the cleanest path is to generate one scenario per property — switch the ID in the wizard before each generation. Multi-ID-per-generation is a roadmap item.