Free live webinar

Same team, more pipeline: AI-powered marketing for Dynamics 365 · Wed 11 Nov · 1:00pm ET · with Microsoft MVP Mark SmithSame team, more pipeline · 11 Nov

Save my seat
Get pricingBook a demo

Web artifact

A web artifact is a standalone web page — something like a landing page, event page, or web form — that isn't part of your main website. It's built for a specific purpose: sending traffic from an ad or email, collecting sign-ups for an event, or hosting a form that feeds directly into your contacts. Create one whenever you need a page you can link to on its own, without going through your website's usual pages and navigation.

How to create one

Start a session anywhere in the app and describe the page you want. Pulse's "New report" is a good place to start if the page isn't tied to a specific campaign yet. If it is, open that campaign's chat so the assistant has the right context.

Describe the page's purpose (a landing page, a form, or a combination), who it's for, the main thing you want visitors to do, and any fields you need collected if there's a form. You can also point to an existing page elsewhere on the web and ask the assistant to build something similar, re-skinned in your own brand. See Using AI sessions for more tips on writing a good prompt.

Example prompts

Quick

  • "create a web form to capture a prospect's name and email"
  • "create a landing page for registering for a promotional webinar streaming on the 4th of next month"

Fully specified

  • "create a new web form called 'Contact Us' which I'll embed on our website's contact page. It needs to capture email, first name, last name and phone number, and leave a place for notes."
  • "Design a registration landing page for a webinar on no-code data integration. Audience: operations, IT and finance at mid-market companies. Sections: a headline leading with the outcome, a short value paragraph, speaker bios, an agenda, and a short signup form. Primary CTA: register free."

Fields that branch

  • "create a web form that asks for name and email and has a select list to choose a region out of: North, South, Center. If they choose North, ask for their role. If they choose South, ask for their team size. If they choose Center, ask for their industry."

A page plus a gated download, or a copy of an existing page

  • "create a new landing page for sharing a white paper. The white paper is available after the prospect submits their email in an embedded web form inside the landing page. The white paper is called 'The Integration Playbook'."
  • "copy the landing page at [url] into a new landing page about warehouse logistics"

What happens after you ask

If your request leaves something important open — the page's purpose, audience, or main call to action — the assistant will ask before it starts designing. Otherwise, it produces a complete draft page and saves it to your Library.

If the page collects an email address and you have a subscription list set to require double opt-in, you'll also be asked whether the form should offer email sign-up and for which lists. It's never added on its own — plenty of forms collect an email without being a newsletter sign-up. Say yes and each chosen list gets its own unticked checkbox showing that list's description. See Double opt-in for what happens after someone ticks one.

The page is not published or made publicly accessible at this point — it's a draft you can preview, and it stays that way until you publish it yourself from the artifact's preview panel. You can ask the assistant for small text or link swaps, or bigger changes to the layout and copy, as many times as you like before you're ready to publish.

If a change isn't what you wanted, click Undo in the preview panel, open History to go back to an earlier version, or ask the assistant — see Version history.

In the preview panel

Open the web artifact to see its preview panel. Close, Publish (or Unpublish once the page is live), and View live are available from any tab.

For most pages, click the pencil icon on the Preview tab to edit the page's content directly in a Visual view — click and change text, images, and links, and your changes save automatically. Editing always updates the draft. If the page is already published, your edits don't appear on the live public page until you publish again — the Publish button switches to "Publish changes" and is highlighted as a reminder that the live version is now behind your draft.

Some pages are built with their own embedded script that renders the page's content — certain interactive forms, for example. Because that script would overwrite any visual edit as soon as the page reloads, those pages don't have a pencil icon at all — there's no direct way to edit their content in the preview panel. Ask the assistant in chat to make the change instead; it edits the page's underlying code directly.

If the page collects form submissions, its Submissions tab lists them, with a Download CSV button to export them. The Name and Email columns show what the form's field mapping resolved — so a form whose fields are called "Full name" or "Work email" still fills them — and open a submission to see every field exactly as it was sent.

What happens to a form submission

