Skip to the main story
RecipeJam

Recipes, collections & other kitchen matters

Ad-free · Yours, full stop. · ?.??

Business intelligence

Local Food Company Discovers Where Its Recipe Traffic Comes From

Management had previously relied on a mixture of guesswork and asking Janet.

What RecipeJam does about it

Higher plans are built for businesses that need to know whether any of this is working: their own tracking on published collections, richer publishing controls, and an API for the ones with a website that should be showing the recipes too.

RecipeJam, in use

A recording of this, in the real application

Business collections, publishing controls, and where tracking is configured.

Filmed in RecipeJam itself, not an animation. Coming shortly.

Available now: the API

A documented REST API over recipes, collections, books, photographs and shopping lists, with tokens you make yourself. If your website should be showing your recipes, it can read them from here.

Available now: your own analytics tags

A published collection is an ordinary web page on your own link. Whatever you already use to measure your website can measure this.

Planned: per-collection reporting inside RecipeJam

Scan counts and recipe-level figures reported back to you in the application, rather than in someone else’s dashboard. This is on the roadmap and not yet built — we would rather say so than show you a screenshot of it.

Everything above marked “planned” is exactly that. Nothing on this page is a feature we are pretending to have.

Read on