Skip to main content


We are currently working on a UI for Destinations. This means that you'll soon be able to setup directly from the Enterspeed APP yourself. But note, the destination itself is fully ready for production.

For now, contact us if you want to get started.

The Enterspeed integration uses the destinations field to send data from views directly to a configured store. This means that you can decide on the schema level which views you want to send to

You will only have to set the destination field on the entity schema you want to send to All schema references are automatically resolved so you don't have to set it on all referenced schemas.

It's possible to configure multiple destinations if you need to push different types of data to different stores.


As of now the integration only support pages. We are working on adding support for all type supported in


In order to setup the configuration you need the following:

Clerk Public KeyThe unique public key of the store you want to integrate to
Clerk Private KeyA private key on the store you want to integrate to
Enterspeed Environment Client API KeyThe API key for an Enterspeed Environment client. This is used to fetch the view that will be inserted into


Table of available options, that you can optionally specify, if needed for your use case.

idBy default Enterspeed uses view id as the value for object id in Clerk. You can override default object id by providing value for this option.
clerkEntityTypeThe type of entity you want to send to Clerk. Supported values: page.

Example of usage specific properties

Each type in (page, product, category, ...) has a set of required field which must be mapped in the Enterspeed schema.

See required fields here:


id is set automatically or by the options id if you use that, so you don't need to map this property.