Changelog

Gift card emails and texts now go out in the language set for the purchase. The platform translates its own wording, so you do not write anything twice.

What changed

• Every gift card message: the purchase confirmation, the email to the person receiving the card and the SMS notice all follow the chosen locale.
• Previews you can trust: when you send a gift card, the preview shows the translated wording for each delivery method before anything goes out.
• Email previews with sample or real data: both show the translated text, so you can check a message without issuing a test card.

Good to know

• There is nothing to switch on. The locale decides the language.

A new WhatsApp marketing template shows a countdown clock inside the chat, with your discount code right under it. You pick the end time each time you send, so one approved template covers every promotion.

Customers see the time left on an offer tick down in the message itself. WhatsApp draws the clock, so you never rebuild an image to change a date.

What changed

• A limited time offer template type: create it under Marketing, with a heading for the offer, an image header and a body that can hold variables. The builder previews it on a phone as you type.
• A clock that counts down: WhatsApp renders the timer in the chat, and it turns red in the last hour before the offer ends.
• Copy code and URL buttons: one tap copies the code, another opens your offer page. Meta requires both buttons on this template type, so they always appear.
• Expiry chosen when you send: the template holds the layout and you set the deadline at send time. No new template, and no new Meta review, for each campaign.
• Works wherever you send WhatsApp: conversations, bulk actions, workflows and calendar messages. Ask the AI template writer and it drafts the heading, expiry, code and image.

Ideas for using it

• Fill empty appointment slots with a code that runs out at midday.
• Bring buyers back to an abandoned cart with a discount that visibly runs out.
• Close a sign-up offer before the end of the month.

How to set it up

1. Open Settings → WhatsApp → Templates → Create template.
2. Choose Marketing as the category and Limited time offer as the type.
3. Add the heading, image, body, code and URL.
4. Submit it for Meta approval.
5. Pick the expiry each time you send.

Check the date before a bulk send. If the expiry is already in the past, Meta still delivers the message and the customer sees an offer that has ended.

WhatsApp templates are now created and edited in a new builder with a phone preview beside it. Media headers can also point at a contact field, so each person gets their own image, video or document from the same template.

One approved template can now carry a different invoice, ticket or image for every contact, instead of one template, and one Meta review, per file.

What changed

• One builder for everything: category, type, name, body, media, buttons and variables sit on one screen. The AI template writer and the WhatsApp template option in Reputation open the same builder.
• A phone preview while you type: it updates with every edit to the header, body, media and buttons, so layout problems show up before you submit for approval.
• Dynamic media URLs: a media header can use a custom field or another dynamic value instead of one fixed link. The value is filled in for each contact when the message is sent.
• Available wherever templates go out: workflows, conversations, bulk actions, calendar appointments, review requests and missed call text back.
• Clear failures: if the value for a contact is empty or is not a valid public link, that message fails with a clear error instead of sending the wrong file.

Where to find it

• Templates: Settings → WhatsApp → Templates → Create or Edit
• Review requests: Reputation → Settings → WhatsApp Requests → Open WhatsApp Template Builder
• Missed call text back: Settings → Phone System → Voice → Voicemail & Missed Call TextBack → Missed Call Text Back → Customize

Sending a different file to each contact

1. Save a public HTTPS link to each contact's file in a custom field.
2. In the template's media header, select that custom field instead of pasting a link.
3. Send from a workflow, a bulk action or a conversation.

Personalised images work the same way. Use an image service that draws a picture from a URL carrying the contact's name, and put that URL in the media header. Each contact in a bulk send then gets an image with their own name on it.

The link has to be public, because Meta downloads the file. Links behind a login, private cloud storage links and empty fields fail.

Checkouts built in AI Studio, the platform's state-of-the-art vibe coder, now let you decide which fields buyers fill in, save the contact before the payment and show the order once it is paid. You change each one by asking in the AI Studio chat.

Pick the checkout fields

The phone number and each part of the billing address (street, city, state, ZIP, country) can be shown, hidden or required. Name and email are always asked for.

Ask for example: "Require the phone number and remove the billing address."

Two-step checkout

