Consent Tracking
Keep the evidence behind the lead
Capture intake-page interactions with the native consent pixel, link certificates to leads and keep the submitted consent language and references for review.
How it works
- 1
Configure capture
Turn on the consent module and install the supported pixel on the intake page. Use the campaign posting instructions to map the certificate URL and the consumer consent fields into the submitted lead.
- 2
Attach the evidence
Send the native certificate URL in consentCertUrl along with the individual consent fields that apply, including tcpaConsent and the consent text and timing. Third-party certificate references use their own documented fields and integrations.
- 3
Review and deliver
Review the certificate, captured interaction summary, snapshots and claim state where available. Lead detail and your delivery and reporting fields keep the evidence tied to the lead.
Capture, connect and inspect
Consent evidence is most useful when the intake page, submitted fields and delivered record agree.
Native interaction capture
The native pixel records supported page interactions and creates a certificate for that capture session. Review the interaction summary and any snapshots from the certificate detail. Install and set up capture on the real intake page; turning on a tenant module alone does not add a pixel to it.
Certificate-to-lead mapping
The native certificate URL belongs in consentCertUrl. The accepted disclosure, the true/false consent value and the timestamp are separate lead fields. A certificate reference does not make a missing consent value true, and it does not replace fields the campaign requires.
Claim state and external certificates
Native certificates and TrustedForm certificates are different records. Supported external integrations can store references and run configured claiming; their credentials, issuance and claim requirements stay provider-specific. Jornaya references also follow their supported integration path.
Review evidence with the lead
Use consent status filters and the linked certificate detail to look into captured evidence. Carry the certificate references and consent fields that apply through your delivery mappings. What you can see depends on your role, permissions and the evidence that was actually submitted or captured.
Connect evidence to your operating rules
The platform gives you records and controls you can configure. Your intake and use of the data still need to match what the consumer agreed to.
Campaign and vertical requirements
Generated specifications show the consent fields the campaign requires. Set up the vertical and intake requirements that apply, validate real submissions and make sure the stored disclosure text matches what the consumer saw.
Suppression and privacy workflows
Consent capture works alongside suppression, data-access permissions and data-request handling. A captured certificate does not override an opt-out, and it does not give every portal user access to personal information.
Call announcements are a separate control
For calls, proof from an upstream partner that a disclosure already played, together with the offer or campaign settings, decides whether the platform repeats a recording announcement. The stored reason explains the playback choice. Announcement playback and recording settings are separate from a web-form certificate.
Evidence rather than a legal guarantee
A certificate documents the capture and the related evidence. It is not a promise that every contact or use is legally permitted. Describe and keep the actual disclosure and permissions you collected, and apply the rules that fit the campaign and the communication.
What your account needs
Consent capture needs the enabled module, the installed pixel and correct posting-field mapping. Third-party services need their own credentials and supported inputs. Retained evidence depends on what was captured and submitted; it is not rebuilt for traffic that never supplied it.
Frequently asked questions
Is a native certificate a TrustedForm certificate?
No. Native consent capture and outside certificate providers are separate systems. Use the certificate fields and provider integration that match the evidence your intake page produces.
Which field attaches a native certificate to the lead?
Use consentCertUrl as shown in the generated posting specification. Submit the required boolean consent, text and timestamp fields separately.
Does a certificate automatically satisfy every consent requirement?
No. It keeps capture evidence. The disclosure, the consumer’s action, the campaign requirements and the intended communication decide what you need to collect and keep.
Does turning on consent tracking install the pixel?
No. Enable the module, install the pixel on the intake page and wire its output into the submission. Test that the resulting lead links to the expected certificate.
Explore the platform
Set up your buyer network
Choose how buyers get leads and calls. Keep their setup and routing rules in one place.
Every feature is part of the plan. Usage is billed in credits.