Your StageGlide guide.
StageGlide is a staff-operated private preview. Public campaign pages are available to visitors. Follow this workflow to prepare and share an offer.
1. Prepare content locally
Run Content Studio on your development machine. Create a project, prepare captions and media, preview the output and export its files and manifest. Studio and its AI keys stay local. Optional AI requests use the provider configured on that machine.
2. Review your social content
Open the staff workspace and choose Social → Content drafts. Import a Studio manifest or create a draft, upload finalized files, review the caption and approve its exact revision. Then set its schedule. Editing an approved draft requires approval again. Check Social jobs for status and errors.
Real publishing is disconnected. A saved schedule is a plan; blocked jobs are not successful posts. AutoDM rules can be simulated without sending messages.
Plan and test social engagement
Content planner sets a draft’s Facebook or Instagram target and format. Target changes clear approval and schedule. Social → Contacts stores invented test recipients, tags, lead stages and notes. Opt-out and human handoff stop automation.
In Engagement flows, choose a comment-to-guide, message-keyword or Instagram-story template. Save its copy, campaign link, optional post scope and tag condition. Mark the flow test-ready, select a test contact and run an event. The decision trace shows the opening reply, tags, wait and follow-up eligibility; it sends nothing. Reusing an event key is rejected. Social → Inbox retains those test interactions; Social → Insights reports simulation counts, not real reach or delivery.
Comments alone do not permit continuing a DM sequence. Follow-up previews stop on reply, opt-out, handoff or window expiry. The supplied @stageglide account still requires professional status and Meta authorization before real sync or sending.
3. Publish a product
Choose Sales → Products. Enter a brand, unique URL slug, title, description, currency and price. Save the draft. Upload any resource files before publishing the current revision. Published product pages are public; payment collection is unavailable.
4. Build a campaign
Choose Campaigns & funnels → New campaign. Select a published product, enter the page copy and optionally select a free resource from that product. Configure the announcement bar, timer, tab message, exit prompt, anonymous proof and second page variation. Leave Demonstration campaign enabled when testing. Save and publish, then open the public campaign.
Offer timers are real server-enforced windows. A visitor window stays fixed in that browser. Changing a published campaign creates a new revision for measurement and visitor allocation. Pause a campaign to close its public page.
5. Test the visitor journey
Open the campaign, submit a test name and email, reach the thank-you page, download the selected free resource and view the offer. Free resource access lasts one hour in the requesting browser. Selecting a file here intentionally provides it free; do not select a paid-only file.
The offer's checkout availability check takes no money. Only the staff Checkout test lab can simulate a paid or failed order; simulations grant no real paid access.
6. Read reports and export leads
Open Leads & measurement and refresh the report. Compare page variations and campaign steps, review traffic sources and export the displayed latest 100 leads as CSV. Optional measurement requires visitor permission; unmeasured visitors are excluded from conversion denominators. Test activity stays separate from live totals and proof. Choose a split-test winner manually after assessing your results.
7. Test recovery safely
Use Recovery test lab to create a consented failed checkout simulation. Inspect the three reminder jobs at 1, 24 and 48 hours. Payment completion or unsubscribe cancels pending reminders. No customer emails are sent: real checkout and a sender must be connected first.
Storage and access
Staff sign-in uses Cloudflare Access. Never share login codes. Files are private, with a 10 MB per-file limit and 250 MB per-module intake limit. Visitor records expire after 30 days; leads remain until staff delete their details. Public campaign links do not provide dashboard access.