Best Practices

​

Journey execution

This section outlines best practices for executing journeys in GBG GO.

​

Use specific journey versions

Always use specific journey versions instead of @latest in production environments.

// Not recommended
{
  "resourceId": "8c24f3a5b76d09e182c397fd45c91ae3f8b530d7a19e64c2bd93f5a76c48e09f@latest"
}

// Recommended
{
  "resourceId": "8c24f3a5b76d09e182c397fd45c91ae3f8b530d7a19e64c2bd93f5a76c48e09f@3x5wz848"
}

​

Why this is important

• Using @latest can introduce up to 10 minutes of processing delay.
• Prevents unexpected changes when new journey versions are published.

​

Module dependencies

This section outlines best practices for managing module dependencies in GBG GO.

​

Configure NameMatch module dependencies

When using the NameMatch module, ensure DocumentExtraction module is added to the journey as a dependency.

The NameMatch module requires extracted document data to function properly. Without DocumentExtraction:

• NameMatch verification may fail.
• Users may experience incomplete verification flows.

​

Implementation best practice

• Add DocumentExtraction module before the NameMatch module in your journey.

Check the guide Best practices for ordering document modules in GBG GO to learn more about module ordering and dependencies.