Build an offer and close the loop on it

Most offer work stops at launch. The tool that matters most here is the last one, which is the one that turns a result into something the next offer knows.

Look before you build

Analyse the offer opportunity for shop your-store.myshopify.com and explain the reasoning, not just the recommendation.

gem.analyze_offer reads the catalog and order context through the offer brain and returns a recommended strategy. It is read-only, so this costs you nothing but time.

Push back on it. The useful follow-up is usually:

Which of those assumptions depend on order history you can actually see, and which are inferred?

Register the strategy

Create the offer strategy from that analysis.

gem.create_offer_strategy runs the brain and registers the resulting artifacts, the strategy and any bundle template, inside GemBoss. This is draft level work: it creates things in GemBoss, and touches nothing in Shopify.

Close the loop

When a campaign that tested the offer has been decided:

Report performance for that campaign back against the offer.

gem.report_offer_performance takes a decided campaign that tested an offer arm and feeds the outcome back. Skip this and every future analysis is working from the same starting knowledge as the first one.

Check what is running

List the shop's campaigns and their status.

gemboss.list_campaigns on the analytics server lists governed campaigns, which are the unit that launches and tests run through. Note the different server: read-only, separate key.

A caution worth stating

The offer brain proposes. It does not know your margin floor, your supplier constraints or the promise you made to a wholesale partner. Read the strategy as a well-informed argument, not an instruction.

Next

• Launch an advertorial funnel
• Diagnose conversion