The Google Optimize migration, step by step.
New here? Start with the short version →
Step 1: Remove Optimize
Find the Optimize snippet (usually right after the Google Analytics tag) and delete it; also remove the anti-flicker snippet. Export any experiment results you care about from Google Analytics first (screenshots are fine); nothing imports.
Step 2: Install the Prept snippet
Paste one async script tag before </body>:
<script async src="https://prept.dev/snippet.js" data-site="YOUR_SITE_ID"></script>
Step 3: Tag elements
Add data-prept="headline" to the h1, data-prept="subcopy" to the supporting paragraph, data-prept="cta" to the button; the existing text is the fallback and never renders blank.
Step 4: Decide what each element should do
Headline = the promise (highest leverage). Subcopy = visitor-specific proof. CTA = first-timers get "See how it works", returning visitors get "Pick up where you left off". You tag; Prept writes the variants.
Step 5: Check the math
1 credit per new visitor, 0.25 per returning; a 20,000-visit/month page at half returning costs about 12,500 credits (~$36 on the 10,000/$29 pack rate). Your Optimize bill was $0, so weigh whether per-visitor copy is worth it — for paid-traffic pages, one extra conversion a month covers it.
What doesn't carry over
- Experiments (nothing to import)
- The anti-flicker snippet (delete it; Prept reserves layout space instead)
- Statistical significance (Prept doesn't run experiments; a 10% control holdout stays on your original copy so you can see the difference)
If you still need A/B testing
Keep an A/B tool alongside Prept — testing tells you which of two designs wins on average; Prept makes the copy fit each visitor. Many teams run both: test the layout, personalize the words.