FAQ | Yext Hitchhikers Platform

How often does each connector refresh data?

Both connectors automatically run on a daily basis, between 2am and 4am Eastern Time.

Can I force a run of either connector?

As of now, you cannot force a run of the Restaurant Connector, or change the time at which it runs. You can force a run of the Menu Connector during the app installation flow. Navigate to Apps > Your Apps > Olo Menu Connector > Launch. Click Install on Yext and then Edit. No need to make any changes, just click Save. This will trigger a run.

I already have restaurants/menus in Yext. Will these be deleted or overwritten when I run the connector?

The menu connector does not delete any entities or overwrite any data. Therefore, if you run this connector with menu items already in Yext, you will have duplicate ECLs.

The restaurant connector works slightly differently. If your pre-existing restaurant entity IDs in Yext are the same as your vendor IDs in Olo, the connector will overwrite data for every field it brings in.

There are two ways to avoid this, depending on your use case: 1. Change the entity IDs in Yext to avoid automatic matching between Olo data and pre-existing Yext data, or 2. Unmap all of the fields in the final step of the Restaurant connector flow so that only the appropriate fields are overwriting/adding data. Go back to Step 3 for more information on the second option.

I only want to bring in a handful of fields from Olo. Can I do that?

Yes! If you are creating new entities, simply unmap all of the fields you don’t want to import in the final step of the connector flow. Navigate to Content > Connectors and click View on the Olo connector you wish to edit. Click Edit Configuration in the top right corner. Scroll down to the final step of the connector, labeled Map Data. Unmap all the fields except those which you wish to bring in. Save and run the connector.

If you are mapping specific fields from Olo to pre-existing entities in Yext, you will need to ensure that the entity IDs in Olo match your Yext entity IDs. If they do not, the connector won’t know where to edit the appropriate fields. This will likely require editing the entity IDs of the pre-existing entities via manual edit / data upload with Excel, however, you will only have to do it once. Once the entity ID in the connector matches the pre-existing entity in Yext, unmap all fields in the final step of the Olo connector except the entity ID and fields you wish to import. Save and run the connector.

I can see that some of the entities failed. Why? And what should I do about it?

Navigate to Content > Connectors > View Connector. Click Download Results next to the most recent connector run on the activity log. Look at the Excel file titled Entity Diagnostics, which should give you some insight into why certain items did not come through. Often, it is because data (such as phone numbers, addresses, etc.) are not entered correctly on the Olo side.

Currently, no.

Check with your Olo CSM that they have granted this new location access to the Yext Partner Portal. This process must be completed for every new restaurant within your brand.

I’ve successfully downloaded the app, but the connector is bringing in no entities.

This is usually caused by one of two problems:

The wrong Olo Internal Name (also called Brand ID) has been input in the app installation flow. It should be an all-lowercase name with no punctuation or spaces. Confirm with your Olo CSM that you have the correct internal name.
The app cannot find a match between your Olo restaurants and your Yext entities. Remember that the Menu Connector matches based on Olo’s external reference ID, while the Restaurant Connector matches based on vendor ID.

Menu items that are marked as 86’d (temporarily unavailable) in Olo will be pulled into Yext. We recommend reviewing your 86’d menu items in Olo to ensure that any menu items you do not want displayed on publishers don’t get pulled in to Yext.

<% elem.innerText %>