Step one saves the buyer as a contact in your CRM. Step two takes the payment. Anyone who stops before paying is still a lead you can follow up, the same idea as a two-step order form in a funnel.

Ask for example: "Switch to a two-step checkout."

Check your workflows: a lead saved in step one starts workflows on the Contact Created trigger. Order Form Submission does not fire for it.

The order after payment

The confirmation screen lists the order ID, the items, tax and the total paid, plus, for a subscription, the next charge. You can also send buyers to your own thank-you page, which shows their actual order.

Ask for example: "After payment, send buyers to my thank-you page."

Availability

AI Studio projects that already take payments get these options on their next prompt, with nothing to reconnect.

Connect GitHub to an AI Studio project and the code stays in step in both directions. AI Studio sets up a private repository, sends each saved version to it and brings back commits made anywhere else, so you can also work on the code in your own editor or coding agent.

What changed

• Connect an account: in the project, open More → Git and connect a personal GitHub account or an organisation. You choose whether the connection is shared with your team or kept to yourself.
• The repository is set up for you: a private repository named after the project, with the first push done. Reconnecting later reuses that repository and never force-pushes.
• Sync both ways: saved versions (prompts, code edits, visual edits and restores) go to GitHub, and new commits on the connected branch come back on their own. Either direction can be switched off, and Push now and Pull now are always there.
• Your branch: a project starts on main. Switch whenever you like, or name a new branch that is created on the next push.
• A preview after each pull: AI Studio builds it in the background and shows Update preview when it is ready, so the page does not reload while you work. A failed build offers Retry build and Try to fix.
• When both sides changed: choose Force push to keep the AI Studio version, or New branch to keep both.
• Sync history: total syncs, success rate, pushes against pulls and each commit, linked to GitHub. Errors are explained in plain words.
• Secret scanning: a push is blocked when it contains keys such as AWS, GitHub, Stripe or OpenAI keys, or private keys. Images, fonts and other binary files survive every sync.

A new permission: manage Git and download code

This AI Studio permission covers Git and code downloads. Every role has it at the start, so no one loses access. To take it away from a user, go to Settings → Team → Permissions → AI Studio. Without it, the Git tab and the download options are hidden, and the user can still build, edit and preview.

Good to know

• Supported for React (Vite) and TanStack Start projects.
• Commits from AI Studio carry the author name "levelpartner AI Studio" rather than your GitHub identity.
• Only the connected branch syncs.
• Projects without a GitHub connection work as before.

Type "add a live chat" in AI Studio and a chat widget appears in your app, styled like the rest of your site instead of a stock bubble. It runs on the platform's own chat widget: the conversations, contacts and settings are the ones already in your account.

What changed

• Created from the chat: AI Studio offers a card to create Live Chat, or Email Chat, where a visitor leaves a message and you reply by email. The widget is named after your project and connected to the app.
• A few design questions first: before building a new chat, AI Studio checks the greeting, where it sits on the page and its tone with you.
• Part of your app's code: the widget uses your colours, fonts and layout. Change it by asking AI Studio or by editing the code. One project can hold several widgets, for example a daytime live chat and a separate after-hours chat.
• The same protection as the standard widget: secure visitor sessions kept out of your app's code, a captcha when a visitor looks like a bot, rate limits and your spam settings.
• What a chat needs: file attachments within the widget's limits, history for returning visitors, sending, sent and failed states with retry, and your business hours, offline message, inactivity timeout, ratings and end-of-chat message.
• One inbox: every message arrives in Conversations, as with the standard widget.

Chat widget analytics

In the project, More → Analytics → Chat Widgets shows chat loads, opens, open rate, ratings and satisfaction, plus a table of every lead with contact details, chat type, the page the chat began on and the widget it came from.

Filter by widget and date, pick the columns you want and download the leads you select.

Managing a widget in AI Studio

More → Chat Widgets lists the project's widgets.

Open one to rename it and edit the welcome and acknowledgement messages, the contact form, compliance notices and consent, spam handling and live chat business hours. Suspicious leads are tagged and held for review, with optional DND for SMS, email or both. With no widget yet, Add a chat widget asks AI Studio to make one.

Availability

