Signing in to Personalization¶

Signing in to Personalization¶

To sign in to the Personalization interface and manage your campaigns and visitor information, visit the URL appropriate for your local Personalization Admin region:

• Americas: us-east-1.lift.acquia.com
• Europe, Middle East, and Africa: eu-central-1.lift.acquia.com
• Asia-Pacific and Japan: ap-southeast-2.lift.acquia.com

If you are a Personalization - Premium or Personalization Starter - Premium subscriber, the Personalization API reference websites are available at the following URLs:

• Americas: us-east-1-api.lift.acquia.com
• Europe, Middle East, and Africa: eu-central-1-api.lift.acquia.com
• Asia-Pacific and Japan: ap-southeast-2-api.lift.acquia.com

Information about your local Personalization Admin region is provided to you with your keys. Contact Acquia Support if you need help connecting to either website.

Personalization user sessions have a non-changeable timeout of 30 minutes.

Documentation resources by tab¶

Use the following pages to help you configure and use Personalization:

Other information in the interface¶

In the upper-right corner of the interface are the following items:

• Help displays a list of links. Click any link to navigate:
  • Help documents brings you to Personalization
  • View Support tickets goes to support.acquia.com
  • Submit a support ticket
  • The Search Help Documents text box, which searches Acquia’s product documentation and knowledge base.
• The Product picker (a grid of 9 squares) is a menu which opens the sign-in page for the selected product, in a new browser tab.
• Clicking the Profile icon displays a dialog box containing your user email address, and a Sign out link.
• When a new release note or status change is available, the In product announcement icon displays. Click the icon to display the release notes or to see any announcements. A small blue bar displays when no new information is available. Point to the bar to display the icon. Select the right arrow (>) to go to status.acquia.com. For more information, see Using in-product messaging.