Jornaya Consent Capture Requirements

Contact your Engine account representative for onboarding support. For information related to Jornaya's tag behavior, please reference their documentation.

Overview

You can increase your conversion rates by allowing the Engine Call Center to contact leads after they search for a Loan or 2nd Look Product. To enable this for your API you must a consent proof - a Jornaya LeadiD token.

A consent proof is independent, third-party-witnessed evidence that the consumer saw a consent disclosure and acted on it. It is not the consent flag itself; it is evidence the consent event occurred, useful for TCPA defensibility.

Security & Data Handling

• The consent proof relates to a consumer consent event - handle it with the same care as the rest of the lead's personal data.

• Don't log the token alongside unnecessary PII, and transmit it only over the authenticated, encrypted API connection.

• Use placeholder values, never real consumer tokens, in test fixtures and shared examples.

How It Works

The tag should run on the page(s) of your consent flow so the consumer's journey is witnessed. You submit the captured token to Engine when you create or submit the lead at the consent step.

Integration Steps

You must generate a token every time a user goes through your flow and submits consent. The request takes a single consentProofInformation object. A lead can accumulate multiple proofs across submissions.

1

Install the LeadiD Tag on your Consent Page(s)

Add the campaign script on every step where the consumer progresses toward consent. Per vendor guidance, place it after the closing </form> tag and just before </body>.

Please reference Jornaya documentation for additional guidance at this step.

Sample Installation:

<script id="LeadiDscript" type="text/javascript">
(function() {
  var s = document.createElement('script');
  s.id = 'LeadiDscript_campaign';
  s.type = 'text/javascript';
  s.async = true;
  s.src = '//create.lidstatic.com/campaign/<CAMPAIGN_ID>.js?snippet_version=2';
  var LeadiDscript = document.getElementById('LeadiDscript');
  LeadiDscript.parentNode.insertBefore(s, LeadiDscript);
})();
</script>
<noscript><img src='//create.leadid.com/noscript.gif?lac=<LAC>&lck=<CAMPAIGN_ID>&snippet_version=2' /></noscript>

2

Add Hidden Token Input

Include the vendor's hidden input on the form that captures consent:

<input id="leadid_token" name="Jornaya_leadid" type="hidden" value="" />

You can read the token from this field, from the LeadiD callback function, or both. See Jornaya's callback documentation.

3

Mark the TCPA Disclosure

The disclosure must be witnessed by the tag. Put the marker attribute on a hidden <input> - Jornaya will not witness a disclosure placed on a div, span, or p.

<label>
  <input type="hidden" data-leadid-type="disclosure" />
  [YOUR TCPA DISCLOSURE TEXT]
</label>

Keep the disclosure visible to the consumer near the point of submission.

4

Submit Token to Engine

When you submit the lead, include consentProofInformation with the captured token and the correct source.

curl -X POST "https://api.engine.tech/leads/rateTables" \
  -H "Authorization: Bearer <YOUR_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{
        "consentProofInformation": {
          "consentProof": "<your_jornaya_leadid_token>",
          "consentProofSource": "external_jornaya"
        }
      }'

You can also submit on POST /leads/{uuid}/rateTables and other lead-submission endpoints - consentProofInformation is accepted wherever you submit a lead.

Please reference Engine's API endpoint definitions for more information.

API Schema Field Reference

Field	Data Type	Required?	Description
consentProof	string	Yes	The Jornaya LeadiD token generated by your Jornaya tag
consentProofSource	string	Yes	Must be external_jornaya

Note: external_jornaya is accepted on API submissions only. It is not valid inside an Engine-hosted embed.

API Response Reference

{
  "consentProofInformation": {
    "consentProof": "abc123-leadid-token",
    "consentProofSource": "external_jornaya"
  }

Additional Considerations

• Optional and additive. Submitting consentProofInformation doesn't change anything else about your lead payload. Leads without it are still accepted.

• Disclosure markup matters. The data-leadid-type="disclosure" marker must be on a hidden <input>, or the disclosure won't be witnessed.

• Use production campaign code in production. Don't ship a Preview/test campaign ID to your live pages - it won't witness real traffic correctly.

• Token is opaque. Don't modify or re-encode the token; submit exactly what the tag produced.

Troubleshooting

Symptom	Likely cause	How to confirm / fix
Token is empty at submit time	Tag not installed on the page, or read before it fired	Confirm the script is on the consent page and read the token from the hidden input or callback.
Disclosure not witnessed	Marker placed on a non-input element	Move data-leadid-type="disclosure" onto a hidden <input>.
Validation rejects the token	Token malformed / not a real LeadiD	Verify the tag produced a valid token (vendor self-test below).