Attribution & analytics for destinations

Your marketing.
Their next adventure.
See the connection.

See what travelers explore on your official map, where they use it, and which plans become observed visits. Bring your board a story grounded in real activity.

Your campaignTheir planWander on the groundEvidence you can explain

Map analytics and movement studies today. Connected campaign attribution through a scoped, validated pilot.

Actual activity · Florida

Actual user journeys to
Sanibel & Captiva.

A worldwide view, then a closer look at the islands. Built from the locations people shared while using Sanibel & Captiva’s official map.

A 24-second view of real activity on Sanibel & Captiva’s official map: worldwide movement, earlier origins, journeys across the islands and location density. Lines connect recorded observations; origin curves show regional connections. The animation reveals historical records, rather than replaying continuous travel.

75,669
recorded location observations
1,383
reconstructable movement trails worldwide
688
trails touching the islands area
86
devices with an earlier remote origin match

December 22, 2023 – October 2, 2026. All qualifying trails in the available history are included. These are observations and device-based trails, not a count of visitors or campaign-attributed trips.

Explore density, journeys & origins
How to read these maps

Teal lines connect successive observations from the same device and platform, grouped to roughly 100 metres. They break at gaps over 30 minutes, session changes, conflicting positions or implausible jumps. Gold curves connect generalized origin regions to the islands; they are not the routes traveled or home locations.

Origins use the earliest recorded location at least 50 km away before that device’s first islands-area observation. Density cells contain at least three device IDs. Repeat events, known bots and known internal IDs are removed. Older records lack location-source and accuracy metadata: 700 of the 75,669 observations explicitly identify GPS. Reported accuracy over 100 metres is excluded. The islands area is a geographic bounding box, not a list of verified business visits.

The story behind the numbers

From “that looks good”
to “let’s go.”

Give every campaign a useful next step: a guide to save, an event map to explore, a weekend to plan. Then define the evidence needed to connect what happens next.

  1. 01

    They respond.

    A traveler opens your guide from a social post, follows an email link or scans a QR code in a visitor brochure.

    A recorded click or scan

    Give each campaign placement its own link. An impression or email open alone is not a verified response.

  2. 02

    They make a plan.

    They explore the map, open a place, save a trail or build an itinerary. Your content becomes something they can take along.

    Supported map & planning activity

    A connected pilot needs the permitted campaign context to reach the guide and its planning events.

  3. 03

    They take it along.

    They open Wander on their phone and continue exploring. Supported account or app handoffs can connect the next part of the journey.

    A verified continuation

    We test the supported paths. An app install alone does not prove a connection, and unmatched journeys stay unmatched.

  4. 04

    Then they’re here.

    With location permission, an observation near a mapped place can show where Wander was used on the ground.

    A qualifying later observation

    An attribution study checks timing, location quality and the place boundary. A linked visit does not establish an extra trip caused by a campaign.

This is the measurement path for a proposed connected pilot. Each connection must be implemented and validated before a campaign receives credit.

Real journeys · existing studies

A place on a map.
A phone there later.

These are verified, anonymized examples from destination studies. They connect map activity with a later location observation. They do not establish an advertising campaign’s impact.

Yosemite Mariposa County, California

A plan for tomorrow.

Night-before planningCurry Village the next day

Late one night, about 25 km from Yosemite Valley, someone planned the next day on Yosemite Mariposa County’s official map. By lunchtime the next day their phone was at Curry Village, steps from the coffee stop they had opened.

Read the destination story

Gettysburg, Pennsylvania

From the map to the market.

A chocolate-shop tapAt the shop the next morning

Late one night in central Pennsylvania, someone tapped the Gettysburg Chocolate Market on Destination Gettysburg’s official map. The next morning their phone was at the shop, about 140 km away.

Read the destination story

Glenwood Springs, Colorado

A trailhead chosen along the way.

A trailhead tapAt the trailhead that afternoon

Early one afternoon in Summit County, Colorado, someone tapped the Doc Holliday Trailhead on Visit Glenwood Springs’ official map. About three hours later their phone was at the trailhead, about 100 km on.

Read the destination story

Distances and times are rounded. A location observation does not prove a purchase, an overnight stay or a completed activity.

Useful at your next board meeting

Know what happened.
Explain what it means.

A dashboard helps you spot activity. A destination study turns the records into a clear account of what people discovered, where activity appeared, and what the evidence can support.

Explore the analytics dashboard
Your destination · measurement brief
01

Discovery & interest

Map use, searches and places opened. See which content helps people decide.

02

Movement & observed origins

Patterns in shared locations, local activity and earlier remote observations.

03

Supported tap-to-visit journeys

A place interaction followed by qualifying location evidence, when the same identity can be linked.

04

Coverage & next steps

The date range, definitions, exclusions and missing connections alongside every conclusion.

Report outline · tailored to the data available for your destination

Build the next connection

Start with one campaign.
Give it somewhere to go.

Campaign attribution · pilot planning

Bring your campaign, your destination content and your web or agency team. Together, we’ll scope the connections and the evidence your report needs.

Illustrated campaign example

Your next weekend.
Mapped out.

Save the guide. Find a trail.
Make it your trip.

Plan your trip in Wander Use a campaign-specific link or QR code in social, email, your website or print.
  1. 01

    Choose a useful next step.

    Send people to your official map, a themed guide or a trip plan. Match the destination to the promise in your campaign.

  2. 02

    Scope and test the connection.

    Agree the supported channels, permissions, handoffs and visit definition. Wander and your team implement and validate the complete path before launch.

  3. 03

    Report what the evidence supports.

    Separate campaign responses, planning activity, verified continuations and qualifying later visits. Keep gaps visible, and distinguish pre-arrival interest from activity after arrival.

Clear answers

What the data
can tell you.

What does the dashboard show today?

First-party, bot-filtered map analytics: map loads, places opened, searches and referral sources. Location coverage depends on the visitor’s permissions and the records available for that map. A tailored movement or attribution study is a service from our team.

Can we connect a campaign to a later visit?

That is the goal of a connected attribution pilot. We first scope the campaign links, permitted identity connections, supported app handoffs and visit rules, then implement and validate the reporting. It is not a self-serve integration you can switch on today. Historical movement alone cannot establish a campaign connection that was never recorded.

Does a journey prove our marketing caused a trip?

It shows a supported sequence of observed actions. Causal lift needs a separate study design, such as an appropriate comparison group. We do not turn a tap followed by a visit into a claim about incremental tourism or spending.

Are these all visitors to our destination?

No. Observations cover devices that shared location while using Wander. Visits with the app or map closed are not recorded. Devices are not individual people, a point is not a visit, and the same person can use more than one device.

How are journeys presented publicly?

These examples omit device identifiers, exact dates and precise origins. Story distances and times are rounded. Sanibel & Captiva’s density cells contain at least three device IDs; movement points are grouped to roughly 100 metres and earlier origins are shown at state or country level.

Bring your board
closer to the journey.

Let’s look at your destination, the questions you need to answer and the evidence we can build together.

Talk about analytics & attribution