Embedded Field Support for 3rd Party Posts (Spring ‘22 Release)

In the Spring ‘22 release, we now support embedded fields from Knowledge Graph in the body of Facebook and Google Local Posts. Embedded fields are useful for posting to several entities at once, because fields like phone numbers and addresses are different for each entity. Embedding fields allows you to post the same message to each location, with dynamic values for those entity-specific fields.

To add embedded fields to Google Local Posts:

  1. Click Listings in the navigation bar and click Post.
  2. Click on the + Add Post button.
  3. Click on the desired publisher icon.
  4. To add an embedded field, click on the plus sign and select your desired embedded field from the drop-down menu.
  5. Click Post Now to publish your post, or click on the drop-down button next to Post Now to schedule the post for a future date and time. For more information, see Create a Social Post.

To learn more about Embedded Fields, visit the Embedded Fields Overview training unit.

Turn on the Spring ‘22: Posting UI Updates (early access) account feature to use this feature during the Early Access period.

Do we use this function for both Facebook and Google Business profile?

Background is
When I choose just FB, I can see + button, but when I choose Google, it disappeared.

Hi Tsuyoshi -

This feature is available for both Google and Facebook!

Can you confirm that the account feature is turned on in your account? You can do this by navigating to Account Settings > Account Features Screen and setting Spring ‘22: Posting UI Updates (early access) to On.

Hi Micaela,

Yes, I already did it, but as attached, when I select Google, + button disappears.
Is it still under development?



2022年4月22日(金) 0:56 Micaela Luders via Hitchhikers <turtlehead@discoursemail.com>:

Hi Tsuyoshi,

I opened up the account and retry turning on the feature in account settings and I am now seeing the UI update!

Oh it works! Thank you so much.


2022年4月22日(金) 13:24 Micaela Luders via Hitchhikers <turtlehead@discoursemail.com>: