Promote in-app and in-game events, offers, and major updates with LiveOps

The features described on this page are currently only available to select Play partners.

You can use LiveOps to create real-time events, offers and updates that will be displayed on the Google Play Store. LiveOps help you to promote your app or game on Google Play and increase engagement, interactions, and purchases from your users.

Note: LiveOps is only available to a limited set of developers. If you are interested in participating, please contact your Google Play business development manager.

Understanding LiveOps

LiveOps are self-serve merchandising units on Google Play that feature fresh and timely content such as special offers, limited-time events, new content, and major updates to users. There are different kinds of LiveOps available, all of which help you to engage with your users outside of your app and drive users to open or reinstall your app, or partake in an offer such as a discount on an item, a store-wide sale, or a first-time special deal. In some cases, LiveOps are also shown to new users and will help incite their curiosity to download your title.

LiveOps appear across the Google Play Store. This includes the Apps or Games tab, the Events tab under the Games tab, search results, the store listing page, and in the case of offers in the special ‘Offers’ tab in select geographies. Most surfaces are available globally, except for the Events tab which is only available for games in Australia, Brazil, Canada, France, Germany, Hong Kong, India, Indonesia, Italy, Japan, Korea, Mexico, Russia, Taiwan, Turkey, UK, and the US.

Types of LiveOps

Read the following description before creating your LiveOps card and choose the correct LiveOps type. Selecting the correct LiveOps type is part of our content guidelines. Therefore LiveOps that are miscategorized will see limited reach and impact.

  • Offers: Discounts or $0 items that your users might be interested in. These can be digital goods administered through Google Play's billing system, fully $0 digital items administered through your own systems, or physical goods and services. If you’re running an event, such as a competition or holiday-themed take-over that includes high-value deals such as discounts or exclusive $0 items, you should select Offer as your LiveOps type.
    • Examples include give-aways for joining an event ("Claim a limited-time costume for playing this weekend"), item or store-wide percent or real-value discounts ("20% off your first order" or "$5 discount on all shoes"), value-adds and bundles ("50 gems for the price of 20," "5 lives included with any purchase," or "Starter pack bundle for $4.99, normally worth $20"). Offers can be time-limited up to 28 days, or run indefinitely if targeting specific types of users. Find more information on Offer type requirements here.
  • Events: Non-offer time-limited events happening in your app or game such as tournaments, challenges, live events, or co-operative/alliance events. 
    • Note: Events that offer a reward/discount should be submitted under Offers, not Events.
    • Events must be time-limited. Evergreen updates or new episodes/TV shows should go under Major update, not Events.
  • Major update: Significant updates with large new features or a large new content drop such as new season, new movie, etc. If the LiveOps is promoting a new in-app product (for example, a battle pass) you should enter it as a Major update unless it is only available for a limited time, in which case it should be an Event.
    • Note: Major updates have a display limit of one week.
    • The release of new in-app purchases (without a discount) should be submitted under Major update, not Offers.

Additional types of LiveOps for games 

  • Crossover: A crossover between games or IP collaboration event. If your cross-over offers a reward or discount, you should select Offer as your LiveOps type.
  • Pre-registration announcements: Updates for pre-registered users informing them of new content, instant app demos, milestone rewards progress, or global release announcements.

Create a LiveOps

LiveOps can be created at any time but must be submitted within 14 days of the event start date. It can take up to four days to approve your event; submit your event at least 4 days prior to the start date to ensure it goes live in time.

