adsoraFollow the offer through to submission
Ask for a representative ad or entry point, the landing page, each qualification step and the final contact form. Read the offer as a homeowner would. Check what service is promised, which company or companies are presented and what the page says will happen after submission.
Compare those details with your buying brief. A campaign that invites small repairs may not fit a replacement-only roofing program even if the final record is labeled roofing. A page promising a broad renovation may not match a wet-area bath installer. Record the mismatch at the source rather than asking the receiving team to discover it repeatedly in calls.
Identify who controls the campaign
Document the party responsible for the ads, capture page and delivery. If the supplier uses additional publishers, ask how those sources are approved and identified in the record. A brand name alone does not establish who can change the page tomorrow.
Request a stable source or campaign identifier that your team can use in reporting. Agree when a new page, offer or publisher requires another review. Keep the approved version and effective date so the reviewer can connect a delivered inquiry to the source configuration that applied at capture.
Check capture evidence and retention separately
When a program uses TrustedForm, keep the certificate reference linked to the source lead ID. ActiveProspect documents a Retain operation for storing a certificate and a lead-matching operation for comparing supplied contact details with the certificate. Inspect the result of the operations your team requires, not only whether the field contains a URL.
A record of the capture event does not decide every later use of the data. Have the responsible privacy and legal reviewers approve the proposed contact workflow and evidence requirements. The operational task is to capture their requirements in the buying specification and verify that the system follows them.
Sources: ActiveProspect: Retain API operation and lead matching.
Keep an approval packet you can retrieve
| Record | Purpose |
|---|---|
| Source and campaign owner | Identifies who can explain or change the capture path |
| Approved page and offer | Shows the experience the reviewer examined |
| Required fields and evidence | Defines what must accompany delivery |
| Review decision and date | Records which version was approved |
| Change contact | Names the person who receives source updates |
Use a redacted or approved test record for general review. Restrict access to actual homeowner information and capture evidence to the people who need it. A source review should not create an uncontrolled copy of the same personal data in several team folders.
Make source changes visible during the pilot
Ask the supplier to identify changes in page, offer, qualification questions or publisher mix before they affect the approved program. Decide which changes need a fresh review and which can be logged without stopping intake. The answer should follow your program’s requirements rather than a blanket rule that every cosmetic edit triggers a relaunch.
If project-fit complaints rise, compare recent records with the approved capture path and the effective campaign version. A changed offer, a field mapping error and a receiving-team misunderstanding require different fixes. Use a small set of traceable records to identify the cause.