Deployment cookbook
Eight ways to get a campaign in front of people, each as a short recipe: what it is, how to set it up, and when to reach for it. Several of them deliver your campaign’s Squid — a Squid is your campaign’s living, conversational ad — it greets, talks, and adapts.
1. Website embed
Section titled “1. Website embed”Put your campaign on any website you control with one script tag.
-
Publish the campaign you want to show.
-
Add the embed script to your page:
<script src="https://app.sparkletree.io/api/embed/v1/script.js?org=your-org"></script> -
Load the page. The Squid renders in place, served from the edge, always showing the variant that’s currently winning under Adaptive CVG.
Note: The old
/embed/[id]route is deprecated. If you have an embed from before, replace it with the script tag above. If you can’t run scripts on a page, a raw iframe to your hosted campaign page works as a fallback.
When to use it: you already have a website with traffic and want campaigns living inside it, updating themselves without redeploys.
2. Landing pages
Section titled “2. Landing pages”Every published campaign gets a hosted landing page at a /lp/ URL — no build step, nothing to host.
-
Publish the campaign.
-
Grab its landing page URL:
/lp/your-org-slug/your-campaign-slug(subdomain variants of the URL work too). -
Append UTM parameters for source tracking, exactly as you would on any link.
-
For ad A/B tests, use the variant override parameters to pin a specific variant to a specific ad — each ad links to its own variant instead of letting Adaptive CVG choose.
When to use it: paid traffic and link-in-bio situations. It’s the natural destination for ads, and the override parameters make clean A/B splits trivial.
3. Brand page and campaign pages
Section titled “3. Brand page and campaign pages”Your brand page — the public home for your brand at yourname.sparkletree.io or your own domain — carries your campaigns automatically.
-
Set up your brand in Dashboard → Brand (the Brandbook and Publishing tabs) and click Publish to publish.
-
Publish a campaign. It appears on your brand page and gets its own campaign page — no extra steps.
-
Visitors can also talk to the built-in
/askconcierge, which answers questions about your brand and campaigns — and answers AI agents as readily as humans.
When to use it: always — it’s on by default once your brand is published. It’s your durable home on the web; the other recipes mostly drive people toward it.
4. QR codes
Section titled “4. QR codes”Bridge the physical world to your pages with tracked QR codes.
-
Open Dashboard → Brand → Publishing.
-
Download your QR code from the Share your page card.
-
Print it — packaging, posters, table tents, wherever your audience stands.
-
This QR points to your brand page — scans land visitors there, not on a specific campaign or variant. Campaign and surface QR codes work differently: those scans are tracked as clicks and tagged with the campaign, surface, and variant, and the visitor is redirected to that page.
Scans can also hand off a conversation: someone mid-conversation with your Squid on a screen can scan and continue that same conversation on their phone.
When to use it: any physical touchpoint — retail, events, print — where you want measurable traffic instead of hoping people type a URL.
5. Physical screens and signage
Section titled “5. Physical screens and signage”Run campaigns on real-world screens, from a single shop display to a fleet.
-
Open Dashboard → Network.
-
Register each screen as a surface. Many types are supported: retail, vending, transit, stadium, kiosk, and more.
-
Optionally group surfaces into Zones — assign a campaign to a Zone and every surface in it updates together.
-
Assign campaigns to your surfaces or Zones.
-
Click Publish to push the content to SparkleTree’s global edge network, so screens load it fast wherever they are.
When to use it: you operate physical locations. Zones are the difference between updating fifty screens and updating one thing fifty times.
6. Android TV kiosk
Section titled “6. Android TV kiosk”For dedicated signage hardware, SparkleTree ships a native Android TV app.
-
Install the SparkleTree signage app on your Android TV device.
-
Pair the device with your workspace using the pairing flow in the dashboard.
-
Assign content as in recipe 5 — the paired device is a surface like any other, and updates arrive via SparkleTree’s global edge network when you click Publish.
When to use it: unattended screens that need to boot straight into your content and keep running — shop windows, lobbies, kiosk installations.
7. Meta ads
Section titled “7. Meta ads”Turn a campaign into paid distribution on Facebook and Instagram.
-
Connect Meta in Settings (admin-only) — see Connect your accounts.
-
Open the campaign’s detail page and deploy to Meta from there.
-
Manage it from SparkleTree afterward: status sync, pause and resume, and an admin-only emergency stop that pauses every Meta deployment in the workspace at once.
When to use it: you want reach beyond your own audience and are ready to put budget behind a campaign. Pair with recipe 2 — variant override URLs make each ad’s destination measurable on its own.
8. Shopify product pages
Section titled “8. Shopify product pages”Note: The Shopify integration is in beta with limited availability.
-
Install the SparkleTree app on your shop and connect it in Dashboard → Shopify.
-
In the Shopify theme editor, add the SparkleTree app block to your product template.
-
The winning variant renders on your product pages, and the web pixel attributes completed checkouts back to it.
Full guide: Shopify.
When to use it: you sell on Shopify and want campaigns working at the moment of purchase, with revenue attribution to close the loop.
Choosing a recipe
Section titled “Choosing a recipe”Start with what’s free and already yours: brand page (3), embed (1), landing pages (2). Add QR codes (4) the moment your campaign touches paper or a screen in the world. Screens (5, 6) suit operators with physical locations; Meta ads (7) buy reach; Shopify (8) closes the loop at checkout. They stack — most workspaces end up running several at once.