To create a LiveOps event:

  1. Go to the LiveOps page (Grow > Store presence > LiveOps).
  2. Click Create Event.
  3. Add the following information:
    • Event name: An internal event name that is only displayed in the Play Console
    • Event type: Choose an event type (see Types of LiveOps above)
    • Offer type: If your event is an offer, specify what type of offer it is. This allows Google Play to display offers correctly, helps our review team to quickly evaluate them, and enables users to see offers of similar types.
      • Note: It’s important to choose the offer type that matches what users will see and get in your app. The available types are:
        • Discount: Offers that give users a discount on one or more items, or for performing an action. For example, "10% off gems," "$5 off when you spend $25," or "15% off sale across the store."
        • Value add: Offers that give items away for free with other things, or increase overall value. For example, "Buy 1 get 1 free," "Get 60 coins for the price of 40," "Free muffin with a latte," or "Starter pack bundle for $4.99, normally worth $20."
        • Free reward: Offers that give users an item for free for performing an action. For example, "Race in this week's tournament and get 100 gems for free," "Free shipping for this week only," "Bonus item if you open the game today."
        • Subscription trial: Free or discounted trials for a subscription. For example, "50% off first 2 months."
        • Other: Any other type of offer that is not listed here.
    • Countries/regions: One or more countries/regions where this event will be displayed
    • Start date and time and End date and time: The start and end dates and times for your event, which can have a maximum duration of four weeks. Note the following:
      • Offers can be set to have no end time. This is useful for when you have a standard offer for a type of user, such as a new-starter offer. Selecting this will automatically set eligibility for your offer to new users only. We plan to introduce more eligibility criteria, such as buyer-state, time since last engagement, and churned users in the future.
      • Major updates and pre-registration announcements have a set duration of one week.
    • Preview event: Choose whether or not you want to show your event on Google Play before its start time, and specify a date and time. Note the following:
      • Preview event is selected by default. Make sure you change the selection if you do not want to show your event before the start date.
      • You cannot preview offers.
    • Priority: If you have multiple events for your app or game, this selection determines which event will be shown first. You can choose Normal (selected by default), High, or Very high. Note the following:
      • This selection does not impact how your event is shown in relation to other apps or games.
      • Important: You can submit one Very high priority event, offer, or major update per quarter. Very high priority events must be saved as a draft at least 30 days before the start date, and submitted within one week of the start date.
    • User eligibility: If your event is an offer, you can select which users are eligible to see it. This ensures that Google Play only suggests offers to users who can actually benefit from them, and limits the possibility of your users getting an offer that wasn't intended for them. For example, special offers for new users such as heavily discounted starter-packs, a discount on the first three meal delivery kits, or new trial subscriptions should only be seen by users who have not used your app or game before. Currently, you can select:
      • Everyone: For offers which are applicable to anyone in your selected countries or regions
      • New users: For offers that can only be redeemed by users who have never used or purchased in your app before
  4. Provide your event’s text and graphical assets:
    • Tagline (required): Make sure your tagline is descriptive and specific to your event. Don’t use a generic tagline that could be reused for other events or by other titles. If you're configuring an offer, include the items that are being discounted, and by how much. For example: "Holiday sale! 25% off when you spend over $50", "New course: try Prince’s Highway this weekend and unlock your exclusive legendary car", or "Buy any 4 books for the price of 3."
    • Description (required): Don't duplicate your tagline text in your event’s description; it will be shown alongside the tagline in Google Play. Make sure your description is relevant to the event. If you're configuring an offer, include any relevant limitations or conditions, such as eligibility, total number available, number per user, or how to claim. Description should be as expressive as possible so that even users who may not know your app or game would understand. Read the description requirements below.
    • Primary Image (required): Make sure your image is relevant to the event and helps users to visualize the event. Do not include any text on images (including brand logos, slogans, or app/game names) and do not include critical visual elements into cutoff zones. Read the image requirements below.
    • Square Image (required): Required to be shown in various Google Play surfaces and lists. Read the image requirements below.
    • Video (highly recommended): This must be a public YouTube video with monetization turned off. Read the video requirements below.
      A common reason for events and offers being rejected by our review team is that they have been entered in the wrong language. Make sure that you enter your tagline and description in the correct language(s).
      Note: The default language is EN-US.
  5. Recommended: You can also localize your event into different languages so you can reach users in different countries, similar to custom store listings. Select Manage translations > Manage your own translations and select the additional languages you’d like to provide for this event.
    • Note: Other languages will use the graphic assets you uploaded in step 6 by default. You can manually provide locale-specific assets by selecting a language and uploading the required graphic assets for each locale.
  6. Click Submit event to publish it on Google Play. You can click Save as draft to save your work without submitting to Google Play.
    • Important: You can’t edit your event after you submit it, so make sure you’re happy with your work.

