Back to the journal

Facebook

A Facebook Story sticker expires. The Page website does not.

Use the sticker for a 24-hour drop, tagged so you can see it. Leave the Page’s Website field on a hub that still makes sense after midnight, including for people who only have Messenger.

September 26, 20265 minLinkForge Editorial

Facebook Stories borrowed the sticker habit from Instagram. Eligibility and labels move around; some accounts see a link sticker, some see a reduced set, and a personal profile is a worse place to run commerce than a Page. None of that changes the durable object: the Page’s Website field, which does not expire when the Story does.

Use the sticker for the thing that is only true today. Use the Page website for the thing that should still be true when someone screenshots your Page or opens it from Messenger next month. Both URLs should be the same hub, with different tags if you need to tell the traffic apart.

Two doors, one page

Sticker. It points at the hub with a query string that marks the surface: utm_source=facebook&utm_medium=fb_story&utm_campaign=saturday-drop. The sticker is allowed to be specific in the Story’s text (“the Saturday menu is the first button”) while the URL itself stays the hub. A sticker that points at a raw event URL, a raw checkout, or a PDF will be wrong tomorrow, and you cannot edit a Story after it expires. You can edit the hub.

Page website. About → Website → the clean hub, or the same path with a stable utm_medium=page if you want Page taps separated from Stories. People who never watch Stories still use this row. It is also what some shares and “website” previews cling to.

If those two disagree — sticker goes to this weekend’s festival tickets, Page website still goes to last year’s festival — you will sell the wrong date to the more careful visitor. The field-by-field setup is what to put in the Facebook Page website field. Read it once, then keep the Story honest.

When a sticker is the right tool

  • A dish, a flash sale, or a guest shift that ends tonight.
  • A livestream that is happening now, where the ticket or the replay will move.
  • A fundraiser day, if the donation URL is also ready on the hub for people who arrive late.

Say the expiry in the Story frame: “Order by 14:00.” The hub’s first button can say the same thing, and at 14:01 you change the button to “Kitchen closed — book for Sunday” without touching the Page’s website field. That edit is the whole point of a stable URL, spelled out in keep the same Instagram bio URL. Facebook is the same discipline with a different app.

When the sticker is the wrong tool

  • Anything you want a journalist, a parent, or a regular to find on Thursday.
  • A recruiting link, a menu PDF that changes weekly, or a booking page you hope will get saved.
  • A personal profile Story if the business is the Page. Personal profiles are messy: friends, old stickers, no clean commercial identity. Prefer the Page for anything you would put on a receipt.

If your account cannot add a link sticker, do not buy a workaround. Put the offer in on-screen text (“Website on the Page — first button is the menu”) and keep the Page field correct. The Instagram cousin of this limitation is adding a link to Stories. The lesson travels: stickers are a bonus, the profile URL is the business.

Set the pair up in one sitting

  1. Publish the hub with today’s offer as the first button and the evergreen action as the second. Create the page. A café might hero “Saturday lunch menu” and keep “Book a table” directly underneath. Five free links are enough for menu, booking, map, reviews, and one special. Pro at 7€/month adds the custom domain and SSL if the sticker URL should show your name.
  2. Paste the hub into the Page website field. Open the Page as a non-admin and tap it.
  3. Build the tagged URL for the Story. Test it: the page must ignore unknown parameters and still load. If a site builder 404s on query strings, fix that before you sticker it. LinkForge pages are meant to keep working with campaign parameters.
  4. Publish the Story with the sticker and with words on the image. Do not rely on the sticker alone; people miss it.
  5. The next morning, open analytics. Story traffic and Page traffic should be separable by utm_medium if you tagged them. On-page clicks tell you whether they hit the special or the evergreen button. The parameter guide is UTMs on bio links, and it applies to Facebook even though the examples say Instagram.

People forward Page posts into Messenger. The preview they see is whatever the hub’s title and description say, not the Story’s joke. Write the title so a forward still makes sense: “Hale Café — menu, booking, Saturday specials,” not “Links :)”. If Open Graph is thin, the forward looks like spam and the careful relative does not tap.

Also assume the sticker visitor is in Facebook’s browser. Heavy popups and autoplay will stall. If the hub is thin HTML and the menu button goes to a heavy PDF, say so in the label (“PDF menu, 2 pages”) so the wait is expected. Performance habits from Instagram’s in-app browser are the same WebView family.

After the Story dies

Do not leave a first button that says “Saturday” on Monday. Change the label. Leave the Page website alone. If you run a weekly special, the rotation is the button text and the Now line, not a new domain. Archive the Story’s campaign name in a note so next month’s UTM does not reuse a name you still want to compare.

If a sticker URL was a one-off checkout and people are still asking for it in comments, reply with the hub and the current button name. Do not republish the dead checkout to be nice. A closed cart with their card details half-filled is worse than a clear “sold out.”

The sticker is a flare. The Page website is the address painted on the door. Point the flare at the address, tag it so you can see the flare worked, and update the offer on the page when the day is over.

Create my page — Pro is 7€/month (~$7)

Free to start. Pro is 7€/month (~$7 depending on exchange) for a custom domain and full SEO controls.