Consent language: what publishers must not change
This guide covers the consent language on Summit landers: what each part does, the ways a publisher's setup can change it without meaning to, and how to test your funnel so it stays intact. By the end you will be able to audit any campaign for consent problems in a few minutes and know what to do if you find one.
The rule is short. Traffic goes to Summit landers through your tracking link, and the consent language on Summit landers is not changed or removed. This guide is general information, not legal advice.
Published 5 October 2026. How we write and check guides: editorial standards.
Already generating leads on your own forms? Sell your leads instead.
Why the consent block is fixed
Buyers of MVA and home improvement leads call and text the people who submit a form. Under the FCC's TCPA rules, many of those contacts need the person's prior express written consent, which is defined in 47 CFR 64.1200(f). The consent language on the lander is the written agreement the person accepts when they submit.
Summit captures TCPA consent on every lead and attaches a consent certificate. The certificate records the session on the lander, so it reflects what the person actually saw. If the text was hidden, cut off or reworded on the way, the record shows that too. A lead with a weak consent record is harder for a buyer to use, which affects whether it sells. If you are new to the law itself, start with TCPA basics for lead gen affiliates.
The parts of a consent block
Consent language on lead forms generally contains the elements below. The exact wording on each Summit lander is set by Summit, so treat this table as a guide to what the parts do, not a copy of any one lander.
| Element | What it does | How a publisher setup can break it |
|---|---|---|
| Who may contact the person | Identifies the companies or the type of companies that may call or text | Ad or pre-lander copy that names a different company, or says only one company will call |
| How contact happens | States that contact may include calls, texts and automated technology | Pre-lander copy that promises email only or "no calls" |
| The phone number | Ties the consent to the number entered in the form | Passing a number into the form from your own page, so the person never types or confirms it |
| Not a condition of purchase | Tells the person that agreeing is not required to buy anything | Cropping the lander in a frame so the bottom of the text is cut off |
| The action that signals agreement | The submit button or checkbox the person uses to agree | Scripts that click, check or submit on the person's behalf |
| Placement and visibility | Keeps the text near the button and readable | Overlays, sticky bars, chat widgets or zoom settings that cover or shrink it |
What counts as a change
Most consent problems are not deliberate edits. They come from tools and page setups that sit between the click and the form. Treat each of these as a change to the consent language:
- Editing or translating the text, including by browser extensions or translation layers you add.
- Hiding it, with CSS, a collapsed panel, a tiny font or a color that blends into the background.
- Covering it with a pop-up, exit intent box, sticky footer, cookie bar or chat bubble that you control.
- Cropping it by loading the lander inside a frame on another page.
- Copying the lander to your own domain or page builder, even word for word. The copy is no longer a Summit lander and its consent record is not Summit's.
- Automating the action, such as auto-checking a box, auto-submitting or pre-filling fields from another page.
- Moving the agreement off the lander, by asking for the phone number on a pre-lander and sending it along.
If you want to run your own pages in front of a Summit lander, read hosted landers vs your own landers and email us before you build. Ask before passing any form data in a link.
How to audit a campaign for consent problems
- 01
Step 1: List every live path
Export the destination URL of every live ad. Group them by tracking link and sub ID. Any URL that does not resolve to your tracking link needs a reason, or it comes down.
- 02
Step 2: Open each path on a phone
Most MVA and home improvement traffic is mobile. Tap through each path on a real phone, in the in-app browser for Meta traffic and a normal browser for Google and native traffic. Scroll to the submit button and read the consent text in full.
- 03
Step 3: Repeat on desktop
Check that the text is not cut off at the side, hidden behind a fixed header, or pushed below a footer you added.
- 04
Step 4: Compare the promise to the consent
Put your ad copy, your pre-lander copy and the consent text side by side. If the ad says one thing about who will contact the person, or how, and the consent says another, rewrite the ad.
- 05
Step 5: Check scripts on your own pages
Review every script, plugin and widget on your pre-landers. Remove anything that writes to the next page, opens overlays after the click, or interacts with forms.
- 06
Step 6: Record the result
Note the date, the paths you checked and the devices you used. Repeat the audit whenever you change a pre-lander, add a placement or launch a new offer.
Want to run traffic to landers with consent built in? Apply as a publisher with your sources and states.
Apply as a publisherQuick consent checklist
- Every ad points to your tracking link, not a copy of the lander.
- The consent text is fully visible on mobile and desktop without zooming.
- Nothing of yours loads on top of the Summit lander.
- Your ads and pre-landers do not promise "no calls", email only or a single caller.
- No field on the lander is filled in or checked by a script you control.
- The person types and submits their own phone number on the Summit lander.
- You saved the date and results of your last audit.
What to do if something looks wrong
If you see consent text missing, cut off or different from what you expect, pause the affected ads first. Then email team@summitleads.ai with the tracking link, the sub ID, the device and a screenshot. Do not try to fix a Summit lander from your side, for example by adding your own consent text above it. Two consent blocks that say different things cause more problems than they solve.
If the issue came from your setup, fix it, run the audit again and note the dates the problem was live. Leads from that window may not sell or may be returned. Returns are deducted under the return terms agreed during onboarding. See why leads get returned.
Common mistakes
- Rebuilding the lander to match your brand. A copied lander is not a Summit lander, even if every word matches.
- Adding urgency overlays. Countdown bars and exit pop-ups often cover the bottom of the form, where consent text sits.
- Pre-lander quizzes that collect the phone number. The number has to be entered and submitted on the lander with the consent language.
- Copy that narrows who will call. "One local attorney will contact you" can conflict with consent language that covers more than one company.
- Testing only on desktop. Problems tend to show up on small screens and in in-app browsers.
- Auditing once. Every new pre-lander or plugin is a new chance to break the consent block.
Frequently asked questions
Can I edit the consent text to make it shorter?
No. The consent language on Summit landers is not changed or removed. If you have a question about the wording, email us rather than changing it.
Can I use a pre-lander before the Summit lander?
Pre-landers are common with native traffic. The pre-lander should send people to your tracking link, should not collect the phone number, and should not make promises that conflict with the consent text. Follow our traffic guidelines and ask us if you are unsure.
What does the consent certificate record?
A consent certificate records the session on the lander, so it reflects what the person saw and did when they submitted. That is why changes from overlays, frames or scripts matter: they become part of the record.
Can I add my own disclaimer above the Summit form?
Do not add consent wording of your own on or over the lander. Two consent blocks that say different things confuse the person and the record. If you think a disclosure is missing, email us with the tracking link and a screenshot, and pause the ads while you wait for an answer.
Does this apply to Meta and Google traffic the same way?
Yes. Whatever the source, the lead submits on the Summit lander through your tracking link. On Meta, that means using a website destination, not an instant form. See how to run MVA traffic on Meta.
Related guides
The law behind the consent block.
When your own pages fit, and what to ask first.
How to build pages in front of the lander.
The rules for every publisher campaign.
Why the FCC rule never took effect.
Sources
- 47 CFR 64.1200: Delivery restrictions, Electronic Code of Federal Regulations
Run traffic to landers with consent captured on every lead
Every publisher is reviewed before going live. Email us your sources, verticals and target states.
Apply as a publisherOr write to team@summitleads.ai. We reply by email.
Already generating leads on your own forms? Sell your leads instead.