View your events

The LiveOps page has several tables that provide an overview of all your events, so you can quickly see event statuses and key information such as countries, start/end date and priority level:

  • LiveOps events: Contains draft and published events
  • Rejected events table: Contains events that have been reviewed and rejected
    • If your event is rejected, you’ll receive a rejection notice and a reason for rejection in Play Console.
  • Previous events: Contains expired or canceled events

Copy an event

To make it easier to create similar events, you can copy information from previous events.

Prerequisite: Review the content quality guidelines to ensure that this event is sufficiently different to the original. You cannot have events that are identical or very similar to each other live at the same time.

To copy a LiveOps event:

  1. Go to the LiveOps page (Grow > Store presence > LiveOps).
  2. On the main page, click Copy to new event
  3. A copy of the event will be created. You can edit the details you want to change (these details are described in the Create an event section above).

Import events

You can bulk-upload events using a CSV template.

To import events:

  1. Go to the LiveOps page (Grow > Store presence > LiveOps).
  2. Click Import events.
  3. On the Import events page, click Download CSV template.
  4. Complete the template using the tips below.
  5. When you have the completed template, drop your .csv file in the upload box or click Upload event.

Tip: If you want to make edits, there’s an option to download drafts only. Click the Download events drop-down, select whether your event has images or not, and select Draft apps. You can then make your edits and re-upload the changes. When making changes using the CSV, remember to provide the event_ID.

Tips for completing the CSV template
  • event_ID: Leave this blank for new events
  • Event_type: Must be one of: OFFER, EVENT, MAJOR_UPDATE, CROSSOVER, or PRE_REG_UPDATE
  • Priority: Must be one of: NORMAL, HIGH, VERY_HIGH
  • submission_state: Must be one of: DRAFT, SUBMITTED
  • start_time_utc and end_time_utc: Times are in UTC and must follow the format YYYY-MM-DD HH:MM
  • default_language_code: Enter language code separated by ";"
  • countries: Enter country codes separated by ";"
  • taglines and long_description: Should use the format: language code=tagline and separated by ";" for each language. 
    • For example: en-US=testUS;en-GB=testGB
  • images/video_ids: Similar to taglines, you can target graphic assets by language. If you don’t have localized assets, just use the default_language_code and we will use that same asset for all other languages you are targeting. For example:
    • en-US=testus.jpg;en-GB=testgb.jpg
    • en-US=YeT0t1C_y20;en-GB=r-ERajkMXw0
  • user_eligibility: for offers, one of EVERYONE, NEW_USERS_ONLY (empty if event_type is something other than OFFER)
  • preview_opt_in: Is one of: OPT_IN, OPT_OUT
  • preview_time_utc: Follows the format: YYYY-MM-DD HH:MM 

Content guidelines: Requirements and recommendations

Read the following guidelines before creating your LiveOps. Submissions that fail to comply with the requirements and recommendations described below may not be shown to users.

Note: All LiveOps submissions should comply with content guidelines outlined in the sections below. Offer-type LiveOps should also comply with Offer eligibility guidelines.

