Consent and privacy
Keep a record of what the visitor saw
When someone asks what the page said on a given day, you need the page, not a recollection.
A landing page changes. Headlines get tested, consent paragraphs get edited, fields are added, and a privacy link gets pointed at a new URL. Months later someone asks a narrow question: what did this visitor see when they submitted the form on that Tuesday? Memory is not an answer. The live page is not an answer either, because the live page is whatever you deployed since. You need a record of the page as it was offered, tied to the time of the submission.
This is ordinary operational hygiene. It is also the difference between a serious campaign and a pile of screenshots nobody can find. The record does not, by itself, prove that a particular person understood a particular sentence, and it does not make a bad paragraph good. It does let you stop guessing. This article describes what to keep and how to keep it findable. It does not describe a legal hold, a discovery process, or a product feature as a guarantee. Follow your own retention and legal advice for how long a record must exist.
What “the page” includes
Capture the things a visitor could actually use. That means the headline and offer, the form labels, the consent paragraph, the privacy-notice text or the exact URL it opened, the button label, and the address of the page. If a banner or a sticky bar covered the button, a record that crops the banner out is a flattering edit, not a record. Save the mobile view if that is how the traffic arrived. A desktop-only screenshot of a page that ninety percent of people saw on a phone is a picture of a different experience.
Include the date and the page address in the file name or in a log line you can search. “final-final.png” is not a record. “2026-04-02-windows-estimate-consent.png” next to the URL is a record. When you change the consent paragraph, save the new version before traffic hits it, and leave the old version alone. Do not overwrite. Overwriting is how a helpful cleanup destroys the only copy of the words you may need.
Tie the record to the submission
A folder of screenshots is only half the system. The submission itself should carry enough context to find the right screenshot: the page or campaign name, the time, and, if you version the copy, a version identifier. You do not need a romantic narrative in the database. You need a key. When a question arrives about one phone number, you should be able to go from that row to the words that were on the page, without asking the marketer who has since changed jobs what they “think it said.”
If your platform can store a visual playback or a copy of the consent text alongside the lead, use it and then verify it. Submit a test lead, open the record, and confirm the stored words match the page you just saw on your phone. Tools fail in quiet ways: they store last month’s template, they miss the checkbox state, or they capture the page before the consent text has loaded. A tool you have not tested is a rumor. The test lead can use an obvious fake name so it never enters a real follow-up queue. Delete or flag it according to your own process after the check.
What not to rely on
Do not rely on the ad platform’s preview. The preview shows the ad, not the page after your latest edit. Do not rely on a designer’s export from a graphics tool. Visitors did not submit the export. They submitted the HTML. Do not rely on a teammate’s assertion that “we always use the standard paragraph.” Campaigns drift, and the drift is the entire reason the record exists. The standard paragraph is a hope. The saved page is a fact.
Do not keep consumer submissions in a personal photo roll or a random chat thread “so we have a copy.” That spreads sensitive form data into places with no access control and no retention plan. Store the page record and the submission in the system your business already treats as the system of record. Limit who can export it. A record that protects you in a dispute and leaks a list of phone numbers in a chat app has failed a different duty at the same time.
Change control in plain clothes
You do not need an elaborate release ceremony. You do need a pause. When the consent text, the fields, or the privacy link change, stop and save the new state, note the time, and only then send traffic. If you run a headline test, treat each headline as a version. “We were testing some stuff in April” is not a version history. A note that says which headline ran, on which URL, from Monday to Thursday, is. The measurement guide explains how to compare headlines without lying to yourself. The record explains how to reconstruct the comparison later.
Assign a person. Records die when they are everybody’s job. The person does not have to be a lawyer. They have to be the one who will not deploy a consent edit without saving the previous wording. Put their name in the campaign’s one-page brief. When they are out, name the backup. This is unglamorous and it is the whole control.
A minimum kit
- A saved copy of the page as phones see it, including consent and the privacy link target.
- A date and the public URL on that copy.
- A new copy whenever the offer, fields, consent, or privacy destination change.
- A way to connect a submission to the copy that was live.
- A tested path through whatever tool claims to store the page for you.
- One named owner, and a backup, who refuses to overwrite history.
- Storage inside the business system, not in a personal chat log.
Build the kit before the campaign is large. Reconstructing it during a complaint is how details get invented. A calm Tuesday is the right time to submit a test, open the stored record, and see whether the words match. If they do, you can go back to operating the page. If they do not, you still have time to fix the capture. Later is a worse time to discover that the record was a blank thumbnail.