Personalization

Regenerate and restore

Versions are never lost quietly. When a page gets a new version, the old one moves to Archived versions, where you can bring it back. This guide covers Archived versions and Restore, asking adfit for a fresh version, why a run can come back with nothing to change, and what to do when your page changes.

Archived versions and restore

When you publish a version of a page while another version of the same page is already live in that personalization, the one that was live moves to Archived versions. The same happens when you regenerate a draft, unpublish a page, or when adfit applies your plan limits. Nothing is deleted, and visitors only ever see the version that is published now.

You will find the archive on the personalization itself: under Changes, open Archived versions. Each entry shows the date it was archived and how many changes it carried, with a Restore button next to it. A version that a regenerate replaced carries the mark Has been regenerated (its tooltip reads This version was replaced by a regenerated one). adfit keeps the last five versions of a page.

Restore asks how to bring the version back: Choose how to bring this version back.

  • Restore as draft: adfit adds this version as a draft. Your site does not change until you publish it. If the page already has a draft, that draft moves to Archived versions and you can restore it later. This works even while your plan is on hold.
  • Publish now: visitors see this version on your site within about a minute.

Publishing a restored version is a swap, not an addition

Publish now publishes the version you picked, and the version that was live until then moves to Archived versions. You can restore the other one back later.

Two limits can switch Publish now off, and the restore dialog says which one applies. If your plan's limit of live personalizations is reached, it says, for example, Your plan allows 5 live personalizations per site. Unpublish one, then restore this version. If the personalization already has the most live pages it can have, it says A personalization can have up to 25 live pages. Unpublish a page, then restore this version. In both cases Restore as draft still works. To publish the version, first unpublish a personalization or a page, as the dialog says. An archived version is never published by accident, which is why it has no Publish button of its own.

Limits are also the reason pages end up in the archive without you doing anything: see When your plan or its limits change.

Regenerate a personalization

To have adfit write a fresh version of a page, open the personalization on that page, press Regenerate, then confirm. adfit only ever touches this personalization, never another one of the same persona. The dialog says what happens to what you have: if the page already has a draft, adfit writes a new version of this page. Your current draft moves to Archived versions, marked "Has been regenerated", and you can restore it from there. If only a live version exists, adfit writes a new draft for this page in this personalization. Your published version stays in place until you publish the new draft.

Before you confirm, the dialog shows what the run costs: This uses 1 AI task. If adfit finds nothing to change, that run is usually free. If the next empty run would already count, adfit warns you instead of promising a free run.

There is no undo bar after a regenerate, because nothing is overwritten: the draft before it is in Archived versions, marked Has been regenerated, and you can restore it from there. The new version appears on its own when it is ready and carries the mark Awaiting approval: see Keep or discard a draft.

When you regenerate from an ad suggestion, adfit asks for a short note first (What should adfit focus on this time?) so it knows what to change. You can also set the Depth for that run (Cautious, Balanced or Bold), or leave it on Site default to use your site setting.

Sometimes there is nothing to change

If adfit finds nothing it can safely change, it says so instead of writing a version (and the run is usually free, see When a run comes back with nothing): adfit found nothing to change on this page. That is a result, not an error. Under it, adfit says why whenever it can: see Why adfit found nothing to change. When it has no specific reason, it suggests adding or rewording a few elements and trying again. adfit never changes checkout, cart, account, login, or legal pages; on those pages it says adfit did not personalize this page. instead and tells you that trying again gives the same result.

Why adfit found nothing to change

When a run ends without changes, adfit names the reason in a single sentence. You see the same sentence wherever that run shows up: under the result on the personalization or persona, in the tooltip of the Nothing found chip in your list, in Details of the status card, and, after the word Skipped:, in the results card of Extend to other pages. What the sentences mean:

  • adfit could not match this personalization's message to any text on this page. Try a page about the same topic. Nothing on the page fit the message of this personalization. A page about the same topic gives adfit something to work with.
  • adfit needs more text on this page to suggest a change. Try a page with more headlines and copy. adfit did not find enough text on the page to base a change on. Pages with more headlines and copy work better.
  • adfit left this page as it is because its text already fits this personalization's message. Good news: there is nothing to improve here, so there is nothing to do.
  • adfit left this page as it is because every change would have altered what the page says, not just how it says it. adfit rewrites wording, not meaning. Nothing to do.
  • adfit could not change the text on this page without breaking its formatting, such as links or bold words. The text sits inside links or styling that a rewrite would break, so adfit left it alone.
  • adfit only had ideas that would change a price, and prices are never changed. Try a page that is not mainly about pricing. adfit never changes prices. A page that is not mainly about pricing gives it more room.
  • adfit never changes checkout, cart, or legal pages, and this page looks like one. adfit judged this from what is on the page. Nothing to do.
  • adfit dropped every idea for this page because each would have broken a content rule, such as a claim your site does not back up. For example a guarantee or a “number 1” that your own pages do not state. adfit leaves out claims your site does not back up.
  • adfit was not confident enough in any change for this page. adfit prefers to leave a page alone over making a change it is not sure about.
  • adfit needs a fitting image for this page, and your image library has none. Add more images to the library, then try again. The only fitting change was swapping an image. Add images in your image library.
  • adfit only had image ideas for this page, and image swapping is not included in your current plan. This is what you see instead of the previous one when your plan does not include image swapping. There is nothing to add to your library; see Plans & pricing for what each plan includes.
  • adfit cannot find any elements on this page to suggest changes for. If the page changes, ask adfit for ideas on it again: adfit reads a changed page again at most once every 7 days. adfit did not find any elements on the page to suggest changes for, for example because the page has little content yet. When you change the page, ask adfit for ideas on it again.

Regenerate changes the wording, not the tone

Regenerating is the way to get different suggestions. To change how many elements adfit touches, adjust your personalization depth; to steer the wording, update your AI briefing first.

When Regenerate is not available

Regenerate is disabled, with a reason next to it, in a few cases:

  • The personalization came from an ad. Regenerate it from the ad instead: see Re-analyze an ad.
  • It is the "All pages" entry, which applies to every page of your site. Regenerate works on one page at a time.
  • No persona is assigned yet. Assign one first.

When your page changes

A personalization remembers the original text it replaces. If you later edit that text on your site, adfit flags the personalization with an Original changed badge and a note on its detail page, so a change can never quietly go stale.

Review the changes against your current page. If the new text is correct, press Update baseline: adfit takes the current text on your page as the new original for this personalization, and the flag clears. If the text is not available yet, adfit says adfit has not read this page recently. Open it once with the snippet installed, then try again.

Updating the baseline ends the running test

Updating the baseline of a published personalization ends the personalization's current run, because the comparison would no longer mean the same thing. When an A/B test is running on a live personalization, adfit asks first: End the running A/B test? It does not restart on its own. You can start a new test with Restart experiment in Performance. A personalization that adfit only observes (no A/B test) ends its run the same way, without a question. See The original changed.