General requirements
  • LiveOps events must be new and noteworthy user-facing updates, events, or offers within your app or game; LiveOps should not be submitted to promote general service description, evergreen, or routine events.
  • LiveOps events must be applicable to all users. If an event is only available to users who meet a minimum level requirement, you must clearly describe this requirement. The one exception to this rule is "new user" Offers, which can be targeted at new users using the eligibility criteria provided.
  • LiveOps events must run in-app at the same time as the LiveOps are scheduled. Failure to comply may result in a warning or in the removal of LiveOps in the Play Console for a 30-day period after which you can request to be re-enrolled in the program. You can edit or cancel LiveOps events in Play Console if necessary.
  • Users must readily find the submitted LiveOps information upon opening the app or game.
  • Your submission cannot contain inappropriate text, images or videos, such as third-party trademarked characters or logos used without proper permission.
  • LiveOps events must be consistent across tagline, description, image, and video. For example, if a tagline calls out "80% discount" but the description mentions "buy 2, get 1 free offer," then it will confuse users.
  • When submitting LiveOps, be mindful that LiveOps will be shown to users who may not be familiar with your app/game or the specific event.
  • LiveOps events should not reuse duplicate or very similar assets from other LiveOps. Each image, tagline, description, and video must be unique and specific to the LiveOps event. Do not reuse the same assets across multiple LiveOps, even if they were previously submitted for a different app or game. Minor changes within visual or text are also considered ineligible.
  • In order to provide a quality user experience, Google requires that all LiveOps events submissions meet high editorial standards. LiveOps need to be clear, professional in appearance, and lead users to content that is relevant, useful, and easy to interact with. The following restrictions apply:
    • Text that does not use commonly accepted spelling or grammar is not allowed.
    • Text that is incomprehensible or doesn't make sense is not allowed.
    • Images should not look overly stretched or distorted.
  • Do not submit more than one LiveOps for the same content. If a single LiveOps is targeting multiple regions, please localize your submission into different languages so you can reach users in different countries, similar to custom store listings. Select Manage translations > Manage your own translations and select the additional languages you’d like to provide for this event.
  • Enter a date more than 24 hours in the future. This is so that we can review your event, and make sure it is eligible for promotion across Google Play.
Overall requirements for text

The following requirements apply to all text elements of your LiveOps event (tagline, description, etc.). All text must comply with our store listing and promotion policies.


  • Submitted content should be in the correct language for the selected locale. Non-local languages are not allowed unless it's expected to be widely used and recognized in the region (for example, Using a simple English word such as 'Sale' on a ko-KR locale can be allowed.)
    Note: The Play Console may show a warning if we identify the incorrect language has been input. Please be sure to review and resolve these warnings if necessary before submission.

