All Collections
Optimize your Shopping Campaigns
Shopping Management in Optmyzr
Refresh and Sync your Shopping/ PMax Campaigns with Merchant Center
Refresh and Sync your Shopping/ PMax Campaigns with Merchant Center
Rishabh Singh Jasrotia avatar
Written by Rishabh Singh Jasrotia
Updated over a week ago

On this page:


The Shopping Campaign Management tool also helps keep Google Ads Shopping and Performance Max campaigns in sync with the merchant feed. It can run on all ad groups in the campaign together, which makes it much more efficient to use when you have many ad groups.

Read more about the tool here.

Refresh Product Groups and Listing Groups

Choosing to refresh your campaigns/campaign groups using the tool will:

  • Update your already existing product groups and listing groups,

  • Create new ad groups and even entire campaigns in accordance with the structure and feed changes.

The tool will suggest removals for products that are no longer present in the feed and additions for those that have been recently added.

We suggest refreshing your campaigns every week, this can be done manually through this option or automatically by using Automatic Sync Schedules.

Automatic Sync Schedule

This option allows you to sync your shopping campaigns with feed changes automatically at the frequency of your choice.

The 'Automatic Sync Schedule' column will show you if a sync schedule has been set up for the shopping campaigns present in your account and when it's scheduled to run if no automation has been set up, or if the automation has been paused.

You can click on any of these options to make changes to the sync schedule. This will open the 'Edit Schedule' side tray where you'll first find details such as:

  • Automation Type (which will be Shopping Campaign Refresher,)

  • Account Name and ID,

  • Campaign Group Name and Data (number of campaigns and ad groups in it,)

  • Merchant Feed,

  • Target Country or Feed Label,

  • and the Campaigns' Structure (Attribute at which the Campaigns and Ad groups are being created, along with the full hierarchy.)

The Status toggle allows you to enable or pause the automation. You can then define the schedule below using the Frequency (daily, weekly, or monthly,) Days (day of the week or date of the month,) and Time Slot fields.

In addition to setting up the frequency, the 'Edit Schedule' side tray gives you the option to select which team members should receive 'Error Notifications' and which actions should the tool perform when updating your campaigns to match changes in the feed. These actions include:

  1. Add Product Groups or Listing Groups: this allows the system to create new entities whenever it detects that a new variation of the selected attribute has been added.

    For example, if you've selected to create Product Groups for every Item ID variation, the tool will create a new product group every time a new product is added to the feed, locating it in the corresponding campaign and ad group, based on the hierarchy.

  2. Remove Product Groups or Listing Groups: Opposite to the above, this allows the system to remove these entities if it detects that the product is no longer present in the feed.

  3. Create New Campaigns: this allows the system to create new campaigns whenever it detects that a new variation of the selected attribute has been added.

    For example, if you've selected to create Campaigns for every Brand variation, the tool will create a new one every time a new Brand is added to the feed. These campaigns will follow the hierarchy set up for the campaign group.

  4. Create a New Ad Group or Asset Group: this allows the system to create new entities whenever it detects that a new variation of the selected attribute has been added.

    For example, if you've selected to create Ad Groups for every Product Type 0 variation, the tool will create new Ad Groups for every new variation that is added afterward and you specify the budget these new campaigns should have.

  5. Pause New Campaigns: With this option enabled, any new campaigns that may be created after an automated sync will be in a paused state.

Did this answer your question?