Once your journey is fully configured, the next step is to publish it. Publishing a journey makes it available for use in different environments. GBG GO allows you to publish journeys in two environments:
OptionPurpose
PreviewAllows testing before going live. Generates a schema for API integration.
ProductionDeploys the journey live for real users. Once published, the journey cannot be edited directly.
Publishing to Preview allows the development team to test API calls and verify that the journey is functioning as expected.

​
Publish to Preview

Publishing to preview allows you to test your journey before making it live. To publish to Preview:
  1. Click Publish to Preview in the journey editor.
  2. A confirmation message appears: Delivery deployed successfully.
  3. Click on Dashboard to see:
    • Environment (Preview)
    • Version number
    • Resource ID
    • Last published date
    • Schema
  4. The schema for your journey is automatically generated.

​
Understanding the schema

The schema defines what information is required for the modules in your journey.
  • If a new module is added, new fields may be included in the schema.
  • If a field is already used, it will be shared between modules (e.g., an address field used in multiple verification steps).
  • Developers can copy the schema and use it for API integration with Postman or other tools.
Ensure your journey is fully tested in Preview before publishing to Production. Any changes will require creating a new version.

​
Publish to Production

Once testing is complete, you can publish the journey to Production. This makes it available for real users. To publish to Production:
  1. Click Publish to Production in the Dashboard.
  2. A confirmation message appears, prompting you to verify the journey settings.
  3. Click Confirm to proceed.
  4. A Production Resource ID is generated.

​
Important considerations:

  • Once a journey is published to Production, it cannot be edited directly.
  • If changes are needed, you must create a new version of the journey.
  • You will have two Resource IDs (one for Preview and one for Production).

​
Example use case

A business user creates a journey and publishes it to Preview:
  • The developer retrieves the schema, integrates it with their system, and runs tests.
  • After successful API testing, the business user publishes the journey to Production.
  • The journey is now live and can be used by real customers.

​
What’s next?

After publishing, the journey is ready for integration with your system.