The Publish feature in Experiences by Jebbit enables you to transform your current draft into a formal version of your experience, making it ready for audience engagement. Publishing is crucial as it saves a specific version of your experience, ensuring consistency for consumers accessing it via launch links.
Before you begin
Preview your experience to ensure it appears as intended across various devices.
Test each path to ensure questions or outcomes branch as expected.
Scan the QR code (accessible via the top-right icon) to view the experience on your smartphone.
Publish your experience
Navigate to the Builder map in your experience.
In the top right corner, select Publish once you are ready to save that version of the experience.
Name the version of the experience. Ideally, we recommend inputting the current date and the edit that was made, such as "first screen removed".
(Optional) select schedule options to:
a. Choose Publish Date & Time
b. Choose the Date & Time to Disable your ExperienceYou'll be returned to the Builder Map, where a small icon on the Publish button indicates that your experience is scheduled. This icon will disappear once the experience publishes at the specified time.
Publishing creates a record of the experience at that point in time and sets the iteration that your launch links will direct traffic to.
Editing after publishing
After the initial publication, you can make further edits to your experience in a new iteration.
The live experience accessed via launch links remains unchanged until you publish the new iteration.
To push updates live, click Publish again, creating a new version that reflects your latest changes.
Republish an older iteration
Ensure you have the correct permissions. If the iteration dropdown is not visible in your Builder Map, contact the Support team.
Use the Version dropdown in the Builder Map to locate the published iteration you wish to restore.
Select the iteration, note that you cannot edit published versions.
Click Publish to apply this version as your new draft.
Optionally, rename the version (e.g., include the date or describe the change).
Once published, your draft will reflect the restored version, which you can further edit if needed.
Comparing iterations
On the Question Analytics page, compare different published versions to assess how content changes impact performance.
FAQ
I can't find the iterations' dropdown. What should I do?
If you do not see the dropdown pictured in the screenshot in your builder map, then reach out to our Support team using the in-platform chat or emailing support. You may just need one of our team members to update your permissions for you.
When can I publish the experience?
You can publish the quiz without having to generate a launch link to share with the public. Since publishing saves a version of the experience, we recommend publishing the experience when you have designed at least 50% of your quiz.
What happens when you deactivate a campaign?
Once the campaign is deactivated, the launch link will redirect to the URL that you specify.
It seems like my iteration did not deactivate or publish at the time that I set?
Keep in mind that Jebbit uses the UTC timezone as a reference, so you will need to ensure that you set the date and time according to UTC.
How do I fix an “infinite loop” error when trying to publish my quiz?
If you see an infinite loop error when attempting to publish a quiz, it usually means that one of your screens is branching back to itself or creating a closed loop unintentionally. To resolve this, open the experience in the builder and look for a red line below the screen, this is a visual indicator of the loop. Disconnect the existing branch for that screen and reconnect it to the correct target screen to eliminate the loop. Try publishing the quiz again to confirm the issue is resolved. If you've reviewed your branching logic and the error persists, contact support for further assistance.
Why do the buttons in my experience work in preview mode but not on my website?
If the buttons in your experience work in preview mode but don't work on the live website, the issue is likely related to browser caching or local environment settings. First, ensure the experience is published, changes won't appear on the launch link until it is. Try opening the launch link in a private or incognito browser window to bypass cached content. If that resolves the issue, clear your regular browser’s cache and cookies, then reload the page. If problems persist, test the link on another device or browser.
I’m trying to publish my quiz, but it keeps saying I need to map attributes, what should I do?
If you’re trying to publish your experience and the platform continues to prompt you to map attributes, even though you’ve already done so, it’s likely that one or more attributes are assigned multiple times or are mapped incorrectly. This can happen when the same attribute is applied to more than one element, such as a text field and a checkbox. To fix this, review your attribute mappings and make sure each attribute is used only once across all screens. For any additional fields, especially optional or consent-related elements, use a unique attribute. After making these adjustments, try publishing again and the message should disappear.