> For the complete documentation index, see [llms.txt](https://docs.maker.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maker.co/maker-pages/publish-and-measure/maker-optimize-for-personalization-and-ab-test.md).
# Maker Optimize for Personalization and A/B Test
## Maker Optimize for Personalization and A/B testing
Personalizing Experience
Creating an A/B Test
Debgging Experiment
Maker allows you to serve personalized content on the fly on the same URL and our out-of-the-box integration with Google Optimize lets you create informative A/B tests with multiple variants.
In order to personalize the user experience of a visitor based on their persona, begin by clicking on the Option button on the Enhance bar and selecting "Optimize." The Optimize Rule Builder modal will open. The user will be served the page based on the rules set here. If there are no matching rules found then the default story continues to display.
Note : Maker Optimize is available only to customers using Enhance. Maker may ask you to re-auth with Google Analytics first. If so, make sure you have the proper GA permissions before re-authorizing and proceeding. Also, this is a collection of all the experiences and rules set across the site with Maker and not the ones specific to the current page.
Once the modal opens, click on " Create Experience " on the top right corner of the screen. In order to set up the experience, add rules for the following:
* Page Targeting : What page are you optimizing or personalizing?
* Audience Targeting : What sub-set of users would you like to optimize for?
* Selecting the Maker Story : What content should be seen by the visitor?
1: Page Targeting - To save time, as the default option, we pre-fill the URL you started with; however, using the dropdown arrow, you can choose between URL, Host, Path Hash or, Query Param. Add the remaining page targeting information based on the options available. To be very specific, you can add additional rules and use them in an and/or combination. The rules can be re-ordered by dragging them up/down in position using the icon on the left side.
2: Audience Targeting - Proceed to add the information about the audience you are targeting. You can use the options provided here or based on rules you've pre-set in Google Optimize, such as an A/B test, AdWords, device, language, JS Variable, cookie, and location. We do recommend using Google Optimize when location targeting or aiming for returning users.
3: Story - Select the story from the story picker you wish to serve based on the rules set in steps 1 & 2.
Preview Link - This simulates what the story looks like on the page but does not indicate if the rule is set correctly. Please use the Maker Optimize debugger to check if the story is running with the rules set in place. Click here to download and install the Chrome extension.
Cookie Visitor - Cookies can be set for visitors based on either time or session duration. This way when they later organically visit the page, they are still served the personalized experience. In Google Analytics and many other tracking tools, the default session expires 30 minutes after the last interaction. This means that if a user leaves a page open and then comes back within half an hour, the two visits will be recorded as a single session in the session count. Once a cookie is set, we hard code that experience for the user unless the parameter is no longer present, the cookie expires or the experience is overridden with another rule. Since all cookies are time-stamped, a cookie buster rule can be set to override the previous cookie. You can also delete the experience or turn off the cookie.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.maker.co/maker-pages/publish-and-measure/maker-optimize-for-personalization-and-ab-test.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.