Managing Listing Sync Priority with Force Sync

Understanding Force Sync

Force Sync is a manual tool within the CRM's Listings feature that allows you to prioritize and expedite business listing updates that may be delayed or stuck. Instead of waiting for the standard automated sync cycle, using Force Sync flags your location data for immediate processing by the listings engine. This tool is designed for urgent situations, such as updating holiday hours or correcting critical business information, where a standard sync timeline is too slow. It's important to understand that while Force Sync increases priority, the final publishing time is still subject to the individual directory's own review processes and systems.

Availability and Requirements

Force Sync is available for listings managed through specific third-party engines.

• For the Yext engine: You can trigger Force Sync for all connected publishers for a location (Entity-level) or for a single, specific publisher (Publisher-level).
• For the Uberall engine: Force Sync is available only at the Entity-level, applying to all connected publishers for the chosen location.

To use this feature, you must have an active Listings subscription with one of these engines connected. The specific business location (entity) you wish to sync must have all required profile information filled out, such as business name, address, and phone number. You will also need user permissions that allow you to manage listings.

When to Use Force Sync

Choosing the right scope for Force Sync helps manage updates efficiently.

Entity-Level Force Sync

Use this option when you need to push updates to all connected directories for a location. This is ideal after making broad changes like adjusting operating hours, updating business categories, or correcting the address. This option is supported for both Yext and Uberall engines.

Publisher-Level Force Sync (Yext Only)

If only one specific directory (like Bing or Apple Maps) is lagging behind while others are up-to-date, you can target just that publisher. This minimizes unnecessary data pushes and focuses the system's effort. This granular control is only available when using the Yext engine.

Limitations and Best Practices

Force Sync is a prioritization tool, not a guarantee of instant publishing. Be aware of the following:

• It cannot override publisher rules, policy issues (like a suspended Google Business Profile), or missing mandatory data.
• If a sync is already in progress or a publisher's system is under maintenance, your Force Sync request may be queued.
• Always ensure the location's profile data is complete and accurate before initiating a Force Sync, as incomplete information can block the update.

How to Initiate a Force Sync

1. Navigate to the Listings section of your CRM.
2. Select the specific business location (entity) that requires an expedited update.
3. Choose your sync scope:
   • For an Entity-level sync, look for the option to prioritize sync for all publishers.
   • For a Publisher-level sync (Yext only), find the option within the list of individual publishers for that location.
4. Click the button labeled Request Force Sync.
5. Review the confirmation details and click Confirm to submit the request.
6. A success notification will appear, confirming the request has been queued for processing.

Checking Status and Troubleshooting

After initiating a Force Sync, you can monitor its progress. Check the Entity History or Audit Logs for entries related to the Force Sync action. These logs will show timestamps and can help you correlate the request with any subsequent status changes from the publishers.

If the listing does not update as expected, consider the following steps:

• Double-check that all required fields for the location are filled out correctly.
• Verify there are no known policy issues with the publisher's listing, such as duplicates or suspensions.
• If you use the Listings Suggestions feature, ensure any pending suggestions are accepted or rejected to prevent conflicts.
• Review the entity history logs for any error messages that indicate the next step.