Buyer profiles via FeedPulse
Three buyer segments inferred from on-site behaviour and (consented) past activity. The homepage and lifecycle email shape themselves to the segment within a session.
Watch Trader serves two completely different buyer profiles — the £200 first-watch hunter and the £15k collector. The same homepage was being asked to do both jobs and doing neither well.
The hardest thing about a marketplace is that "the user" is at least three different people. We modelled each properly and let the system serve the one in front of it.
Three buyer segments inferred from on-site behaviour and (consented) past activity. The homepage and lifecycle email shape themselves to the segment within a session.
SendPulse fires segment-aware sequences. The collector gets the new-stock alert; the bargain hunter gets the weekly under-£500 round-up.
High-value listings push to specific marketplaces; lower-tier listings stay on-site only. Same FeedPulse rule engine, two different routes out.
A small set of custom plugins sit on top of vanilla WordPress + a managed-host setup. We don't use the WP UI for content the team didn't want to manage.
Long-running. Quietly making the marketplace work harder than it did before. Specific segment-level lift figures belong to Watch Trader.
The site has been live and segmented for two years. The lifecycle pipeline runs without intervention; new buyer signals get factored into the profile model on a weekly retrain.
One call. We'll dig into what you've got, where it's friction, and whether we're the right people to help. No deck, no pitch.