3 min read

Snapshot deliverables, import once and run your Proof Engine

Load one GoHighLevel snapshot, switch on reviews, clips, and case snippets, then place proof on pages and emails. The pieces are small, named clearly, and built to refresh in under an hour each month.

TLDR

Import a single snapshot that includes review capture, UGC intake, a case snippet generator, a proof wall page, four reusable proof modules, and tracking. Use plain tags and one data model. Place a quote in hero, a snippet under pricing, and a clip near the final CTA. Refresh items monthly. Track lift by page and by module.

🏆 Start your Highlevel journey today

Learn more

What you get in the snapshot

  • Pipelines and tags: Clean stages for review_rescue and proof_refresh, plus tags for proof_clip, proof_quote, proof_snippet, stale_yes.
  • Forms: Review form with stars, text, consent; UGC upload with consent; snippet confirm form.
  • Workflows: Review ask and publish, UGC invite and intake, snippet creation nudges, rescue path, stale proof sweeper.
  • Pages: Proof wall, upload thanks, removal request, and a slim reviews LP section you can embed.
  • Email and SMS assets: Short asks, reminders, thank you notes, rescue macros.
  • Modules: Logo row, quote, snippet, clip, each as a block you can drop on any page.
  • Dashboards: By page and by module, with exposure, CTR change, paid change, and staleness.
  • Lists and fields: Data model for proof with consent text, source name, screenshot id, and last_refreshed date.

How to import and go live

  1. Import the snapshot and map forms to your primary domain.
  2. Update your brand and support email in global settings.
  3. Drop the quote block beside your first CTA, the snippet under pricing, and the clip near the final CTA.
  4. Link “Read more reviews” to your proof wall.
  5. Turn on review and UGC workflows. Set daily throttles to protect deliverability.
  6. Open the dashboards and confirm events fire on view, click, play, and complete.

Tags and custom fields, simple and readable

  • Contact tags: verified_paid, review_requested, review_posted, ugc_invited, ugc_received, snippet_ready, review_rescue.
  • Custom fields: proof_source (GA4, Stripe, CRM), proof_timeframe_days, proof_before_value, proof_after_value, proof_consent_text, proof_screenshot_id.
  • Module fields: module_id, module_type (logo_row, quote, snippet, clip), page_slug, position_above_fold (yes, no), last_refreshed.

Core workflows, in plain words

Review capture
Wait 14 days after verified_paid or a logged win, send one SMS and one email, publish 4 to 5 star reviews automatically, route 1 to 3 stars to rescue, store consent text.

UGC intake
Invite 21 to 45 days after verified_paid or after the first measured result, accept phone video or voice note, store consent, auto create captions, and add to the clip module library.

Snippet builder
Nudge internal owner to fill three lines, before, action, after, plus timeframe and source. Save a redacted screenshot and mark snippet_ready.

Rescue path
For 1 to 3 star reviews, open a task, reply human within 24 hours, offer one fix or a 15 minute call, and close when resolved. Only then ask for an update.

Stale sweeper
Nightly, tag proof items older than 180 days as stale_yes, queue them for the monthly refresh.

Pages that ship with the snapshot

  • Proof wall: Filters by niche, use case, timeframe, and media type. Cards for quotes, clips, and snippets. Links to pricing.
  • Upload thanks: Clear next steps and a reminder that removal is always available.
  • Removal request: Simple form with email and item type. Workflow removes within 72 hours and confirms.
  • Embeddable reviews section: Small, fast row you can drop on any LP.

Placement defaults you can copy

  • Hero: Two short quotes or a small logo row next to the first CTA.
  • Pricing: One matched snippet under the math, timeframe and source in line.
  • Final CTA: One 30 to 60 second clip with captions.
  • Comparison pages: Small table, our result vs baseline, each with a source.

Tracking that is already wired

Events fire on proof_view, proof_click, snippet_view, ugc_play, ugc_complete, and review_submit.
Each event carries page_slug, module_id, module_type, and position_above_fold.
Dashboards show exposure, CTR change, paid change, refund trend, and staleness.

Monthly refresh, built in

The dashboard flags stale_yes. Replace three items, retire three, ship, purge cache, and log the changes. Target under 20 percent stale at all times.

Safe defaults baked in

  • Consent text is stored with every review and clip.
  • Negative but lawful reviews are visible and routed to rescue.
  • Logos swap to name and role if permission is unclear.
  • Removal requests close within 72 hours.

Quick checks before you publish

  • Do quotes fit under 120 characters on mobile.
  • Do snippets include timeframe and source in the line.
  • Do clips have captions and a clear label.
  • Do all links resolve, and do pages load in under 2 seconds on a 4G connection.

Metrics to watch after go live

  • Proof exposure on top LPs, target 70 percent of engaged sessions.
  • CTR change with hero proof, target plus 15 to 30 percent.
  • Paid change with pricing snippet and clip, target plus 10 to 20 percent.
  • Refund rate, aim down 10 to 20 percent with clearer expectations.

Troubleshooting

  • Low exposure: Move the hero proof row higher and cut quote length.
  • Clip ignored: Add a clearer thumbnail and keep length under 60 seconds.
  • Numbers questioned: Add “view source” and link a redacted screenshot.
  • Library stale: Turn on stale sweeper and schedule the monthly refresh.

FAQ

What if I already have a reviews tool
Keep it for collection, route published items into the snapshot’s modules so placement and tracking stay consistent.

Do I need video to start
No. Quotes and snippets are enough. Add clips later where hesitation is highest.

Can I use this outside landing pages
Yes. Drop modules in lifecycle emails, help panels, comparison pages, and proposals.

How do I migrate old proof
Import quotes and snippets into the data model, attach dates, sources, and consent notes, then place them with the same modules.

How often should I refresh
Run the 60 minute sprint monthly and after any pricing or plan change.