On this page11 sections
Growth Operations ResearchA reproducible consent-evidence audit, not a legal opinion.

Measuring How Often Imported Leads Lack a Timestamped Consent Record

A bounded measurement design for counting imported leads that cannot be tied to a dated consent event.

Published ••4 min read
Measuring How Often Imported Leads Lack a Timestamped Consent Record research illustration

What this measurement covers

This design measures how many imported leads lack a consent record that can be tied to a specific date and source. It is not a legal opinion and does not decide whether a list is lawful. The practical question is narrower: after an import, can the team show when and where each contact agreed to receive messages? A missing timestamp is a maintenance and evidence gap, even when the consent itself was valid. The measurement makes that gap visible before the first campaign.

Define the import population

Start with the imports completed during a stated window. Record the source, the import date, the number of rows, and the person who ran the import. Decide whether partner lists, event lists, and manual uploads all count, and write the rule. If an import was a correction to an earlier file, record that as well. The population should be the imports the team actually made, not a theoretical list of sources. Keep the import log with the export.

Write down the fields that must be present for a record to count. At minimum, a consent timestamp, a source identifier, and the consent value or language version. Decide whether a date-only field counts or whether a time is required. Record how the timestamp is stored and whether it is timezone-aware. The definition should be strict enough to be testable but realistic for the systems in use. Apply the same definition to every import so the results are comparable.

Capture the import as received

Export the imported rows with the consent fields exactly as they arrived, before any normalization. Keep the raw file and a checksum if the process supports it. Record the mapping between the source columns and the CRM fields, including any default values applied during import. A default timestamp added by the import tool is not evidence of when the person consented. The raw file is the primary evidence; the CRM view is secondary.

For each row, try to match the consent record to the source system that collected it. Record whether the match succeeded and what field was used, such as an email address or a source identifier. If the match fails, mark the record as unverifiable rather than guessing. Do not use the import date as a substitute for the consent date. The join is the core of the measurement and should be reproducible from the saved files.

Classify the evidence

Group the records into timestamped consent, consent with a date but no time, consent language but no timestamp, no consent field, and unverifiable. Add a category for a timestamp that is clearly the import time rather than the collection time. The classification separates a formatting problem from a missing-evidence problem. Each category points to a different repair, from a field mapping fix to a conversation with the source.

Measure the share with dated evidence

Report the number of rows imported, the number with timestamped consent, and the number in each failure category. Report counts alongside percentages and break the result down by source. Do not describe the result as an industry benchmark or a legal standard. It describes these imports at this time. A small import with a clear gap is more useful than a large aggregate that hides which source is responsible.

Check the timing relative to the first send

For each import, record the date of the first campaign that included the new rows. Compare it with the consent dates. A campaign sent before the consent date is a serious finding; a campaign sent long after is a different question about freshness. Record the gap and flag the records where the order is impossible. This step ties the evidence gap to an actual send rather than treating it as a filing issue.

Investigate the source pattern

Group the failures by partner, by form, and by import method. A partner that never sends a timestamp is a source problem. A form that writes the date in a local format may be a mapping problem. A manual upload that fills a default date is a process problem. The pattern determines whether the repair is a contract change, a field mapping, or a training step. Record the evidence for each pattern.

Choose one repair and retest

Pick the largest pattern and fix it at the source. That might mean requiring a timestamp field in the partner export, correcting the import mapping, or rejecting a list until the evidence is provided. Retest with the same definitions on the next import. Compare the share with dated evidence and report what changed. A repair that increases verifiable consent without slowing the import is a real improvement.

Document limits and data handling

The measurement depends on access to the source systems and on the accuracy of the matching key. It cannot prove that a person understood the consent, and it does not replace legal review. State those limits in the method note. The files contain personal data, so restrict access, keep only the fields needed, and delete the working extracts when the review is complete. A repeatable consent audit is one that another analyst can run after the next import with the same definitions.

Sources

  1. https://www.ftc.gov/business-guidance/privacy-security
  2. https://www.ecfr.gov/current/title-16/chapter-I/subchapter-C/part-316
  3. https://www.w3.org/TR/NOTE-datetime
  4. https://www.nist.gov/cyberframework
  5. https://www.census.gov/data/developers/guidance/api-user-guide.html