• Live Chat and Email Chat work in TanStack Start and React projects.
• Voice, WhatsApp, Facebook Messenger and Instagram widgets are not available in AI Studio yet.

A new workflow action, Add Internal Comment, posts a note inside a conversation when the workflow reaches it. The contact never sees it. @mention teammates in the comment to bring them in.

Use it to put context where your team already looks. Say a high-priority lead joins a workflow: leave the assigned owner a note with the next steps. The note sits in the conversation history next to the messages.

How to add it

1. Open Automation → Workflows.
2. Create a workflow or open one you already have.
3. Add the Internal Comment action.
4. Write the comment and @mention anyone who needs it.
5. Save and publish.

A schema dashboard now sits in a new SEO & AEO tab on every website and funnel. Check and fix the structured data for all of its pages there, without opening the builder page by page.

What you can do there

• See the overall state: a Schema coverage card grades the site Needs work, Getting there, Good or Excellent and counts the pages that are Up to date, Might be outdated or have No schema.
• Scan every page: each row lists its schema types, when they were last updated and one of five statuses: Unsaved, Unpublished, No schema, Might be outdated or Up to date.
• Generate with AI: select one page or many and click Generate schema. Progress is live, and you review the results before anything is published.
• Edit by hand: use + Add schema on a page without any, or click a schema tag to open the editor.
• Publish when ready: nothing goes live until you click Save and publish. Until then the schema shows as Unsaved, and Discard drops it.
• Find what needs work: look a page up by its name or path, or narrow the list to one status. A page edited and republished two or more times since its schema was made is marked Might be outdated.

Why it is worth a look

Current, accurate schema is what makes a page eligible for rich results in Google, and it helps AI answer engines describe and cite your business. When the only way to fix it was one page at a time, it rarely stayed current.

Good to know

• Nothing to migrate: schema you already have shows in the new tab.
• The schema editor in the page builder still works, and the two stay in sync.
• Running Generate schema overwrites any schema a page already had, so review it before publishing.

Steps

1. Open Sites → Websites or Funnels, choose one and open SEO & AEO.
2. Check the coverage card and filter for No schema or Might be outdated.
3. Generate schema for the pages you select, or add and edit it by hand.
4. Review the result, then click Save and publish.

InitiateCheckout now fires when a buyer starts checking out instead of when they pay, and AddPaymentInfo now sends the order and customer details to Meta. Your reports show how many buyers leave between checkout and payment, and Meta gets better signals for your ads.

It applies to funnels, websites and stores with the Meta Pixel set up and the InitiateCheckout event switched on.

When InitiateCheckout fires now

• As soon as a store checkout page loads, and as soon as any page with the event set at page level loads.
• Everywhere else, the first time the buyer clicks, taps or types in an order form: one-step, two-step, popup and the new order form.
• At most once per page visit, however many order forms or triggers the page has. Autofill, password managers and fields focused on load do not count.
• For buyers returning through an abandoned cart link, after their saved cart loads, so the event carries the cart value and products.
• For buyers who go straight to Apple Pay or a similar wallet, when the payment starts.

Set at funnel, website or webinar level, the event waits for the first interaction with the order form. Set at page level, it fires as the page loads.

What AddPaymentInfo sends now

Order value, currency and product IDs, plus the customer's email, phone, name and external ID in hashed form, whenever the platform has them. Fuller events raise Event Match Quality, so Meta can tie more of them to real people.

What does not change

• Your pixel settings, with nothing to reconfigure.
• When PageView, ViewContent and Purchase fire.
• Cookie consent: without consent to advertising cookies, nothing is sent.
• Conversions API: browser and server events still go together and are deduplicated in Meta Events Manager.
• Orders that need no payment details still skip AddPaymentInfo. An order paid entirely with a gift card now triggers it, at a value of 0.
• Pixels that do not have InitiateCheckout switched on.

What to expect

• InitiateCheckout numbers will rise, because buyers who leave before paying are now counted. Keep that in mind when comparing figures from before and after the change, including automated rules and cost per InitiateCheckout.
• Page-level settings can take up to 24 hours on pages that are already published. Edit and save a page to apply them straight away.
• Every event for an order reports the same currency, and blank or invalid values are never sent.