Location-based Personalization
Personalize your content for visitors in different locations. Whether it's a simple city or country swap or a full multi-variant experience, we've got you covered.
This feature is available only on Max and Enterprise plans
When to use location personalization
Location-based personalization shines when you want to show different content based on where your visitor is. Common use cases include:
Store location pages that highlight the nearest location
Pages that adjust content for regional preferences
Pricing or messaging that changes by market
Any content that benefits from being location-aware
How to set up location-based personalization
We offer two approaches: Pick the one that fits, as the approach you take depends on how much of your project needs to change based on location.
Approach 1: Simple personalization (city and country only)
If you only need to surface a visitor's city or country in one part of your project, just prompt it in Maker, and you're done. It takes literally one step.
Here's what happens behind the scenes: our system detects where your visitor is and passes that city and country information to your project. You can surface it as text, use it in a headline, or reference it however you need.
How to do it:
Open your Maker project
In the prompt box, mention that you want to display the visitor's city and country
That's it. When you prompt, Makeer will set it up for you automatically
Publish the project and the embed code (starting with embed.maker.new) includes this location data by default, so it works on your site right away.
Example prompt:
Display the visitor's city and country in the footer
In the hero copy, replace {location} with the users current city
Approach 2: Advanced personalization (multiple variants by location)
If you need different versions of your page for different locations, you'll create variants first, then set up rules that show the right variant based on where the visitor is.
Think of it like this: You design one "default" project, then create variations of it for each location you want to target. Each variant can be completely custom. Then you tell our system which variant to show to visitors in each city.
Step 1: Create your base project and variants
Start with a version that works for one location (or a default). Then create variants for the other locations you want to support.
For example, if you're running a store locator for multiple cities, create the default variant and ask Maker, either via a prompt or using our Variants feature, to create the multiple variants.
Default variant: New York (default)
Variant 2: Los Angeles
Variant 3: London
Variant 4: Paris
Variant 5: Singapore
Each variant can have completely different content, headings, or layouts. It's up to you.
Step 2: Use Maker to set up rules
Once you have your variants, prompt Maker to create the rules that connect each variant to its location. You can prompt something like:
Maker creates the rules automatically based on your variants.
Step 3: Publish
Make sure to publish the page and use the embed code provided.
Use a Maker Skill
You can also use the Location variants Skill to create per-city variants so different content is shown to visitors based on their detected city. Use when you need completely different page experiences for different locations, like showing store info for local visitors or region-specific content.
Skill descriptions on the cards are previews only. The full instructions are written for Maker to read and apply, so you don't need to see the complete text to get the benefit.
How location detection works
Our system uses CDN-provided location data to figure out where your visitor is. Here's what that means in practice:
We detect the nearest major city to where a visitor is located
For someone in Manhattan, we'll recognize them as "New York" (the nearest major city)
For someone in a small town outside a major city, we fall back to the closest large city we can identify
We pass both city and country data to your project
A note on precision: Because this uses CDN data, it's accurate at the city level for major cities, not down to neighborhoods or specific addresses. If you need more granular control, you can also pass location data as a query parameter (like ?city=Manhattan), and that will override the auto-detected location.
Testing your location variants
When you create location variants, you'll want to test them from different locations. Here are a few ways:
Option 1: Use the Geo Simulator In the Variant Rules section, click Test in Geo Simulator next to the variant you want to test. Select a country, region, or city to preview the page as a visitor from that location.
This lets you verify that the correct variant is being served without using a VPN or changing the page URL.
Option 2: Use a VPN If you connect to a VPN in a different city, your location will appear to be in that city when you load the page.
Option 3: Use query parameters Add a query parameter to your URL to manually set the location for testing:
This overrides the auto-detected location, so you can test each variant without needing a VPN.
Option 4: Ask your team Have team members in different locations test the page from their actual locations. They'll see the variant appropriate for their city.
Limitations and things to know
CDN coverage: Our location detection works best for major cities. Small towns and rural areas might fall back to the nearest major city.
Radius coverage: There's a radius around major cities. For someone in Mountain View, we'll recognize them as 'San Francisco' (the nearest major city). This is by design, but if you want finer control, use query parameters.
One-time setup: Adding location support to your project is a one-time effort. Once it's live, it works.
Embed code requirements
If this is a new project, then the right embed code will be created. If this is an older project that you are working on, make sure you publish the project and verify that the embed code uses the new location-aware embed code. Look for code that starts with:
FAQs
Last updated
Was this helpful?