Getting started

Rankrake recommends items to your visitors and measures what those recommendations earn. To do that it needs two things from your site: your catalogue, so it knows what it can recommend, and the events your visitors generate, so it knows what they do.

The pieces

Account (tenant). Your organisation in Rankrake. It holds your sites, your dashboards and the people who log in to the platform.

Site. One website or store. Each site has a platform (Shopify, WordPress or an independent website) and its own keys. Use one site per storefront: a store and a blog are two sites.

Keys. Each site has two:

• a public key, used in the browser. It can only send events and ask for recommendations, so it is safe to put in your pages;
• a secret key, used on your server, for catalogue sync and anything else that changes data. Never put it in a page or in a public repository.

Catalogue (entities). The items Rankrake can recommend: products, articles, recipes, courses. Each item has your own id for it (its external id), a title, a url, categories and a status (active, inactive or deleted).

Events. What visitors do: a visit starts and ends, a page or item is clicked, a recommendation is shown, an item is added to the cart, an order is placed. Rankrake builds its recommendations and its metrics from them.

Choose your integration

• Shopify: install the app. It syncs your catalogue, tracks events and places recommendation blocks for you. No code.
• SDK: for any other website, custom store or headless setup. The browser part tracks events and asks for recommendations; the server part keeps your catalogue in sync.
• WordPress: a plugin is coming soon. Until then, the SDK works on WordPress.

Consent

Rankrake records nothing about a visitor until they agree to it. On Shopify this follows the store’s own consent banner automatically; with the SDK, you tell Rankrake when the visitor agrees or refuses.