Fenced Rates


Note: You are viewing an article about the Hotel Ads Center, which has been replaced by the Hotel Center as the primary feeds platform for Google Hotel Ads. Learn more about the new Hotel Center experience.

Fenced rates offer different rates for your itineraries, based on the end-user's device, domain, and signed-in status. Fenced rates offer benefits to users based on rate rules that you set up.

Create a rate rule

To create a rate rule, follow the steps below:

  1. Open the Hotel Center.
  2. Click the Tools tab.
  3. Select Prices > Fenced Rates in the left-hand navigation. The Fenced Rates tool displays.
  4. Enter a rule name in the "Create new rule" field and click Add. The rule name will appear in the "Find rule" field.
  5. Choose among the configuration options described below.
  6. Click the Save button.
  7. Request activation of your rule for it to become active.

For more information, see Fenced Rates.

Configuration settings

You may create one or more rules defining fenced rates by device type, country code, and signed-in status. To define a rule, use one or more of the configuration options described in the following table:

Option Description
Device type Specifies that the rate rule matches target mobile users, desktop and tablet users, or both.
NOTE: If neither option is selected, the rule will target both types of users.
Status Specifies that the rate rule matches users signed into their Google account, users signed out of Google, or both.
Country code Specifies that your rate rule matches users searching from one or more countries. Their location is determined based on IP address.

Rule activation

To request activation of a fenced rate rule, click the Active radio box under the " heading. The selection will gray out and an activation notification request will appear. Your Google account representative will contact you as soon as verification of your rule is complete.

Rule deactivation

To request deactivation of a fenced rate rule, click the Inactive radio box under the "Status" heading.

Was this helpful?
How can we improve it?

Need more help?

Sign in for additional support options to quickly solve your issue