Skip to content
Request a demoDemo

Signature feature · Integrations

Keep what already works. Connect Livstick where it matters.

Use a link, QR code, widget or API to add video gifting to the operational, marketing and technical systems your brand already runs.

Find your situation Talk to us about your setup
  • Online or in store
  • Embed it, or link to it
  • Your brand throughout
  • An open developer portal
A store advisor shows the card attached to a gift bag at the counter
Start with one linkembed it later
Ways in yourbrand.com
  • Online In your pages, or one link
  • In store A printed code
  • Your systems They can drive it
  • Built by Your team, or ours

One option added, nothing removed

Example brand and order, for illustration.

01 — What it changes

Video gifting fits into the way you already work.

The question is not whether to replace your systems. It is where a message belongs in the journey they already support.

Tap a way in. Each number is something that stays yours.

Example brand

gifts.maisonlune.com Maison Lune

Record a message for Marc

Léa records her message in the brand’s recorder REC 0:28
Retake Send

One link — nothing to embed

The whole journey runs on our page, under your brand.

  1. Hand over a link Hosted linkLink From your emails, your receipts or a counter: the journey opens on the hosted page.
  2. Your brand, our page Hosted linkLink Domain, logo, type and wording are yours; nothing says Livstick.
  3. Sent from your own tools Hosted linkLink No page touched, no release booked: your team sends the link today.
  4. Then embed it later In your pagesWidget Once the programme proves itself, the same journey moves into your pages.

MAISON LUNE is an example brand, for illustration.

For the business
  • No release train to wait for.
  • The journey your customers know stays as it is.
  • One brand throughout — yours.
For whoever builds it
  • An open portal, guides and references.
  • One key per brand, one per environment.
  • The same platform behind every way in.

02 — Find your situation

Nine situations, a clear route into each.

Start with the situation that sounds like yours. We’ll help you choose the right link, QR code, widget or API.

  • Where you sell

    Online, at a counter, or neither
    • You have an online storeThe gifting step appears in your own pages, at the point you pick.
    • You sell across a counterA printed code travels with the card, box or bag you hand over.
    • There is no website in the flowWe prepare the batch of codes; you print them and hand them out.

  • What you already run

    Nothing gets replaced
    • A checkout you wrote yourselfThe step drops into the page you have, without redrawing the funnel around it.
    • An email platform you will not replaceYour own message carries the link, and we open the gift once you say it arrived.
    • An order system that knows everythingIt creates the gift under your own reference, and decides when it goes out.

  • Who does the work

    Your team, an agency, or nobody
    • Nobody, on your sideHand over one link: the whole journey runs on our page, with nothing to embed.
    • A technical team of your ownAn open developer portal, three live API versions, references they can read today.
    • An agency or an integratorNothing here assumes an in-house team, and each key is scoped to a single brand.
The platform 4ways in: link, QR, widget, API 3live API versions 100,000codes per prepared batch 1key per brand Prepared batches and printable card templates are set up by our team, not from a self-serve screen.

03 — What it produces

Sooner, without replacing anything, and still yours afterwards.

Three gains, rarely for the same desk.

Speed

You can be live before your next release

The lightest way in asks nothing of your pages: start with a link, embed it once the programme proves itself.

  • Start with a link
  • Embed when you are ready
  • Nothing to rebuild first
Fit

Nothing you already run has to be replaced

Your funnel keeps its steps, your emails their sender, your order number stays the reference.

  • Your funnel, its own steps
  • Your sender, unchanged
  • Your reference, end to end
Control

What changes later does not need a release

Steps, wording, language and theme are read when a journey starts, never compiled into your site. Changing them is our job, not your backlog’s.

  • Changed for you
  • No release to wait for
  • Per brand, per batch

The people who run the programme rarely write the code.

  • A link your team can send
  • A widget your agency can place
  • An API your systems can call
A programme manager and a developer review an integration together on a laptop A programme manager and a developer review an integration together One link to hand over today

04 — Why it matters

Programmes rarely die on the idea. They die in scoping.

Four reasons — and the two things we do not claim.

  1. The integration decides whether it happens

    An idea that needs six months of roadmap is an idea that waits a year.

  2. Your journey is not up for redesign

    Nobody rebuilds a checkout that converts. Gifting arrives as an addition.

  3. The channel is not always a website

    Counters, cards and printed batches carry gifts long before any page does.

  4. Teams and calendars are not alike

    One brand has ten developers, the next an agency, the third neither.

Two things we don’t claim There is no ready-made store extension yet. With API v3, nothing is pushed into your systems — your side asks, ours answers. Webhooks come with API v3.1 or 2.1.

05 — Where it shows

Three setups that look nothing alike.

Main case

A retailer who started with a link, and embedded it later

The first season ran on a link sent from their own emails: no page touched, no release booked. Once the numbers were in, it moved into the checkout.

A chain with no website in the flow

Codes printed ahead on the cards, handed out at the till. Nothing on their side calls anything.

A platform team that wanted the API

Their order system creates the gift, holds the reference and picks the moment.

Also: Franchises with one brand per region Three-month pilots Campaign pages that live six weeks

FAQ

The questions asked before anyone books a developer.

We don’t have a website. Can we still run this?

Yes, and it is a common case. We prepare a batch of codes — up to a hundred thousand — and hand you the print files. Nothing on your side calls us.

Do you have a Shopify or WooCommerce extension?

Not today. Store extensions are planned, but none exists yet. A custom checkout wires in through the API, and the hosted link needs no storefront work at all.

Can our agency or integrator do the work?

Yes. Nothing assumes an in-house team: the portal is open to read, and a key is scoped to one brand, so opening one programme opens no other.

How do we get access?

Keys are issued to approved teams — no open signup, no public sandbox.

Is there a mobile app SDK?

No native iOS or Android SDK. Inside an app, the journey runs in a web view or on our hosted page.

Can we change the journey after go-live?

Steps, wording, language and theme are read each time a journey starts, and differ per brand and per batch. Our team applies them; you ship nothing.

Will Livstick push events into our tools?

Not with API v3: your side reads back the state of a gift, or the messages recorded — which is also how consented contacts reach your CRM. API v3.1 adds signed webhooks: seven events, from a recorded message to its first view, sent to an endpoint you register.

Two developers look at an integration on a laptop

What are you plugging this into?

You already have a journey. We fit into it.

Talk to us about your setup

Online or in store, by your team or ours — which way in fits is a conversation, not a project.