Build and import landing pages with Tracked Site Agent

Tracked Site Agent works with your campaign data and landing-page files inside a private draft workspace. It can inspect performance, edit referenced page files, prepare tracked offers and campaigns, generate images, and show a preview while keeping saving, publication, and campaign writes as separate governed actions.

The useful distinction is simple: the agent can help build the work, but a draft is not live merely because the edit is finished.

What the Tracked Site Agent can work with

The agent can inspect Tracked sites, campaigns, offers, and connected accounts available to the current organization. Its analytics tools cover supported totals, sales, trends, funnels, traffic quality, and breakdowns.

For landing-page work, it can:

• inspect referenced folders and files;
• edit HTML, CSS, JavaScript, and supported assets in a private draft;
• create a new draft page or folder;
• generate a temporary image for review;
• save an approved draft into Tracked Files;
• prepare offers discovered during an import;
• create a site or campaign after the required details are approved;
• configure hosted, proxy, or redirect destinations, weights, rules, variables, tags, and conversion aliases.

Capabilities are discovered as the task needs them. The agent does not assume permission merely because the product has a related object.

Private draft, preview, save, and publish are different states

Every agent thread has its own private draft workspace. That draft can be edited and previewed without changing a production site.

Keep these states separate:

1. Draft: working files attached to the agent thread.
2. Preview: a reviewable rendering of the saved draft.
3. Files: durable content saved into the organization’s Tracked file workspace.
4. Published site content: a reviewed revision made live through the publication workflow.
5. Campaign route: a domain path connected to hosted, proxy, or redirect destinations.

Finishing a draft does not automatically perform the later steps.

Import an existing landing page

A guided import should preserve the page before changing its tracking behavior.

1. Inspect the imported files

The agent identifies the entry page, supporting assets, forms, scripts, pixels, and outgoing links. It should preserve policy, navigation, social, form, and analytics behavior unless you explicitly include those elements in the requested change.

2. Review outgoing offer links

Imported advertorials often contain several old tracker URLs, direct affiliate links, navigation links, and disclosure links. The agent separates candidate offer actions from links that should remain untouched.

You choose which outgoing destinations become tracked offers. Ambiguous links need a decision; they should not be rewritten silently.

3. Prepare offer slots

Approved offer destinations can become private Tracked offers with distinct /click/N slots. Separate destinations receive separate slots so the page structure and click intent remain visible.

Preparing offers is an approval-gated write. It does not publish the page or create the campaign.

4. Update the draft page

The agent replaces approved CTA destinations while preserving the rest of the page. Script-driven buttons should still use an anchor href so the campaign-relative click path and attribution context survive.

5. Preview and refine

Review the page at desktop and mobile sizes. Check layout, assets, forms, click targets, disclosures, and tracked slots. Refine the draft before saving or publishing.

Use the agent to connect analysis to an edit

Because the agent can read supported Tracked analytics and work on referenced files, one thread can move from a campaign question to a page change without losing the campaign context.

For example:

1. compare conversion rate or revenue across landing pages;
2. break the result down by device or supported macro;
3. inspect the page associated with the weaker segment;
4. edit the private draft;
5. preview the change;
6. save and publish only after review.

The analysis is evidence for the edit, not proof that the edit will improve results. Measure the new revision after traffic reaches it.

Build a campaign with the agent

After hosted files are live under the intended site, the agent can prepare a complete campaign request with:

• a campaign name and route;
• a site or domain;
• hosted folders or approved proxy and redirect URLs;
• weighted landing-page destinations;
• tracked offers and click slots;
• routing conditions;
• custom macro values;
• tags and conversion aliases.

Campaign creation is an approval-gated production write. The target site, route, and destinations need to be unambiguous before approval.

What the agent does not do silently

The Site Agent does not treat a draft as published, invent destination URLs, bypass workspace permissions, or turn a preview into a live campaign. It does not need unrestricted access to every tenant or file tree.

The important actions remain reviewable:

• saving durable files;
• preparing offers;
• creating sites;
• creating campaigns;
• publishing a reviewed revision.

That boundary lets the agent do substantial work without collapsing creation and production release into one hidden step.

Frequently asked questions

Can Tracked Site Agent edit an existing landing page?

Yes. When the relevant files are referenced into its private workspace, the agent can inspect and edit them while preserving unrelated behavior.

Does an agent edit immediately publish the page?

No. Draft editing, preview, saving, publishing, and campaign creation are separate actions.

Can the agent create weighted campaigns and routing rules?

Yes. The governed campaign capability supports hosted, proxy, and redirect destinations, offers, explicit weights, conditions, variables, tags, and conversion aliases.

Can it analyze campaign performance before editing?

Yes. The agent has supported tools for totals, sales, trends, funnels, traffic quality, and breakdowns within the authorized organization.

Start free and work on a landing page with Tracked.