Your connector pushes the data: CrossUp updates your recommendations.

​
Three steps

1

Connect your store

In the CrossUp admin, add your store. You get a connection_id (cn_…), which goes in the path of every call.
2

Issue your connector key

From the admin, issue a cct_… key. It is shown only once: store it in your server’s secrets.
3

Send catalog and orders

The first time, all at once with a snapshot. After that, each change. Initial sync walks you through it.
You can have everything integrated and loading before you subscribe. Recommendations are served once the subscription is active: plans are at crossup.ai/pricing.

Request your connector setup

Tell us which platform or system you run and we build the connector with you.

​
Where it fits

  • VTEX or another platform without the CrossUp app.
  • Your own or headless store: your backend already has the catalog; the connector forwards it.
  • An ERP or a file: one export a day is enough, sent as a snapshot.
  • A platform with many stores: the same code serves all of them. Each store is a connection with its own key.

​
Your connector key

The cct_… key lives on your server, never in a browser, and goes in Authorization: Bearer. It works for one connection only.
  • It doesn’t expire. An automated process can’t depend on someone renewing it.
  • Up to 5 active per connection: production, staging, an ERP, a migration.
  • The admin shows it by its last four characters (cct_…7k3m), so you know which one is deployed.
To rotate it without stopping ingestion: issue a new one, deploy it, then revoke the old one. The last active key can’t be revoked, because ingestion would stop silently.

​
What you’ll see

In the admin, your store connected and your key with its last four characters. With the initial sync, every batch answers entity by entity.

​
If you don’t see it

Initial sync

Your catalog and historical orders, in one go.

The canonical model

Which entities you send and which fields they carry.