Sponsor / Fundraising widget

Tag a trip with a sponsor, partner or fundraising target and the public tracker shows a small collapsible widget under the hero card. Useful for outdoor expeditions backed by a gear brand, charity walks crediting the cause, or commercial tours crediting their tour operator. The widget also appears on the countdown screen for trips that haven't started yet, so anyone who hits the share URL early sees who's behind it.

What viewers see

On the public trip page (app.whereistereza.com/o/{slug}/{hash}/{trip-id}) a small panel appears directly under the hero card:

Header row with the admin-defined title (e.g. Sponsor, Fundraising, Powered by) and a ▸ toggle.
Collapsed by default — viewers tap the header to expand.
After expanding: the description paragraph, then a single call-to-action button if a URL was provided.

The widget is hidden entirely when the trip has no sponsor configured — trips without partners don't render an empty section.

For trips that haven't started yet, the same content also shows inside the countdown overlay as a compact sponsor strip (label + description + button), under the timer.

Setup

Open the trip in the org admin (/o/{your-slug}/admin → Trips → click the trip).
Scroll to the Sponsor / Fundraising section between Visibility and Transport.
Fill in any combination of these four fields:
- Widget title — required for the widget to appear. Becomes the header label (e.g. Sponsor, Fundraising).
- Description — short paragraph shown after the visitor expands the widget.
- Button label — the CTA text (e.g. Visit Banana Labs).
- Button URL — destination of the button.
Click Save Changes. The widget shows on the public page immediately (no cache wait).

Leaving every field blank hides the widget. To remove it later, clear the fields and save.

After saving you'll see two confirmations in the admin without having to leave it:

A gold ★ <title> chip next to the trip name in the trip list.
A Sponsor row in the trip-edit summary bar, showing the title and the configured URL.

To preview the public look, click Visit trip page in the summary bar (or copy the share URL into an incognito window).

What it's stored as

Sponsor data lives in meta.json for the trip:

{
  "id": "camino-frances",
  "name": "Camino Francés",
  "sponsor": {
    "title": "Sponsor",
    "text": "This expedition is made possible by Banana Labs.",
    "button_label": "Visit Banana Labs",
    "button_url": "https://banana-labs.example"
  }
}

Field length limits (silently truncated to keep meta.json lean):

title — 60 chars
text — 600 chars
button_label — 40 chars
button_url — 500 chars

The same payload is exposed on the public trip API (GET /api/t/trips/{trip_id}/all) under the sponsor key, so any embed that pulls trip data also picks up sponsor info without a second request.

Tips

Keep the title punchy — it becomes the panel header in uppercase. Sponsor, Fundraising, Partners, Powered by all read well.
Skip the button entirely if you only want to credit a partner without driving clicks — fill in title + description, leave the URL blank.
Sponsor data is per-trip, not per-org. A second trip that needs the same partner has to be tagged manually — by design, so retroactively adding a sponsor doesn't quietly stamp it on unrelated archived trips.

Trip management — full trip editor walkthrough.
Email subscribers — sponsor info does not appear in the trip's email notifications today (planned).

Need help? Contact support · Where Is Tereza?

What viewers see

Setup

Verifying it before sharing

What it's stored as

Tips

Related