By the end of this page you’ll have a CrossUp recommendation in your store and an accepted signal. You need your catalog in CrossUp, through the app or a connector, and twenty minutes.
1

Generate your key in the admin

In the admin: Settings → Keys for your storefront → Generate key. Copy the key and your connection identifier. The key goes in the browser: why that’s safe.
Can’t find the connection identifier? Ask support: there’s one per store.
2

Install the SDK, or get ready to call the API

In JavaScript, the SDK handles the visitor, the signal queue and retries. From any other language the API is enough: HTTP, JSON and the key in Authorization.
The package on npm: @crossup/storefront.
3

Request a recommendation

Tell CrossUp which moment the shopper is in and with what context. The recommendation comes back (in the API, Decision: the list of products recommended for that moment).
4

Use the recommendation

Every product comes complete, no extra call. The design is yours, with two rules: if it’s empty, show nothing; if there’s no price, don’t show $ 0.
5

Report the first signal

Without signals, CrossUp can’t tell the recommendation was seen or that it sold. Report when it’s shown and when the shopper opens it.

What you will see

On your page, the recommended products in your design. In the Network tab, a request that returns a decision_id (the recommendation’s id) and, a few seconds later, a signal send that returns accepted.

If you don’t see it

Signals and attribution

The seven signals and how the sale is measured.

Request recommendations

Each moment with its request and what comes back.