Most landing page builders make a trade: control for safety. You get a grid of blocks that cannot break, and you cannot build anything the grid does not contain.
DropCPL takes the other trade. The page is plain HTML, generated by AI and editable by hand — and the tracking is protected structurally rather than by restriction.
What “plain HTML” means in practice
- The page is real HTML, CSS and JavaScript, served in SSR from the tracking domain.
- The editor is split view: the live preview on one side, a chat with the AI on the other.
- You can iterate on the hero, the copy, the form, the styles — by asking, or by editing the code directly.
- Versions and revert: every meaningful change is a version you can go back to.
The difference from a block builder shows up the first time you need something the builder does not have. A sticky bar with a countdown, a two-step form, a video that starts muted on scroll: with HTML it is a request to the AI. With a fixed grid it is a support ticket.
How the tracking survives free editing
This is the tension worth naming: a page you can edit completely is a page where you can delete the form, break the submit handler, or remove the script that reports the click.
DropCPL handles it by injecting the form and the attribution hooks in a way that free editing of the markup does not remove them. The click identifier is set server-side, before the page is ever rendered, so the attribution does not depend on a script running in the browser.
Why the page must live on the tracking domain
A landing page on your own domain, reached through a redirect from a tracking service, is the pattern that loses attribution on iOS. DropCPL serves the page from the same domain that logged the click — one request, one response, cookie included.
That constraint is not cosmetic. It is the reason the CPL in the attribution matrix is deterministic instead of modelled.
The loop it closes
- Generate or import a page.
- Launch ads pointing at it — DropCPL creates them on Meta and wires the destination URL itself.
- Watch the matrix tell you which page wins for each creative.
- Edit the losing page with the AI, and let the automatic A/B test reallocate traffic to the winner.
Related
- Automatic A/B testing — what happens when two pages compete
- First-party tracking — why co-location matters
- The AI agent — editing a page from a chat, end to end