Special characters and punctuation

  • Do not use more than one exclamation mark (!) or question mark (?) sequentially
    • Example: You can’t use the following: ??, !!, ?!, !?!
  • Do not use any sequential special characters or punctuation
    • Example: You can’t use the following: <>, \\, :), ***, +_+, ((, !!, $%^, ~&~, ~~~, %%
  • You can use the ellipsis (...) as an exception to the previous requirement, but only when adhering to the following:
    • It’s not used in "Tagline" field
    • It’s followed by a space (so not 'x...y' but 'x… y')
    • It’s used a maximum of two times per LiveOps card
  • Use an Em dash (–), not a hyphen (-), double hyphen (--) or En dash (–)
  • Do not use line breaks in taglines
  • Use only standard characters in the spelling, grammar and idiom of your language (for example, don’t use the following: ¿, æ, Ø, ¡)
  • We encourage the use of percentage discounts in your tagline and description to communicate an offer (for example, 'X% off' or 'Up to X% off') and summarize the overall sale.
  • Do not use HTML tags


  • Avoid all capital letters unless needed for an acronym, coupon code, or brand name that is normally stylized in upper case.
  • Capitalize as standard for the language that you’re writing in,
  • Acronyms can be written in upper case or capital letters.
  • You can capitalize the first letter after a colon (:).
  • If the app name in the Google Play store listing is in upper case, you can use upper case or capital letters on the app name, too.
Overall recommendations for text
  • Write taglines and descriptions that all users can understand for that given locale.
    • Although your LiveOps will be shown primarily to users who may know about your title (that is, existing users who actively play/use or lapsed users who have played/used/installed your title), they can also be shown to users who are not knowledgeable about your title (that is, users who have never played/used your title or only played/used for short periods of time). 
  • Do not use duplicate messages across the tagline and description as these will be displayed alongside each other. Each element should add value to the LiveOps by providing context, flavor, or information.
  • Provide high-quality translated text in all elements for each country you are targeting.
    • LiveOps are only displayed to users that match the user countries and languages with localized descriptions you have provided. For example, if you target Japan, France and the United States but only provide English and Japanese descriptions, users in France will only see the event if their device language is set to Japanese or English. 
  • Do not request the user to press any button or otherwise assume the positioning of an element in the LiveOps itself. Examples:
    • "Press the button below to install!"
    • "Check out the screenshots above for more details"
  • Do not mention the word "LiveOps" in your text or image elements. This nomenclature is not understood by users. Use general terms or flavor text to describe your LiveOps.
  • Use of ‘Flavor Text’:
    • ‘Flavor text’ is defined as editorial flair meant for creative or entertaining user-value. It's essentially fluff but it can add context, enhance the tone, include extra background information or add narrative.
    • If it is beneficial for the user to understand the LiveOps, we encourage inclusion of additional context such as flavor text, theme, and setting or story in support of the required tagline.


  • Taglines should be concise (80-character limit), easy to understand, accurate, and only represent the value of the specific LiveOps being promoted. Provide clear event details such as event name, seasonal moment, etc.
  • Start the tagline by clearly mentioning the LiveOps details and do not include any generic promotional text, call-to-actions, or descriptive text that does not add value.
  • For offers, the tagline must clearly state the value of the offer.
    • Mention the value the user gets in the first 40 characters.
    • Values in taglines must reflect the specific offer that is redeemed or applied at checkout. 
    • Clearly state the value the user would receive (for example "X% off all starter packs" or "Up to X% off starter packs"). If stating currency amount, monetary discount must be reflected in the specified area’s currency symbol (for example: £10, €5, etc.).
    • Taglines must have specific offer value and/or discount, and cannot be generic promotional text (for example, "New gifts and rewards"). If the sale is offering a discount or reward on a specific SKU, it should state the name of the specific SKU and offer value and/or discount for the SKU.
    • The tagline must emphasize the limited-time nature of the offer within the app or game. Generally the best practice would be to also include an event name (for example, "Black Friday").
      • If a sale or branded event offers a discount or reward across multiple categories, the tagline does not need to include the specific percent discount but the branded event name is required in the tagline (for example, "Member’s Day- Savings on TVs and PCs").
      • If a sale or branded event offers a discount or reward for a single category of goods, then the discount or reward needs to be specified in the tagline (for example, "25% off TVs").
    • Clearly state any minimum thresholds/items needed for the offer. If a combination of products must be added to qualify for the promotion, the tagline should clearly state all items that must be added.
  • Offer taglines must be broadly applicable but any eligibility requirements (for example, offer applies for swimwear only) must be in the tagline.
  • Offer taglines should include billing expectations, additional charges, minimum purchase limits (for example, $5 off purchases over $20).
  • Make sure the tagline is specific and includes key element(s) of the LiveOps for your title.
    • Avoid a tagline that can be reused for any other LiveOps for your title or by any other title (for example, "Weekly event", "Holiday sale", and similar).
    • Do not reuse the same tagline across multiple LiveOps.


  • Maximum 500 characters.
  • Descriptions should provide a clear explanation of the LiveOps event and help users fully understand the details. Provide details such as event name, event mechanism & how to participate, why it matters to users, etc. Empty or not informative descriptions will be rejected.
  • Do not repeat duplicate messages across taglines and descriptions.
  • If the submitted offer is a branded event combining multiple offer elements, make sure that you don’t include any violating element (for example, sweepstakes, tournaments, and similar) as part of the branded event. The exception to this is adding an evergreen value that would enhance user benefit on top of the promoted Offer (for example, "Our free shipping is also applied for the discount").
    • Note: Mention of evergreen free shipping is allowed in the description only, because it enhances user benefit on top of the promoted Offer.
  • Do not use bullet points to summarize and opt for a short, sharp paragraph instead.
  • Provide details to help users clearly understand the LiveOps. We recommend at least 100 characters.
  • Do not include general descriptions about the app or game in your description.
  • Use line breaks if necessary to improve the legibility of your description.



Primary image:

  • JPG and 24-bit PNG supported
  • 1,920 px by 1,080 px, 16:9 aspect ratio
  • An image is required if you’re including a video

Square image:

  • JPG and 24-bit PNG supported
  • 1,080 x 1,080 px, 1:1 aspect ratio
  • Do not include text in images, including your brand logo, slogans, or event name. Images should consist of only critical visual elements. Your main message should be conveyed through the tagline. Exceptions: Text within third party logos to convey collaborations with other IPs and text that is part of a product (e.g. brand on a t-shirt) are allowed.
    • Rectangular image safe zone: 30% on the bottom, 10% on the sides, and 5% on the top.
  • If you are including a third-party logo, it must conform to safe zones or may be rejected.
  • Do not use the Google Play or other store badges or icons.
  • Do not include design elements that resemble product design elements (CTA button, toggle, or elements that resemble tap targets).
  • Critical visual elements (for example, brand logo, or main character) should be centered in the safe zone as your image may be cropped to fit on certain devices/form factors. Images with border frames are not allowed.
    • Rectangular image safe zone: 30% on the bottom, 10% on the sides.

      Example of safe zone

    • Square image: No safe zone needed.
  • Keep prominent visuals and the focal point towards the center of the safe zone.

    Example of focal point


Liveops visuals should make users feel excited about events at a glance and should compel them to click into the LiveOps event. LiveOps images will show alongside the title and should not be redundant, but complimentary. 

Text fields such as tagline and description should be used to describe and highlight the LiveOps in detail. Failure to comply with these quality guidelines may result in limited exposure of LiveOps on Google Play. Please keep in mind that your artwork will be viewed on many product surfaces, including small mobile screens. Therefore less is more when it comes to making your message clear and effective.

  • Make sure the image is specific to the LiveOps and help users visualize the LiveOps.
    • Avoid using the same image for different LiveOps.
    • Avoid using the same or similar image as detail page (store listing page).
    • Avoid using generic image that only describes the title but not the LiveOps. 
  • Make sure the image does not have round corners.
  • Image should have a single focal point. Busy images with no focal points may be rejected.
  • Avoid using pure white or dark gray as your color scheme as these colors can blend in with the Play Store background. Consider using more vibrant colors in your graphics to build interest and excitement.
  • Avoid any content that reflects or suggests Play Store performance, ranking, accolades or awards, or user testimonials.
  • Localize your image as appropriate for different markets.
  • Avoid using generic in-app or in-game screenshots.


  • You must disable ads for your video to be featured. To disable ads, you’ll need to:
    • Turn off monetization in your video, or
    • Upload a different video without monetization claims and update the URL in the Google Play Console.
      Important: If your video uses copyrighted content, turning off monetization for your video may not be enough to prevent ads. In that case you will need to use a different video (without copyrighted content that has monetization claims).
  • Set your video’s privacy setting to public or unlisted. Do not set it to private.
  • Make sure your video is embeddable.
  • Properly localize the video including UI visuals, text, and audio.
  • Make sure the video is specific to the LiveOps and helps users visualize the LiveOps:
    • Avoid using the same video for different LiveOps.
    • Avoid using the same or similar video/image as detail page (store listing page).
    • Avoid using generic video that only describes the title but not the LiveOps.
  • Video should set the right expectations and get the user excited about the actual LiveOps experience:
    • We understand that branding and storytelling can be important but we highly recommend minimizing these elements and focus instead on showing the actual LiveOps experience.
    • Use captured footage of the app or game itself. Do not include people interacting with the device (for example, fingers tapping on the device), unless the core LiveOps experience is off-device.
  • Create a video in landscape orientation rather than a portrait orientation, as your video will show in the landscape video player.
  • Keep your videos short and concise because only the first 30 seconds autoplay. Users can still continue watching the full video by tapping it.
  • Since videos may inline autoplay with the sound muted by default, consider using copy to give the user more context. However:
    • Do not include any content that reflects or suggests Play Store performance or ranking.
    • Make sure that the text is legible by using readable fonts, proper font size, and displaying the text long enough for the user to read it.

Offer eligibility guidelines

Many in-app and in-game offers are supported by Google, but there are some restrictions. Google has the right to reject submissions that fail to comply with the requirements and recommendations described below and has the right to not show submissions to users.

General requirements for in-app and in-game offers
  • Offers must add value. Offers must provide a monetary discount or an additional or incremental good or service not normally associated with the purchase.
    • Rewards and gifts must be of value.
    • Evergreen or generic ongoing offers are not allowed (with the exception of evergreen offers targeting to new users are allowed).
  • Offers must be eligible to a broad set of users (with the exception of evergreen offers targeting to new users are allowed).
  • Offers must be specific. Submissions must specify what (that is, at SKU or category-level) is offered, how much its value is, and how the promotion will run.
  • Offers must not be submitted to serve as an advertisement substitution listing multiple ongoing or evergreen promotional elements, or including general descriptions about the app or game.
  • Offer must be redeemable in your Android app.
  • Offer should not impose offer-specific costs upon redemption if costs don’t apply to non-offer purchases (for example, extra fees).
  • Users must readily find the offer upon opening the app or game.
  • Offer terms must also comply with any applicable local and national laws.
  • Branded events represent offers from developers which are based on a cultural holiday (for example, "Back to School" or "Black Friday"), or app milestones/events (such as an anniversary sale). Multiple allowable promotional elements under the same branded event may be included (for example, 30% discount and voucher with purchase).
    • Branded events must only be submitted when there's a highly recognized/very important seasonal moment or app milestone/event, as developing too many branded events diminishes the value of each event.
    • During a branded event, Offers can include mention of evergreen programs if there is a net new or incremental discount applied to the evergreen program during the event period. 
      • Note: Mention of evergreen free shipping is allowed but only within the description as an addition to a non-evergreen offer during the branded event.
    • If the offer contains allowable and unallowable elements (for example, it includes mention of daily deals, sweepstakes, or evergreen programs) the offer will be deemed ineligible. 
      • Example: If a retailer presents a Black Friday offer with a discount and free shipping (allowable offer types) but includes mention of ongoing routine daily deals program or a sweepstakes (both disallowed), the offer would be deemed ineligible.
Requirements for each offer type
  • Discount
    • Discounts must be a minimum of 10% and/or reflect an equivalent monetary value.
    • In case of a maximum discount (for example, 20% off everything with a maximum discount of $50) the maximum discount must be clearly stated.
    • Promo codes are permitted (for example, 15% off with code SUMMER21).
    • In case of tiers (for example, "20% off when you spend $100 or more, 30% off when you spend $200 or more"), the tiers must be clearly stated in the offer tagline or description.
    • Cash back offers must be reflected at cart or at checkout.
  • Value add
    • Bonus offers (for example, "Get four times the value on gems, or get 20% more coins for the same price") must provide a minimum of 10% value add.
    • In case of a free reward offer (for example, "Free character, free tote bag with $50 purchase"):
      • The reward must have value and be clearly communicated.
      • In-app loyalty points (must be for your own app) are allowed as a reward.
      • Purchase requirements for redemption of reward must be clearly stated.
      • For physical goods, free items can't be samples or trials.
      • For games, required action to redeem the reward must be for a limited time, should have a minimum reward guarantee for participating, and must be outside of the core game loop. Core game loop examples (not allowed): view an ad, complete a regular challenge/level.
    • For gift card rewards, the gift card value must be clearly stated and be from your own store.
  • Subscription trial
    • Minimum 10% discount for subscription introductory pricing.
Offer restrictions

To be eligible for promotion on Google Play, your offer should not:

  • Be restricted to a small subset of users (for example: only available to users in one city, military discounts, birthdays, teachers and students). New user-only offers are supported through the new user targeting option in the LiveOps form.
  • Be an "everyday low price" discount. For example, if a $5 item is always $1 off, that’s not a genuine discount — the true price is just $4.
  • Be only available in a limited quantity (for example, first 500 buyers only).
  • Be limited to items or services that are usually $0.
  • Involve a sweepstakes, tournament, or other contest.
    • Note: In-app/in-game tournaments and contests should be submitted as LiveOps Events, not Offers.
  • Require mail-in or email rebates.
  • Include tax/value added tax (VAT) discounts.
  • Be used to advertise an item without a discount.
  • Total less than 10% for discount and value-add offers.
  • Advertise an offer for a different app (for example, App A can’t submit a deal that promises 5% cash back on App B).
    • Note: In-app purchase offers for third-party apps are allowed if users can redeem the in-app purchase offer via Google Play's billing system and without leaving the app where the deal is advertised.
  • Be for a special interest rate, annual percentage rate (APR), or credit/debit cash-back product.
  • Be for paid apps or games (title-level discounts). Discounts for paid apps or games should be submitted via "Paid app sales" in Play Console. Learn more about creating sales for paid apps.
  • Be a "reward with action"-style offer in a game where the required action is part of the core game loop. Core game loop examples (not allowed): view an ad, complete a regular challenge/level.
  • Be submitted to promote routine programs or generic ongoing sales (for example daily flash sale mechanisms).
  • Be new content updates without discount or add value-add (for example, new characters, levels, maps, game locations should only be considered offers if they represent limited time promotional events). 
    • Examples of eligible offers include:
      • Update is $0 or discounted but will become an in-app purchase or reflect a  price increase after the limited time event concludes.
      • Update previously was offered at a higher price or was an in-app purchase item and is being offered at a 10% or more discount or is being offered for $0 for a limited time event.
    • Ineligible examples include:

      • New evergreen playable character—unless the new character will become an in-app purchase after a limited time.
      • Introduction of new character or package—unless the price of the new character or package is expected to increase (the sale price must reflect a 10% discount or more).
Offer submission examples

Expand the sections below to view some examples of offer submissions to get you started:

Example 1

Example 2

Measure your event's performance

You can use reports in Play Console to evaluate how your LiveOps events have performed with different types of users on Google Play. This data can help you to report on the impact of your events, learn what works well with your audience, and inform your future plans.

Learn more about evaluating your LiveOps events performance.

Track and fix submissions that do not meet content guidelines

The quality of the LiveOps content you submit is the most important factor in determining its reach and impact. Quality is determined by the overall value of content you submit (such as the taglines, descriptions, images, and videos).

Beginning July 2022, you can see LiveOps submissions that fail our content quality review process in Play Console.

Understand the content quality review process

Every time you submit LiveOps content, we review it in multiple languages to check whether it meets our content guidelines requirements and recommendations. This is to ensure that LiveOps cards are of high quality and deliver the best experience for your users. 

Events that don't meet the guidelines will only be shown on your store listing. Events that meet the guidelines are shown on your store listing and are also eligible to be shown across various Google Play surfaces, for example, in the Apps, Games, and Deals tabs.

This process typically takes less than 24 hours and should be complete in advance of your offer or event going live.

View and understand the outcome of content quality review

You can view the outcome of your submission's content quality review on the LiveOps page (Grow > Store presence > LiveOps). If your content does not meet our guidelines, you'll see a warning message (for example, ⚠️1 issue) next to it. 

If you have a content quality issue, you can click the question mark icon  or overflow menu (the three dots icon  ) to view:

  • The language(s) in which the event has failed a content quality review
  • The status of the event (this provides more information on its failure)

A submission typically fails a content quality review for one of the following reasons:

  • An image, the tagline, or the long description do not meet our content guidelines.
  • The tagline, long description, an image, and/or a video is/are either poorly localized or not localized at all.
  • The offer does not comply with offer eligibility guidelines.
  • The offer or event details are unclear and/or inconsistent.
  • The offer or event does not meet policy guidelines or mandatory requirements.
  • The developer selected the incorrect LiveOps type (for example, they chose the Offer type instead of Event, or vice versa).

Next steps

Review your submission against our content guidelines. If you make changes and want to re-submit, cancel the original submission, recreate it with the issues corrected, and re-submit in Play Console. Review our best practices and common mistakes before resubmitting.

If your offer or event fails a content quality review, you may also receive an email from the Google Play Support team with more information. If you have any questions, please contact our support channels in Play Console.

Was this helpful?
How can we improve it?

Need more help?

Sign in for additional support options to quickly solve your issue

Clear search
Close search
Google apps
Main menu
Search Help Center