The email address on a submission decides which contact it belongs to:

  • A new email address creates a new contact, filled in with every field the form collects and maps — name, phone, company, job title, address, tags, custom fields and so on (the Mapping tab shows which form field goes where).
  • An email address you already have finds that contact and fills in only what's missing. Anything the contact already has is kept, so a form can't overwrite what you know about someone. A form can't tell who is submitting it, though, so it can fill a field that's empty — give a phone number to a contact who has none, for example — which makes a value that arrived this way an unverified one. Tags are added to the contact's existing ones, and a form can switch a "do not contact" setting on but never back off.
  • No email address (or one that isn't a usable address) is saved as an anonymous submission and doesn't create a contact.

Phone fields have a country picker. Every phone field on a page shows a two-letter country code inside the field (US until the visitor picks another), and the number is formatted as it's typed: (202) 555-0143 for the US and the other +1 countries, +44 7400 123456 for everyone else. Typing or pasting a number that starts with + or 00 switches the code by itself. If the field's placeholder is itself a phone number, such as +1 (000) 000-0000, it shows an example number for the picked country instead. A number that isn't a real one gets a quiet hint under the field — "Not a valid UK number" — but the visitor can still submit. A phone field that sets its own pattern or a short length limit stays a plain field, so the page's own rules keep working.

What's saved. The form submits exactly what's in the field, and a mobile, work or home number is saved only if it's a real one (a custom phone field keeps what was typed). A number without a + or 00 is read as a US number first, then as a country code followed by the number (972542234547), and only then in the contact's own country — so a local number like 054-223-4547 is read when the form also collects the contact's Country, or the contact already has one on file. A mobile number is saved in international format; work and home numbers are kept as typed when they fit in 20 characters, and a longer one is saved in international format, without its extension.

Pages made before the picker get it in their draft the next time they're saved (ask the assistant for any change, or edit the page yourself), and a live page shows it to visitors once you publish it again.

Repeat submissions are held back. If the same visitor sends the same form again within 10 seconds — the same page, from the same internet connection, with the same email address (or with no email at all) — the second one isn't saved, and that visitor's further submissions to that form are ignored for the next 30 minutes. This catches double clicks and a page that keeps re-sending on its own, which would otherwise create duplicate submissions and start any journey triggered by the form over and over. The visitor still sees the form's normal confirmation, so nothing looks broken to them. Different people sharing one office or venue connection aren't affected as long as they enter different email addresses.

Forms are checked before they're saved. When the assistant builds or edits a page, its form code is checked to make sure it only sends when a visitor actually submits it — never on its own when the page loads, on a timer, or again after it has already sent. A page that fails the check goes back to be fixed and isn't saved to your Library until it passes.

A value that can't be saved doesn't lose the submission. If a single field can't be used — a phone number that isn't a real number, a date that isn't a date, a number that isn't a number, a country that isn't recognised, a value too long for its field, a choice that isn't one of a drop-down field's options — that one value is skipped and the rest of the submission is saved as usual.

Two more tabs cover how the page is performing once it's live: Stats for the page's own headline figures, and Analytics for the visit and traffic breakdown described in Web tracking. Both stay empty until the page is published and starts receiving visitors. The Preview tab also has Desktop and Mobile view modes.

Sharing and embedding

Once a page is published, its Share tab gives you everything you need to put it in front of people:

  • Public URL — the page's own web address. Copy it, or use the QR code underneath to open it on a phone.
  • Embed — a snippet to paste into another website, so the page appears inside one of your existing pages.

There are two embed formats, and the Share tab tells you which is which:

  • iframe — a plain snippet that works on practically any website, including page builders that don't allow scripts. It uses a fixed height of 600 pixels, so a longer page scrolls inside the frame.
  • script — a small loader that inserts the page for you and then grows it to fit the full content, with no inner scrollbar. Use this one when your website lets you paste <script> tags and you'd rather the embed size itself.

Pick a format, click Copy snippet, and paste it into your site's HTML.

FAQ

Q: Where do I actually publish the page once I'm happy with it? A: Use the Publish button in the preview panel's toolbar — it's available from any tab, not just through the chat. The assistant builds and revises the page, but you control when it goes live.

Q: I edited a page that's already live — did that change what visitors see? A: Not yet. Edits always update the draft first. If your draft has changes the live page doesn't have, the Publish button switches to "Publish changes" and is highlighted — click it to push those changes live.

Q: Can I get an exact copy of a page I already made? A: Yes. Ask the assistant to clone it. That creates a fresh, unpublished draft with the same content, which you can then edit independently of the original.

Q: A visitor typed their phone number into my form but it didn't reach the contact — why? A: Usually one of three reasons. The contact may already have a phone number: a form only fills in what's missing, so it keeps the number you have. The number may not be a real phone number: the field shows a hint while the visitor types, but they can submit anyway. Or it may be a local number from outside the US with no country anywhere: with the country picker that's rare, because the field adds the country code as the visitor types, but a page made before the picker (and not published since) doesn't have it yet. The rest of the submission is saved either way.

Q: Which JavaScript libraries can a page use? A: Every page is built on the platform's own runtime — Preact with hooks and htm — at fixed versions that only change when the platform changes them. The assistant can add other open-source libraries, web fonts and stylesheets too, always pinned to an exact version, so a library's new releases don't change your page. Loading data from other websites while a visitor views the page isn't supported. Embedding videos, maps and other sites in a frame is supported, and so are libraries that do their work in the background, such as confetti effects.

Q: Why does the preview say "When published, the browser blocks …"? A: The Preview tab applies the same security rules as your published page, so anything those rules would stop shows up before you publish. The note lists what would be blocked, for example data the page tries to load from another website. It appears in the Preview tab only, not while you are editing the page. To fix it, ask the assistant in the chat, or use the "Ask the agent to fix" button, which is there only while the chat is open.

Q: Can I change how form fields on the page map to my contact fields? A: That's handled in the page's preview panel under its Mapping tab, rather than through the chat. Open the artifact there to adjust it.