RESOURCES / DEVELOPERS
Instrument eligible events, connect approved identity and customer context, and deliver it to supported destinations.
QUICK START
Install once. Start recognizing eligible journeys. Add more when you need it.
<script src="https://userportal.trustid.life/trustid.iife.js"
privacy-policy="/privacy-policy"
terms-of-service="/terms-of-service"
logo="/logos/trust-id-lockup.svg"
company="Your Company, Inc."
use-headless defer></script>This is the existing Trust ID JavaScript tag example. Replace company name, privacy and terms paths, and logo with your own values. The exact integration and privacy requirements should be verified for your site.
Install the standard tag in the site template or Google Tag Manager. One installation is sufficient.
Set the approved domains, identity and permission settings, and any required consent gating before activating data workflows.
Check that the trustid.iife.js request loads successfully, then look for approved visitor and journey events in the dashboard.
Connect the customer data, destination, on-site action, audience or enrichment path relevant to your goal.
WHAT THE TAG CONNECTS
RECOGNITION + CONTEXT
Reconnect eligible page and session activity with customer memory. A known person match requires supported identifiers and the right permissions.
Returning visitor → permitted history → more relevant page.
INTENT + AI
Use supported on-site behavior and customer context to personalize, recommend, recover an abandoned journey, or route sales interest.
Current behavior → approved AI action → on-site response.
AI AUDIENCES + DSP
Use AI-generated or admin-defined audiences from eligible signals. Activate approved segments through the Trust ID DSP and supported media workflows.
Person + intent → audience rules → permitted retargeting.
B2B + B2C ENRICHMENT
Request eligible person, contact, company or household attributes during a workflow. For larger datasets, submit an approved CSV and use the enriched output.
Known record or list → matched fields → approved action.
DELIVERY + INTEGRATIONS
Trust ID can send approved identity, customer memory, intent, or enrichment context into supported systems. The destination determines the schema, consent and delivery method.
Explore integrationsView visitors, sessions, eligible identity, customer history, and supported intent metrics. No additional export destination is required for initial site insight.
Connect supported events, customer context, or on-demand requests to authorized services. Confirm endpoints, field schemas, rate limits, and access with your implementation team.
Integrate with eligible CRM, CDP, analytics, lifecycle, media, and warehouse destinations. Some connections are assisted or depend on the service tier.
Upload an authorized file for supported matching and append jobs, then use the matched output according to your permitted purpose.
PRIVACY + VALIDATION
Customer data remains yours and is not resold or fed into a shared graph for other customers. Set consent and purpose controls before sending identity, enrichment, or audience information to downstream systems.
Optional credential, verification, and agent-related workflows require explicit implementation scope. The standard tag does not prompt visitors for Trust ID OTP or wallet setup.
Production event names, JSON schemas, delivery credentials, supported endpoint contracts, and rate limits must be confirmed against the current version of your deployment before engineering integration.
Troubleshoot duplicate tags, consent state, GTM triggers, browser CSP, and expected destination delivery. SOC 2 Type II review is in progress.
READY WHEN YOU ARE
Start with a free trial or talk to the team about a more complex deployment.