Help Centre

Guides for every part of Gorilla Dash

Step-by-step how-to guides written by the team that builds the product. Read them here, or download any guide as a PDF.

Integrations

Connecting a tribe to CoreBridge

The onboarding token, what the progress panel is telling you, choosing the tribe's CoreBridge location, and the one thing not to do while a connection is being made.

Last updated September 16, 2026

CoreBridge is the point of sale a large part of the Gorilla Dash network runs on, and it is connected per tribe rather than once for the organisation, because each tribe has its own CoreBridge account. Open the tribe, select Software Integrations, and find the CoreBridge card.

Newer CoreBridge accounts connect through CoreBridge EVO, which issues the credentials to Gorilla Dash itself rather than asking you to copy them across. That is the flow described below.

Making the connection

Open the CoreBridge EVO integration on the tribe and select Generate Token.
Copy the token. It is shown once and once only, and it expires — the screen tells you when.
Paste it into the CoreBridge EVO marketplace to link this tribe.
Come back to Gorilla Dash and watch the panel. It shows each step as it happens: CoreBridge confirming the link, then Gorilla Dash collecting the keys, then the tribe connected.

Do not press Save while the connection is being made

CoreBridge writes the credentials into Gorilla Dash itself, and it issues a fresh pair every time — the previous pair stops working the moment a new one is made. Saving over credentials that have just arrived used to lose them irrecoverably, and the tribe would stop importing sales without any visible error. Gorilla Dash now refuses to overwrite credentials it wrote itself, but the habit is still the right one: let the panel finish, then save.

If the panel says the token expired before CoreBridge used it, that is the whole problem — generate a new one and paste it in more promptly. If it is still waiting on CoreBridge, close the window and open it again later rather than sitting on the page; nothing is lost by leaving it.

Where a tribe is already connected with working credentials, the panel says so, and generating a token again is unnecessary.

Choosing the location

A CoreBridge account can cover more than one site, so Gorilla Dash needs to know which of them this tribe is. Once the credentials are in place, the settings dialog reads the sites straight from CoreBridge and lists them by name, with the identifier shown beside each. Choose the right one and save.

Before the credentials exist, the field explains what is still needed rather than presenting an empty list. If it says Gorilla Dash could not reach CoreBridge, that is a problem at the CoreBridge end rather than with your credentials, and Refresh is worth trying before anything else.

THIS IS SET PER TRIBE

CoreBridge locations belong to a tribe, not to the organisation, so there is no way to set one centrally for everybody. A tribe whose sales are landing against the wrong site has the wrong location chosen here, and it is the first thing to check when one tribe's figures appear on another.

Removing it

Removing a CoreBridge EVO integration clears the pairing as well as the credentials, so the tribe is genuinely disconnected rather than left half linked to a business it can no longer reach. Reconnecting means generating a new token and going through the marketplace again — there is no way to restore the old credentials, because CoreBridge no longer has them either.

Next · IntegrationsEVO integration setup: information we need