A dating app that meets people where they came from.
A podcast listener, a visitor from the 50+ campaign, an active member still on the free plan, and a member who has not been back in two months. Onboarding, events, the upgrade pitch and the top bar change for each — built from campaign links, the member database, visit history and city. Switch the visitor below to see all four.
Dating without the endless swipe
On episode 112 the hosts talked about slowing down: fewer matches, longer conversations, and meeting at real events. That is how Kindred works — here is where to start.
I heard the episode on a Sunday walk and signed up that night. The questions on my profile were the ones they talked about.Kindred member — Portland, OR
Every way in gets its own front door.
Tag every way in
Podcast links, partner campaigns and ads carry UTM parameters, and a landing page is a signal of its own. Each becomes an audience the moment the visitor arrives — before anyone signs up.
Sync what the member database knows
Plan and membership status come from your member database or CRM. Visit counts, last visit and the pages each member uses are recorded by Personyze itself.
Feed it your events
Events are a feed like any catalog: city, date, tags and seats left. Recommendations filter it per visitor — 50+ events for one audience, this weekend in their own city for another.
How Personyze personalizes a dating and community app.
The show notes set the story
The podcast link carries utm_source and utm_campaign, so the listener lands on onboarding written around what the episode discussed, with the show’s code already in the sign-up box. Every other visitor sees the standard sign-up.
Age is never guessed
The later-life audience is built from the campaign they clicked and the page they landed on, and it stays with them on the homepage. The events shown are the ones tagged 50+, and the safety tips are pinned where they cannot be missed.
The upgrade pitch follows what they use
The free plan comes from the member database; the visit count and the pages used come from Personyze. A member who keeps opening Events is shown the Premium features for events, not a generic upgrade banner.
A lapsed member gets their city, not a discount
Sixty days since the last visit and a city from the IP address are enough to open with this weekend’s events near them. The way back in is something to do on Saturday, not a price cut.
Events are recommended like content
The events feed is filtered per visitor — by the 50+ tag, by city and by date — and sorted soonest first, so every row on the page is current.
The top bar is its own campaign
The podcast code, the Later Life strip, the early-RSVP line and the welcome-back count are four banner variations for four audiences, each changed and measured without touching the page underneath.
Questions about this example
How does Personyze target a 50+ audience without knowing anyone's age?
The audience is built from what the visitor did, not from a guess: the campaign parameter on the ad they clicked and the landing page it sent them to. Personyze keeps them in that audience on later pages, so the homepage can show the later-life section, 50+ events and safety tips.
Can the upgrade offer depend on how a free member uses the app?
Yes. The plan comes from your member database or CRM, and Personyze records visit counts and the pages each member uses. Combining the two, a free member who mostly opens Events can see the Premium features for events, while one who mostly messages sees a different version.
How are local events chosen for a returning member?
Events are loaded as a feed, like a catalog. For a member whose last visit was more than 60 days ago, recommendations filter that feed to the city from their IP address and to the next few days, sorted soonest first.
Give every member their own front door.
Welcome the listener, the later-life dater, the loyal free member and the one who drifted away — each with the page that fits, on the site and app you already run.