A plan post goes to many locations at once. Merge fields let one text name each location, and variants let an AI plan send different versions of a post to different locations.
Use merge fields
Type a merge field in the post text, with its braces:
{location_name}: the location’s name, as on its Google profile.{city}: the city in the location’s address.
For example, Autumn drinks are here at {location_name} in {city} becomes a different text for each location. AI plans can use the same two fields in their drafts.
Merge fields work in Content Plan posts only: plan posts and posts scheduled with Schedule a post. In a post you publish straight away from Posts, braces stay as they are typed.
MX fills the fields when the post is sent to Approvals, and checks the result for every location. It stops and says why when:
- the text has other words in braces, such as
{phone}or{City}. MX can fill only{location_name}and{city}; - a location has no name or city in its profile;
- the filled-in text is over 1,500 characters for a location;
- a location’s name or city contains contact details.
Approvers see the text with its fields, and a preview of the text the first few locations receive. Once the post is sent, Outcome by location on the post shows the exact text each location got.
Split locations across variants
In an AI plan, Variants sets how many versions of each post MX writes. Each variant is its own post for a different share of the plan’s locations.
- MX shares the locations out evenly between the variants. With fewer locations than variants, it writes fewer variants.
- On the plan’s page, a slot lists its variants as Variant 1, Variant 2 and so on, each with its number of locations and status.
- Each variant goes through Approvals as its own post, and each counts toward your monthly AI plan posts.