Changelog

The UTM audit reads each pasted line whole, so a value with a space in it gets flagged; it takes links without https://, lists any line it skipped, and names the line and full link in every finding. The SEO audit ignores icon titles inside SVGs, warns when the canonical and og:url name different domains, and caps a noindex page at 40. The GTM audit no longer calls a container with no tags clean, and the retainer calculator asks for a missing or zero number instead of guessing one.

While phloz.com checks whether you’re signed in, the header and the plan buttons on /pricing hold a blank space instead of flashing “Sign in” and then swapping, and nothing on the page moves when the answer arrives. The phone menu no longer lets the page show through.

A receipt, update or reminder that reached your client’s inbox can no longer go a second time when Phloz loses track of it for a moment; the request panel shows such an email as unconfirmed rather than unsent.

A client’s message now counts as waiting until your team answers in that conversation; a reply in another one no longer hides it. The overview, the Messages badge, each client’s page and health score, the needs-reply view, the daily digest and your AI assistant all count the same way, and a waiting row opens the conversation that has waited longest.

Tap-to-call works for numbers written like “(mobile) 604-…” and for two numbers joined by a dash. An Ads health row for an account Phloz can’t read opens that client, the tracking report labels a warning “Warning”, and task titles stay readable on tablets.

The site, the sign-in pages, the browser tab and the share images now carry the new Phloz mark and wordmark.

The overview, clients, team, tasks, messages, tracking health and the client portal no longer scroll sideways or squeeze names down to a few letters on a phone, and contact phone numbers are tap-to-call.

A row in the overview’s recent activity opens its task or conversation, and an AI assistant’s change on the Activity log names the task and the status it set, with a link to pause AI changes. An AI reply drafted on a client’s request is addressed to the person who asked, not the shared inbox.

A client typing the changes they want no longer has Approve as the one-tap button beside the box, and an item waiting on their own approval no longer offers “Ask for an update”.

Google Ads pacing only judges a budget against an account in the same kind of dollars and says why an account’s check is failing; the negative keyword list is flagged while conversions have stopped. Client updates skip contacts who turned updates off, and the client brief shows the work finished in the last 30 days.

Owners and admins can switch a client to “Hidden from AI assistants”: connected assistants can no longer see it, its tasks, messages, map or Google Ads, while your team still sees everything. Settings → AI access can also pause every change from AI assistants at once; they keep reading until you switch it back.

A connected assistant can now read the lists behind the weekly Google Ads audit (the search terms worth negating, keywords with Quality Score, campaign budgets and targets), this month’s spend against the budget you agreed with the client, and a task in full with what the client wrote. Three ready-made prompts turn that into a paste-ready negative keyword list, a pacing check and reply drafts. Phloz never changes Google Ads, and every reply stays a draft a person sends.

The client’s monthly ad budgets card shows this month’s Google Ads spend against the budget, and where the month is heading at the last week’s pace, from the morning check (plans with Ads health).

The Activity log filters to AI assistants and to one connection, showing the changes they made and the calls that were refused, and owners and admins see each connection’s last 24 hours at a glance. Settings → AI access links each connection to its activity.

The monthly tracking-health report now honours the same switch as every progress email: a client who turned updates off doesn’t get it, and each report carries a one-click “Stop these updates” link that mail apps can offer as an unsubscribe button. Their portal still shows everything.

The sample bakery now comes with a Google Ads audit and a morning-check alert, made up to show what Phloz finds: search terms wasting money, settings that leak budget, and conversions that stopped while clicks carried on. It shows on every plan, labeled as a sample, and nothing in it comes from Google.

The privacy policy has a new section, Google user data: what Phloz reads when you connect Google Analytics, Tag Manager and Google Ads, what it keeps and for how long, who can see it, and what it never does with it (no ads, no selling, no AI training). Phloz still only reads from Google and never changes anything there.

A new workspace’s empty pages (Clients, Tasks, Messages, Contacts, Tracking health and Ads health) now offer two ways in: add your first client, or load a sample one, a bakery with contacts, tasks, emails and a tracking map, to look around first. The sample used to be offered on the overview alone, and most new workspaces explored the other pages first.

Each Google Ads alert now has a Create task button, on the overview and on the client’s page. It files a PPC task on that client saying what changed, the campaigns that moved most and what to check first, and marks the alert reviewed. While the task is open, the alert links to it instead of offering another.

On Growth and above, Phloz now checks every client’s Google Ads account each morning against its own last 4 weeks. Spend that stops or spikes, conversions short of what the clicks predict, a rising cost per conversion or a falling return on ad spend shows at the top of your overview and on the client’s page, and is emailed once to the teammates assigned to that client, or to owners and admins when nobody is. Mark an alert reviewed to take it off the overview; it closes by itself when the account recovers.

Phloz’s MCP server now gives a connected assistant a portfolio briefing that sorts every client you can see into urgent, soon and watch, with the numbers behind each flag, a one-call brief on any client, and the Google Ads alerts, daily figures and weekly audit. Three new ready-made prompts run a weekly portfolio review, diagnose a client’s Google Ads, and draft a client update for you to send. The data views an assistant opens are now in the Activity log too, like its tool calls.

When you cancel a paid plan, Phloz now emails you the date it ends and what Starter will keep, by name: the most recently active client stays, the others are archived, never deleted. The Billing page says the same, so you can archive the others yourself and choose which one stays. When the plan ends, by cancellation or a failed payment, the workspace fits Starter the way an ended trial does, and an email names what was kept and how to switch.

A new workspace now starts its 14-day free trial as soon as it is created, on the plan you picked on the pricing page or on Pro, with no card. Before, the trial waited until you opened checkout. Without a card, the workspace moves to Starter when the trial ends, keeping your most recently active client; the others are archived, never deleted, and an email names each one so you can unarchive it after you upgrade.

A task you shared with a client while it was already in progress emailed them that you had started work when a “Waiting on you” or an approval cleared, sometimes weeks in. Phloz now remembers that the client already saw the work in progress, so it only says so when work really starts, or restarts after it was completed.

When a connection dropped just as a client sent a request from the portal, or a teammate logged one, sending it again filed a second request with its own number and receipt. The same request sent again within 10 minutes now returns the first one. Reminders also check, before each contact, that the item still waits on the client, so nobody hears “still waiting” just after someone answered.

Yahoo Mail marks every new email in a way that looked like a reply, so a client writing from a Yahoo address never opened a request: their email joined an old conversation instead. A new email from Yahoo now opens a request like any other.

Opening a Phloz email’s link while signed in to a different account used to land on that account’s dashboard with no explanation. Phloz now says the link is for a workspace you’re not in, shows which account you’re signed in as, and can sign you in as the right one and take you to the link. Sign in with Google also lets you pick the account each time.

When your connection drops or changes while Phloz is saving, the page now says the connection was lost and offers to reload, since what you did may already be saved. It used to show a generic error, as if something had broken.

A client contact who forwards an email to their forwarding address now opens a request, as a new email does. Mail from someone who isn’t one of the client’s contacts no longer stops the “Waiting on you” and approval reminders, and the same email arriving twice is filed once. When a contact’s email stays a message, Phloz says why (for example, their domain didn’t pass DMARC), next to Log as request.

A CSV saved by Excel on Windows kept accented names as “M�ller”, which then didn’t match the client already in Phloz. Clients → Import now reads those files correctly, numbers rows right when a file starts with a blank line, and, for a file too long for one import, names the row to start a second file from.

The client portal now opens with Needs you: every approval you asked for and everything you marked Waiting on client, approvals first, each linking to its page with your note. Before, they were mixed into the request and shared-work lists, where one low in a long list was easy to miss.

A new email from one of a client’s contacts to the client’s forwarding address now becomes a request, with its reference and the receipt, as a request from the portal does. It has to pass the sender’s DMARC check, so a forged sender can’t file one; anything else, such as an out-of-office reply, is filed as a message you can still log as a request. Owners and admins can turn it off in Settings → Client requests by email.

When a client replies by email to a request or shared task you marked Waiting on client, and the email passes their domain’s DMARC check, the wait clears as a portal reply does, and the assignee is told. An out-of-office or other automatic reply is marked Auto-reply, and no longer stops the reminders.

Settings → Agency / Workspace now lists every time zone by region, with its current offset, and can use your device’s zone in one click; you no longer type a name like America/Vancouver. A workspace needs one, since reminders and the daily digest follow it.

Requesting a client’s approval now tells you when nobody it would reach can open the portal to answer (a request’s requester, or a shared task’s portal contacts) and how to fix it. Before, the ask went out and sat at Awaiting approval with no way for the client to give it.

Clients → Import now takes a CSV: your own client list, or another tool’s export of companies or contacts. Phloz matches the columns from the header, you correct any it got wrong and see what will be added first; rows with the same client name become one client with each row’s contact. A name already in Phloz is skipped, never merged, and contacts start without portal access, so no one is emailed.

Email to a client’s forwarding address from a sender who isn’t one of the client’s contacts (a vendor’s quote your forwarding rule passed on, a teammate’s other address, spam) no longer shows in the client’s portal under their name. Your team still sees it, tagged Unknown sender; add the sender as a contact and it shows in the portal too.

An email to a client’s forwarding address with an attachment over 5 MB used to be refused whole. Phloz now keeps its text, as it does for every email, and names the attachments it didn’t keep on the message and in your notification, so you can ask the sender for them another way.

The last “still waiting” reminder now names the day the request actually closes, and a request the client already approved is never promised a close. Asking for approval again right after a reset sends the client the new request. And “Stop these updates” now stops email to that inbox for every contact who shares it.

When you ask a client to approve a task or request and they don’t answer, Phloz now reminds them 3 and 7 business days later, on a weekday in your working hours, with the same “Stop these updates” link as your other client emails. No reminder goes once they’ve written to you, and Reset approval starts the count again.

Finding titles now read “TikTok pixel”, “Google Ads account” and “Custom node”, on screen and in the client report, instead of “Tiktok pixel” or “Google ads account”. A Meta Ads account no longer gets a “no pixel” warning when the map records Meta’s Conversions API as its own node.

Resetting your password has always ended every other session on your account. The confirmation now says so, and a browser that was signed in elsewhere goes to the sign-in page on its next click.

A workspace that starts paying in its first 30 days now keeps the trial’s daily limit on emailing new people until that first payment is a week old, instead of losing the limit the moment it pays. Card fraud is usually reported days after the payment, so this stops a stolen card from unlocking bulk email. Emails to people you’ve written to in the last day never count again, and the help center’s “Limits on client email” has the details.

Client email sent in your agency’s name now ends with a short “Sent by Phloz on behalf of” line and a link to phloz.com/report-abuse, so anyone who gets an email they didn’t expect can tell us. The line comes off once white-label is on and your workspace is paying and at least 30 days old. Settings and the help center’s “Limits on client email” explain the other checks that keep Phloz’s email trusted.

Client email now refuses shortened links (bit.ly, TinyURL and the like), because they hide where they go: paste the full link instead. And a new workspace’s first 24 hours of client email goes only to its own team, so you can try everything on yourself first. This keeps the email your clients get from Phloz trusted.

Google now asks for a passkey before it lets an app read Google Ads. Settings → Integrations and the help center say so: if your Google account has none, create one at g.co/passkeys before you connect, since Google can take up to 7 days to accept a new one.

Starter now includes a public intake form, so you can capture leads from your website before you pay for anything. File questions need a plan with file storage. If a paid plan or trial ends, your oldest published form stays open and the rest pause for visitors until you upgrade.

On the free plan, the monthly client report and weekly digest switches in Settings → Branding now show as locked, with the reason and the plan that includes them, instead of turning down your click. And until your workspace has used its free trial, a locked feature’s link says the plan behind it is free to try for 14 days.

Mark a task you share with a client as Waiting on client, with a note saying what you need: access to an account, a logo, an answer. Their portal contacts get an email, and reminders 3 and 7 business days later; they answer on the task’s page in the portal, which clears the wait. “Draft an access ask” starts the note from the client’s account list.

Where the hours went, on a client’s page, now exports this month’s or last month’s time entries as CSV, with their date, task, minutes, hours, note and who logged them, ready for your timesheet or invoice tool.

A conversation you started as an internal note is titled for your team. Emailing the client from it offered that title as the subject, and your client’s portal could show it. Neither happens now: the subject starts empty, and the portal never shows the title.

The email you get when a client confirms their tracking-health report now has its own switch in Settings → Notifications. It also respects vacation mode and a client you’ve muted.

At a client limit, Upgrade now suggests the first plan with room for the clients you already have, not simply the next plan up, which could still be too small.

Chrome on iPhone rewrote the dates and email addresses in the portal as it loaded, so the page had to draw itself a second time. The portal now asks it not to, and opens as it was sent.

Typing your workspace’s prefix on its own, like ACME, found nothing unless a dash followed. It now lists your tasks and requests, newest first, in search, on the Tasks page and in its CSV export; ACME- still lists the tasks and ACME-R the requests. Settings now says where the prefix came from, and that you can change it to match your agency’s name.

The client portal followed the device’s theme only. Your clients can now pick light, dark or their device’s setting from the portal’s header, or from the foot of the page on a phone, and the portal keeps their choice on that device.

Every request and shared task in the portal shows its reference, like ACME-R17. Your client can now copy it with one click, to quote it in an email or on a call.

Search, the Tasks page and its CSV export found a reference only when it was typed exactly. They now find ACME-R17 pasted from an email subject as [ACME-R17], typed as “ACME R17” or in lower case, and they search the title your client gave a request. In the ⌘K search, ACME-R on its own lists your requests, newest first.

On a client’s Contacts tab, “Copy link” made a portal sign-in link and showed it, leaving the copying to you. It now copies the link as soon as it’s made, and still shows it.

In the portal, a client’s own messages were tinted with your accent colour, so a light one, a yellow say, barely set them apart. They now use a darker shade of it that reads in light and dark mode.

In Apple Mail’s dark mode, on an iPhone or a Mac, bold names and some links turned the colour of the background and vanished: a client’s portal invitation read “has shared a secure portal with you” with your agency’s name missing. Every email now keeps its text readable in dark mode, and the small print at the foot of each one is darker in light mode.

Emails sent in your agency’s name put white text on your portal accent colour, so a light one, a yellow say, made “View your request” and the monthly report’s header hard to read. They now use dark text wherever white would not read.

“Log as request” on an email a teammate forwarded started the request’s details with the whole forward: the forwarding header and any line your teammate wrote above it. Your client reads those details back in their receipt, so they now start from the forwarded message alone. You can still edit them before logging.

A reply to a plan or trial confirmation went to an address nobody reads. It now reaches our support inbox, and the email says so. Annual prices read “$1,190/year”, as on the pricing page.

A member or viewer given no clients yet opened the Overview to “Add your first client” and a setup checklist they could not complete. They now read that no clients are shared with them yet, and that an owner or admin gives access from Team. Setting the workspace up stays with owners and admins.

The sign-up page promises 14 days free on Pro, Growth, Business or Scale, but the Billing page showed prices and Upgrade buttons without saying so, and the Overview said only that you were on the free plan. Both now say a new workspace’s first paid plan starts with a 14-day free trial, with no card needed.

A client you had just added showed “At risk · 40, Never active” until the next night’s update. Adding a client now counts as its first activity, so it starts at Healthy · 100, and an AI assistant’s list of stale clients leaves it out.

A task’s title shared its line with the task’s reference, badges and buttons when you opened it, and was cut to a few letters, like “Deliver trac…”. It now has a line of its own.

A weekly audit’s row showed a client’s score, warnings and info findings but not its critical ones; it now shows all of them. Status changes read “To do → In progress”, and two teammates with the same name are told apart by their email in the Actor filter. Routine entries, the daily digest sends and an AI assistant’s hourly key renewals, are hidden until you choose to show them: they were most of a busy log.

Before any audit had run, Ads Health asked you to connect Google and map a Google Ads account even when you had done both. It now asks only for what’s missing, and otherwise says when the first audit runs and how to run one now.

Due dates in the app and the client portal, and the dates on the tracking report you hand a client, now read like Oct 1, 2026. They read 10/1/2026 before, which a client outside the US can take for January 10.

When a client replies to one of a request’s emails, like its receipt or “We need something from you”, the reply now files in that request’s conversation, where you and the client both see it next to the request. So does a new email from one of the client’s contacts that quotes the request’s ID, like KELD-R17, in its subject, as the emails ask them to. Before, both went to the client’s latest conversation. An email doesn’t clear “Waiting on you” yet; turn that off once they’ve answered.

The task list has an Archived filter. An archived task used to show in no list at all, so only its ID or a link found it. It still stays off the default list and the board.

The button in a client’s monthly tracking report was a sign-in link that expired after an hour, so most clients who opened the email later hit an expired link first. It now opens your portal: a client still signed in goes straight in, and anyone else gets the sign-in page, which emails them a link.

Email that a teammate sends or forwards to a client’s forwarding address, and mail from your Portal contact email, is now filed as an internal note in a conversation of its own, marked with the address it came from. Before, it showed in the client’s portal as the client’s own message, in front of every contact. A client’s email you forward can still become a request: use Log as request on the note.

The daily digest and the weekly tracking-health digest now carry an unsubscribe link, and the one-click unsubscribe your mail app shows. It turns that digest off for you only. Owners and admins can also stop their own copy of the weekly digest in Settings → Notifications; the switch in Agency branding still stops it for everyone.

When a recurring template’s assignee has lost access to its client, the task it creates now lands unassigned, where your team’s lists show it, instead of on the name of someone who can’t open it. Give them access again and the next one is theirs.

A connected AI assistant renews its access every hour, and each renewal added an “AI access key issued” line to Activity. Renewals are no longer listed; connecting an assistant, and a reused or revoked key, still are.

A conversation you limited to one client contact stayed hidden from their colleagues after that contact was deleted, but the participants dialog said it was shared with the whole client, and saving it opened it to everyone. The dialog now shows the former contact, and the conversation stays private unless you uncheck them.

Phloz now checks each day that your custom portal domain still opens your client portal. If it stops (a changed DNS record, a lapsed domain), portal links move back to the Phloz address so clients can still sign in, and owners and admins get an email saying what was found and how to switch back.

A client’s GA4 property and Google Ads account decide what its analytics card and Ads Health read through your agency’s Google login, so only owners and admins set them now. Members still edit everything else on the map; a map they import or copy arrives with those two IDs blank for an owner or admin to fill in.

A task the client approved stays locked against changes, but you can now mark it done. Before, the lock refused that too, so under a “Required” approval policy a shared task could never be completed.

Adding, archiving and unarchiving a client is now for owners and admins, as the roles table always said: each client takes a slot on your plan. Members keep working on the clients they’re given, and are pointed to an owner or admin to add one.

Viewers can now comment on the tasks of the clients they can see, and edit or delete their own comments. They still can’t change the task itself, and they still don’t use a paid seat.

When you transfer ownership of a workspace, Stripe’s receipts, invoices and billing sign-in now go to the new owner. A separate billing email you set in Manage billing stays as it is.

When you remove a teammate, any Google account they connected under Settings → Integrations is disconnected too: revoked at Google and deleted from Phloz, and noted in the activity log. The Remove dialog names the account so you can reconnect it with another login.

The daily digest’s hour now runs from 6 AM to 11 PM. Recurring tasks are created at 6 AM in your workspace’s time zone, so a digest before then could never list that day’s.

In a workspace where members see only the clients they’re given, a client’s task, request or recurring task can now be assigned only to someone who can see that client. Phloz names the teammate and points you to Manage client access. Before, the task went on their name and they never saw it.

When a client replies to their portal sign-in email or their monthly tracking report, the reply now reaches you: it lands in the client’s Messages through their forwarding address, or goes to your Portal contact email (Settings → Agency branding), or to the workspace owner. Before, a reply to the sign-in email reached Phloz’s support inbox, and a reply to the report reached no one.

If you mark a task done while its client approval is still pending, the client’s portal now keeps it under the approvals waiting for them, with its buttons, until they answer. Before, it dropped out of the portal unanswered.

When a client confirms their tracking-health report in the portal, the client’s Audit tab now shows who signed, when, and the note they left, and the email you get links straight there. Before, the note was only in that email.

Some email security scanners open every link in a message, which used up your clients’ one-time portal sign-in links before they clicked them. A sign-in link now opens a page with a Continue button — your own on your portal domain — and only that button uses the link.

A workspace restored from a backup starts on Starter. Clients, recurring tasks and published intake forms past Starter’s limits now come back archived, paused or unpublished instead of all live, and the import says which. Nothing is deleted: upgrade, then unarchive, resume or publish them.

If you cancel a trial from Manage billing, the trial banner and the reminder emails now say it’s cancelled, that nothing will be charged and how to keep the plan. Before, they could say your card would be charged when the trial ended.

If you cancel your plan from Manage billing, the Billing page now says the date it ends and what happens then: the workspace moves to Starter and nothing in it is removed. Renew the plan from Manage billing and the notice goes away.

If a plan change or extra seats are waiting for you to confirm the payment with your bank, the Billing page now says so each time you open it, with a link to Stripe’s payment page and the time it lapses. Once it’s paid, the page shows the change by itself.

Your clients’ tracking card in the portal, and the monthly tracking report and its PDF, now say how many tracking points are set up, how many are verified and when they were last reviewed, instead of calling the tracking “monitored”. A client who confirmed the report before still reads as confirmed.

Clicking Convert to client twice on an intake lead, or converting it from two tabs, made two clients. The second try now makes nothing and says the lead is already converted.

When your bank asks to confirm the charge for a plan upgrade or extra seats (3-D Secure), Billing now sends you to Stripe’s payment page to confirm it, and the change goes through as soon as it’s paid. Until then nothing changes, and if you leave it, nothing is charged. Before, the change stopped and asked you to email us.

If you connect Google without allowing Google Ads on Google’s screen, Settings → Integrations now says so under the connection and how to fix it: connect the same account again and leave Google Ads ticked. It updates the connection you have.

The Import from Google picker on a client’s map now shows each property’s and container’s full name and details, including why a server container without its tagging URL can’t be picked, instead of cutting them off. Once an import is done, what you picked is cleared.

When the Google account you connected can’t read the Ads account mapped to a client, Ads health now says “No access to this account” and how to fix it (check the customer ID, or give that login access in Google Ads) instead of asking you to reconnect Google, which wouldn’t help. Findings also give Google’s reasons in plain words.

When a request is waiting on the client, they now get a reminder 3 and 7 business days later, sent on a weekday in your working hours; after 21 days without an answer the request closes and its assignee is told. Nothing goes out once the client has written to you. New requests also get a Requests to triage card on the Overview and a section in the daily digest for owners and admins.

When a shared task or request moves to In progress or Completed, or you request the client’s approval, the client now gets an email in your agency’s name a couple of minutes later, linking to the item when they use your portal. Every such email has a one-click “Stop these updates” link, and the portal’s item page lists the emails sent about it.

A client can now file a request from your client portal and gets a reference like KELD-R17 and an emailed receipt straight away; your team can log one from a call or an email too. Requests show in Tasks with a Request badge under Needs triage: accept one with an assignee, decline it with a reason the client sees, or mark it as a duplicate. The client sees Received, Accepted or Declined, and once you tick Client-visible, a progress bar and due date — the view shared tasks now get in place of their description.

Each task now carries a short ID made from your agency’s prefix and a number — KELD-142 — on its row, its card on the board, its subtasks, the dashboard, Mentions and the emails about it. Type an ID into the search on Tasks or the ⌘K palette to jump straight to it, or click the ID on an open task to copy a link a teammate can paste. Existing tasks were numbered in the order they were created, a number is never reused, and you can change the prefix in Settings — old IDs still open their task.

A new account by email can no longer be opened from Tor or another anonymizing network, and a sign-up whose name is a machine-made string is refused before any email goes out, so strangers’ inboxes stop getting confirmation emails they never asked for. Signing in, and signing up with Google, work as before.

When your client portal runs on your own domain, the page where clients ask for a new sign-in link now shows your name or logo and your colour, and a request there sends only your portal’s link. It showed a plain page, and a client who also works with another agency on Phloz got that agency’s link too.

When an assistant drafts a reply to a conversation your client started in their portal, the draft now opens in Messages → Drafts with “Re:” and the conversation’s title as its subject. It opened blank and went out as “(no subject)” unless you typed one.

When you add a card from the trial banner, or update it from the banner after a failed payment, Stripe now sends you straight back to Billing once the card is saved. You were left on Stripe’s confirmation page and had to find your own way back.

When a client starts a conversation in their portal and you answer it by email from Messages, the email’s subject is now “Re:” and the conversation’s title. It went out as “(no subject)” unless you typed one.

Opening a client’s tracking map full screen showed “Something went wrong” for any map with a node on it. It opens again, and every node and connection keeps the name a screen reader reads out. The map on the client’s page was not affected. On both, a map now opens clear of the toolbar, the Health key, the zoom buttons and the minimap: the Health key takes one row instead of a column, the minimap is smaller on a narrow screen, and the “?” beside each column’s name is easier to click or tap.

A sentence that ends on a client’s or an agency’s name no longer doubles the full stop when the name already has one, as “Acme Inc.” does. That covers the client portal’s welcome line, the footer of emails to clients, the daily digest and your notification emails.

Deleting a node or removing a connection on the tracking map now asks in Phloz’s own dialog, not the browser’s pop-up. Where the browser blocked that pop-up, the button did nothing at all.

The client portal no longer scrolls sideways on a phone when a conversation has a long subject. In the app, small buttons and links are easier to tap: the icons on a conversation, the map link on an account, calendar entries and a task’s client. An intake form’s embed code wraps instead of hiding off the edge, and a conversation’s Share button says what it does to a screen reader.

When you move through phloz.com with the Tab key, the link or button you land on no longer hides behind the cookie banner or the page header: the page scrolls it clear of both. On a phone, a wide table or code sample takes focus, scrolls with the arrow keys and is named after the heading above it, so a screen reader tells a post’s several apart. The GTM audit’s drop zone answers to the words on it for voice control, related-post summaries stay whole when you widen text spacing, and scrolling no longer glides if your system asks for less motion.

On a narrow phone, the pricing page, 20 blog posts and three tool and landing pages could be dragged sideways past the edge of the screen, and so could the client portal’s tracking strip. Wide tables now scroll inside their own box, long links wrap, and the page stays put. The weekly tracking-health email now fits a phone too, and the menu, Sign in and cookie buttons are easier to tap.

Exported CSVs and workspace backups are named for your workspace’s date, not the server’s, so an evening export in Vancouver no longer carries tomorrow’s date. When an import from Google Ads stops at an account problem, the “Not imported” list now names every campaign it didn’t get to, not just the one that hit the problem.

The free GTM container audit listed every tag with no consent settings for review, Google’s own tags included. Those check consent themselves, and requiring consent on them stops the cookieless pings Consent Mode models from, so the finding now lists only tags with no consent check at all: Custom HTML, pixels and templates that fire whatever the visitor chose.

If the security check on the sign-in or sign-up page can’t run in your browser — an extension or a network filter can block it — the page now says so within a few seconds and points you to Continue with Google, which doesn’t use the check, instead of waiting in silence and then only asking you to reload.

The pipeline strips on the tracking-health overview, the printable report and the Monday digest now mark each tracking point by shape as well as colour — broken is a square, missing a diamond, unverified an open circle, working a filled one — with a key beside every strip. Teammates who can’t tell red from green, and anyone reading a black-and-white print, see the same picture. Renaming a saved view or giving a snooze reason now opens a proper dialog.

When a client approves, rejects or asks for changes in the portal, their comment now shows under the task in your task lists, and the Activity log records which of the client’s contacts decided.

The workspace owner’s email about a client’s approval now respects vacation mode, the “Client approval changes” switch and mutes, and arrives once when the owner is also the assignee. A muted task leaves your daily digest. A viewer is no longer offered a reply-by-email they can’t send.

When you answer a Phloz notification by email and the email arrives twice at once, you no longer get a “Your reply couldn’t be posted” email for a reply your client already received. The reply is posted once.

Moving your workspace to a time zone further west no longer creates a recurring task a second time for a day it already ran, and the template’s “next” date agrees.

A node whose IDs you haven’t filled in yet can now be saved (marked Missing, say), exported, imported into another client and copied, with its blanks kept; before, one empty node could block the whole map. A value in the wrong format is refused by field, in words. A map imported from another client starts Unverified, while a client’s own file keeps what was verified.

If someone changed a node while you had it open, your save no longer overwrites their edit: Phloz keeps your changes and offers to reload the node.

Import from Google no longer preselects every property and container your login can see — you pick up to 50 of each. On a starter map it fills the empty placeholders instead of adding nodes beside them, and measurement IDs are looked up for every GA4 property you import.

A Billing page left open in another tab can no longer change or charge a plan it no longer shows — it asks you to refresh. A plan change keeps your monthly or annual billing, and the confirmation says whether Stripe charges your card now or credits your next invoice. Extra seats say plainly that they end with the plan.

A limit’s upgrade link now points to the first plan that covers what your workspace holds — members, pending invitations and extra seats included — and each lock names that plan. A refused downgrade lists every way through, including buying the difference as extra seats.

Link checkers that only test whether a sign-in link works no longer use it up before your client clicks. A client who is already signed in and opens an old link goes straight to their portal, and each sign-in email names the client it is for.

An @-mention in the portal emails only colleagues who can open that conversation, and a client’s reply to a new-message email lands in the conversation wherever Phloz can file it — otherwise the email says where to answer. A conversation that began as an internal note never shows its title in the client’s portal, and approval emails name the contact who decided.

Downloading a file from the client portal, a client’s Files tab or an intake submission now opens it even in browsers that block pop-ups. Before, the button could flip back with nothing opened.

When the tracking report changes after a client confirmed it, the portal says so and lets them confirm the new version. The portal’s browser tab now shows your agency’s name.

A member who adds a client can open it straight away; before, it disappeared from their lists until an admin granted access. An invited teammate who isn’t signed in now sees the invitation first, not a “Welcome back” sign-in page.

Exporting, importing or duplicating a client now keeps subtasks under their parent tasks and each task’s link to its tracking-map node, and a template map’s unfilled nodes come across whole.

A restored backup now keeps the audit rules you marked as not applying to a client, saved views filter the restored clients again, and tasks assigned to you stay yours when you restore your own backup. A backup holds no uploaded files, so the restore says how many it left out; files you added as links come back.

Verify on a custom portal domain now checks that the domain actually opens your client portal before your portal links switch to it. Until then, links keep using the Phloz address, and Branding says what is missing.

Asking a client to approve a task is offered on open tasks only, since the portal takes approvals on open tasks. The portal lists every task waiting for approval and orders the rest by priority correctly — High tasks were the first left out — and each of your client’s contacts can confirm the tracking report for themselves.

When a client’s tracking map reaches its node limit, the upgrade link now goes to a plan that allows more nodes. Pro, Growth, Business and Scale share one limit, so on those plans it points to Enterprise instead of a checkout that changes nothing.

Dashboard cards show real totals instead of stopping at five, Team counts every client a member can open (through departments and groups too), @-mentions in client emails appear on Mentions, and Ads Health amounts use the account’s currency. On a plan without intake forms, each form keeps its own on/off switch and shows whether it reopens after an upgrade. Upgrade links go to the workspace owner, everyone else is told who to ask, and teammates who open Billing see who manages it instead of an error.

Each finding on a client’s Audit tab now has a Create task button. The task takes the finding’s title, the node it’s about, what the audit found and the suggested fix, with a priority set by how serious the finding is. Once a finding has an open task, it shows “Task open” and links to it, so the same fix isn’t filed twice.

Import from Google now reads what kind each Tag Manager container is. A server-side container arrives on the map as a GTM server container with its tagging server URL, instead of as a web container; one with no tagging server URL set in Tag Manager is listed but has to be added by hand. Android and iOS containers are no longer listed, since the map has no node for them.

The Log time form on a client’s page now has an optional Task field listing that client’s tasks, most recently updated first. Time logged against a task shows up in “Where the hours went”, broken down by task and by department.

Each section of the daily digest lists up to five items and says how many more are waiting in Phloz, and the subject line counts the same items as the email. A client you muted no longer crowds out your other clients’ overdue tasks.

Only emails whose replies reach our team say so. Replying to a new-lead notification answers the lead (the email now tells you), replying to a message notification answers your client, and the monthly client report now shows your agency’s name at the top.

Settings → AI access (MCP) now lists a connected assistant for as long as it can reconnect, idle or not, so you can always revoke it there — with whose connection it is and when an unused one lapses. The Activity log shows each request an assistant makes under the teammate’s name and the connection’s, with what it wrote, or why it was refused.

When an AI assistant runs a client’s tracking audit, rules you snoozed on the Audit tab are left out, as they are in the app, and a large map is read in full rather than its first 100 items.

Our product analytics (PostHog) now run only if you allow analytics cookies, as our privacy policy says. Turning them off under Settings → Privacy & cookies stops them straight away and deletes what they stored, and PostHog no longer receives what you type into search boxes.

Everything you can do with a mouse now works from the keyboard too: connect and edit nodes on the tracking map from a node’s panel, reorder board cards and subtasks with Ctrl/⌘ and the arrow keys, and save views from the Views menu. Closing a dialog puts you back where you were, buttons and fields say which task, contact or client they belong to, and statuses shown by colour are also spelled out. Text meets contrast guidelines in light and dark mode — your brand colour in the client portal included, which now picks a readable text shade automatically — and one-letter shortcuts can be switched off in the keyboard shortcuts sheet (press ? or search “Keyboard shortcuts”). On a phone or tablet, board cards and subtasks have move up and move down buttons, and health scores show their grade in words. On phloz.com, links and labels are now easy to read in dark mode too.

The inbox, Mentions, the client list and the sidebar badges now load much faster in workspaces with thousands of messages and tasks — most of all for teammates who see only some clients. The Messages badge for clients waiting on a reply counts the last 60 days, like the dashboard, and so do the unreplied counts on the client list and on each client’s page. An email that hits our email provider’s rate limit is retried a moment later instead of failing at once, and a backup too large to import says so as soon as you pick the file.

What you change now shows at once and stays changed. The task board and task details show an edit as soon as it’s saved, and saving again no longer brings back old values; the task calendar follows you from month to month and shows tasks you add. On the tracking map, a connection that couldn’t be deleted or changed comes back instead of looking gone, a second connection between the same two nodes is drawn, and list fields such as measurement IDs take a comma as you type. Adding extra seats shows the new count right away, so the next purchase asks about the right total. Pressing Enter twice no longer starts two conversations or plans, a held Cmd/Ctrl+Enter in the client portal sends one reply, and confirm buttons run once. Re-saving your verified portal domain keeps it verified, and if your connection drops mid-save you keep what you typed and see a message instead of an error page. Back from checkout, the Billing page updates by itself once Stripe confirms, and a second checkout started before then is refused instead of opening a second subscription; if Stripe takes longer than usual to confirm a plan change, the plan button says so and reloads the page when clicked. A file whose upload fails stays picked, so trying again is one click, and a file of a type or size Phloz can’t store is turned away as soon as you pick it. Task links from mentions, search and emails open the client’s Tasks tab, a node you drag on the map stays where you put it, and error messages say what went wrong in words instead of a code.

Duplicating a client now keeps every task’s due date and the renewal date. Editing a finished task no longer marks it completed today, so your client portal’s recent activity stays accurate. The trial reminder and banner say “today” or “tomorrow” by your workspace’s calendar, “reviewed today / yesterday” counts calendar days in your timezone, and the weekly backup is dated with your local Sunday. Ads Health’s weekly audit compares two-week periods on your ad account’s own calendar, and AI assistants connected to Phloz are told your workspace’s date, so “due tomorrow” means your tomorrow.

Recurring tasks on an archived client now wait instead of creating new tasks and emails, and start again when you unarchive the client — the recurring list marks them “Waiting — client archived”. The daily digest also leaves archived clients’ messages and overdue tasks out. A conversation whose chosen teammates have all left or lost access now notifies owners and admins again, instead of nobody.

Revoking an AI connection in Settings now either revokes everything it can reach or nothing, so a failed attempt stays on the list to try again. An AI draft that fails to send goes back to your review queue, a duplicate department or group name says it already exists, and restoring a workspace backup no longer fails when two teammates saved views with the same name. Owners and admins can delete a teammate’s shared saved view, and removing the demo client also removes its files. Billing updates from Stripe that arrive at the same moment now apply in the order they happened, so an older plan status can no longer overwrite a newer one, and starting a plan from two tabs at once sets up one billing account instead of two.

A teammate who can only see some clients now gets a daily digest and an overdue count covering just those clients. A client-visible task on a client that requires approval can no longer be marked done before sign-off by any route — a new task, a subtask or an edit — and email from a client’s conversation goes only to that client’s contacts or business address. Re-sending an invitation now updates the clients it gives access to.

Clients brought in with a workspace import now get their own forwarding address, shown on each client page, as clients you add by hand always have. Before, an imported client had none, so there was no address to forward its email to.

A lead can now be deleted from its form’s submission list, and a whole form from the bottom of its editor, each after a confirmation. Files a lead uploaded are deleted with it, and clients you already created from a lead stay. Public forms also check that an email address and a phone number look real, and each workspace’s forms have an hourly limit, so a burst of bot submissions cannot flood your inbox or Slack.

Turning a contact’s portal access on or off, and every sign-in link your team emails or copies from the Contacts tab, now shows in the Activity log. Changing a contact’s email address signs the old address out of the portal. Portal sign-in emails carry your agency’s display name, the monthly tracking report’s button opens your own portal domain when you have one, and the portal names who wrote each message instead of labelling every client message “You”.

A month with one task on it looked like a broken calendar. The task calendar now says how many dated tasks sit in other months, with a jump to the nearest one each way, and how many open tasks have no due date at all. Every client’s Tasks tab gains a Calendar view of that client’s work, and a recurring task set to “0 days” is now due the day it is created instead of carrying no date.

When the activity log is open to every member, a teammate who can only see some clients now sees only rows about those clients, workspace-level changes and their own actions — the same rule as the rest of the app. Removing a teammate now also revokes their AI-access tokens for the workspace and cancels any pending invitation to their address, and inviting someone who is already a member says so instead of sending mail.

When you snooze an audit rule for a client, it now stays out of the weekly tracking-health digest, the daily digest’s audit card, the monthly client report, the tracking-health page and its CSV export, and the client portal’s summary — and it no longer counts against the score on any of them. The client page and the printable report already worked this way.

The weekly backup email and the manual export no longer include your Slack webhook URL — a credential that should not travel in an attachment. After restoring a backup, reconnect Slack in Settings.

The client Overview used to show two look-alike cards — Accounts, typed by hand, and Platform IDs, read from the tracking map. They are one list now: IDs on the map appear on their own with a link to their node, anything you typed stays editable, an ID that lives in both places shows once, and the GA4 property ID is included.

Subscribing on phloz.com now sends a one-click confirmation email, and only confirmed addresses ever receive anything — a typo or an automated submission can no longer put someone on the list. A hidden field on the form turns away the scripts that fill every input, and a second submit re-sends the confirmation at most once a day.

A description typed while creating a task was saved but never shown: opening the task showed only its title, and its Edit form started blank, so saving any other change quietly erased the description. The task dialog now shows the description, and editing starts from what is already there.

After entering a correct email and password, the page could stay on the sign-in form as if nothing had happened — you were signed in, but the app reused an answer it had cached before you were. Signing in and signing up now load your workspace directly.

The sign-in, sign-up and password-reset forms run a short security check before their button turns on. When that check failed to load — an ad blocker, an unsupported browser, a slow network — the button stayed greyed out with no explanation. The form now waits 15 seconds, then lets you continue and says so under the check; if our side then refuses the attempt, you see “Security check failed” with what to do next instead of “Invalid email or password”.

Create your workspace or sign in with your Google account — one click, no password, no email link. Google Workspace accounts work too, and an existing Phloz account under the same email is signed into, not duplicated.

app.phloz.com pages pointed browsers at a favicon file that did not exist, so tabs showed no icon. They now use the generated Phloz mark.

Every email Phloz sends on its own behalf — welcome, password reset, invitations, the daily and weekly digests, backups, trial notices — came from a no-reply address, so hitting Reply could bounce even though the footer said a reply would reach us. Those emails now reply to contact@phloz.com, where a person reads them. Emails your agency sends to clients under its own name are unchanged.

The footer of the daily digest email said a setting to mute it was “coming” and asked you to reply to opt out — long after the “Send me the daily digest” toggle had shipped under Settings → Notifications. The footer now links straight there, the way every other notification email from Phloz does.

Every page of the app was carrying the form-validation library’s messages in 53 languages — about 200 KB of text nobody ever saw, since Phloz shows them in English — and every page of both the app and phloz.com was downloading the whole shared component kit, dialogs and menus included, even where a page used only a button. Only what a page uses ships now, and the app’s error-reporting tools wait until the login and signup pages are idle before they load. phloz.com pages reference about a quarter less script than yesterday and the login page about 45 percent less, so screens become interactive sooner, most noticeably on slower connections.

The marketing site was downloading a product-analytics library on every page that it never switched on — about 220 KB of script. It no longer ships there, and in the app it now loads after the page is already interactive. The error-reporting library on phloz.com (another 235 KB or so) now waits until the page is idle, and anything that goes wrong before it arrives is kept and reported the moment it does. Together, the homepage references about a third less script than it did the day before, so pages respond sooner on slower connections.

Both the app and phloz.com were shipping a block of Node.js compatibility code that browsers never needed — about 440 KB on every page, close to a third of the script on the homepage and a fifth on the login page. It is gone, so pages become interactive sooner, most noticeably on slower connections.

Changes only owners and admins can make — portal branding and white-label, a custom portal domain, the Slack notification destination, who can see all clients or the activity log, the weekly backup, a teammate’s client access, a revoked invitation, and intake forms and their lead stages — now appear in the workspace activity log with who made them and when. The Slack webhook itself is never recorded.

A task comment added by Claude (or any assistant connected through MCP) now carries your name in the app instead of no author, marking a tracking node verified records who verified it and shows up in the node’s version history like an edit made in the app, and archived clients are read-only for assistants the way they are for people.

When you connect an AI assistant to Phloz, the approval screen now headlines the address Phloz has actually verified — for Claude that is claude.ai — and shows the name the app calls itself underneath. If an app would send you somewhere other than the address that identifies it, the screen says so before you approve.

The JSON backup (Settings → Backup & export, and the weekly emailed copy) had left out six kinds of data added after it was built: time entries, intake forms and their submissions, department plan docs, tracking-health sign-offs and each client’s platform account IDs. They are in every backup from today, and importing a backup restores them — an imported intake form gets a fresh public link. Messages, comments and connected-account tokens stay out on purpose.

Dates the app writes for you on the server — “Active Sep 8” on the client list, when a client was added, the activity log, the dashboard feed, the tracking-health print date — used the server’s UTC clock, so an evening in Vancouver could read as tomorrow. They now follow your workspace’s time zone, and the activity log shows your wall-clock times.

A new Outline button on every tracking map lists the whole map in reading order — each lane, each node with its type, health, last verification, IDs and open findings, and every connection both ways. Click a row to jump to the node, or copy the whole outline as plain text to paste into a client email. Screen readers now hear what each node and connection actually is, Tab reaches every node, and Enter opens it.

Every lane header on a tracking map now has a “?” — one sentence on what the lane is for (where data originates, what routes it, what measures it, where the spend happens, what the business counts) and the node types that belong there. Handy when a newer teammate or a prospect is looking at a client’s stack for the first time.

Every tracking-map node with open audit findings now wears a count badge — coloured by the worst finding — so a client’s problem spots read at a glance, and each node shows its real identifiers (GTM container, GA4 property, pixel ID) on its face instead of only in the side panel.

Every client flagged in your Monday tracking-health digest now comes with its pipeline strip — the labeled lanes, one dot per tracking point in its health color — right under the score and the top finding, so you can see where in the setup the trouble sits before you open the app. It’s an image behind plain text, so the email reads the same with images off.

A task due "September 8" could show as September 7 for anyone west of UTC, slip back a day each time you re-saved it, and count as overdue from midnight on the dashboard and in the daily digest. Due dates are now plain calendar days everywhere — the list, the board, the calendar (drag-to-reschedule included), client pages, the digest, exports, and the MCP tools, which now take and return YYYY-MM-DD. The retainer renewal date on a client page had the same day-early problem and is fixed the same way.

Creating an account now takes a name, an email, and one click — we email you a secure link that signs you in and drops you straight into workspace setup. Prefer a password? Set one during signup, or add one any time later from Settings. Either way you can always sign in with an emailed link.

The workspace switcher’s "Create a workspace" quietly bounced you back to your dashboard if you already had one. It now opens the creation form as intended. Each workspace stays fully separate — its own clients, team, and billing.

Search now lives in one place: the search field in the sidebar (⌘K / Ctrl+K), which finds clients, contacts, tasks, messages, comments, tracking points, and files — scoped to what you have access to. The separate Search page showed the same results with an extra click, so it’s gone; old links land on your overview.

The printable tracking-health report now shows the client’s whole pipeline as one glanceable line — labeled lanes, every tracking point with its health color — so the PDF you hand a client carries the picture, not just the numbers. And every row of the cross-client overview now carries a compact pipeline (capped dots per lane), so you can see where in a client’s setup the trouble sits before you click through.

Every tracking node can now record whose login the account lives in: agency-owned, client-owned, or unknown. Agency-owned items are the ones a client loses access to if they ever leave, so the map rolls them up into one line — "N items live in agency-owned accounts — plan a handover" — the offboarding-risk view no other agency tool models. And when you map a Google Ads account, you can now pick it from the accounts your connected Google login can actually see instead of typing the customer ID by hand — a typo-shaped ID can look perfectly valid and still be nobody’s account.

On the tracking map, "Last verified: 2 days ago" now says who verified it — a verification is a teammate’s claim, so the claim carries its author (recorded from today onward; older ones stay date-only). The node editor also explains its two buttons: Save keeps your edits, Save + mark verified stamps the node as checked today. And drawing a connection got smarter: Phloz pre-selects the likely relationship from the two node types, warns when a drag is probably pointing the wrong way, refuses a duplicate drawn backwards, and gives every connection a one-click Swap direction. Select a node or a connection and its edges now animate in the direction the data moves — direction you can see, only where you’re looking (and switched off entirely if your system asks for reduced motion).

When a card payment fails after your trial converts, Stripe retries on its own schedule — and until now the app said nothing while that happened. A banner now appears on every page of the workspace while payment collection is failing, says plainly what happens if no card works (the workspace moves to the free tier; nothing is deleted), and takes the owner straight to the card form to fix it in one click.

The 14-day trial now shows a countdown on every page of your workspace, with a one-click button that opens the card form directly — not the billing portal’s front page. Reminder emails go out 7, 3, and 1 days before the end, and they say the honest thing: with no card on file, nothing is ever charged — the workspace simply returns to the free Starter tier, with all your data intact. Deadline dates now include the time and timezone, and new workspaces pick up your timezone automatically, so “ends Aug 28” means Aug 28 where you are.

After signing up, the page now switches to a clear “check your email” panel instead of leaving the form live — no more wondering whether the click worked, and no accidental duplicate confirmation emails. On the tracking map, pressing Backspace with a node selected used to permanently delete every connection attached to it; connections are now only deleted when you select them deliberately, and connection lines land exactly on the dots they belong to.

If someone on a view-only seat clicked Save on a tracking-map node, deleted a file, or sent an AI-drafted reply, Phloz was right to stop them — but the only thing it said was the word "forbidden", and the button was there to click in the first place. Across the app, controls a seat cannot use no longer render for that seat, and where the surface stays visible it now says plainly what the role can and cannot do. Every error message anywhere in Phloz was rewritten at the same time: instead of an internal code, you get a sentence that says what happened and what to do about it. No permissions changed — what changed is that the app now tells you the truth before you click.

A new Analytics platform node type covers non-GA4 stacks — Matomo, Piwik Pro, Adobe, Plausible, Fathom — so privacy-first clients can finally be modelled properly, and the audit stops asking them where their GA4 is. Two new checks bring the tracking audit to 20 rules: a Microsoft Ads account with no UET tag, and a LinkedIn Ads account with neither an Insight Tag nor conversions sent server-side. Both platforms were previously invisible to the audit — an account running with no tag at all scored a clean 100. Separately, suppressing a rule now removes it from the printable report and from the 0-100 score, not just from the findings list: telling the audit a rule does not apply to a client used to stop it appearing in one place while it quietly kept costing points forever.

Connect Google and Phloz now audits every client’s Google Ads account weekly, ranked worst-first: search terms that burned money with zero conversions (with the dollars attached), conversion tracking that broke or was never set up, campaigns whose budget is starving your best performers, disapproved ads, and more. Every account gets a 0–100 score you can watch move. Thresholds compare each account against its own history and Google’s own signals — never invented industry averages. Read-only: Phloz never writes to your Google Ads. Available on Growth and above.

When the tracking-health card is enabled for your portal, clients now see a compact pipeline strip of their own setup — the same labeled lanes your map uses, with verified points in green and the rest in blue. It is deliberately client-safe: it shows generic tracking-point types rather than your internal node labels, and never surfaces broken or critical states, findings, or scores — that diagnostic detail stays on your side. Clients see coverage: what is tracked, and that it is looked after.

Click Arrange and the map now lays out in named pipeline columns — Sources, Tag management, Pixels & analytics, Ad platforms, Conversions & CRM — with a header over each column your map actually uses (a two-lane map gets two tidy columns, not five with gaps). Every client’s map reads the same left-to-right way, so anyone on your team can parse an unfamiliar stack in seconds. Your saved layouts are untouched until you click Arrange, and the headers only appear while the map is actually in columns.

Connections on the tracking map are directional — a pixel fires, a tag reports conversions to an account, an account pushes audiences to another — but they were drawn as plain lines, so you could not tell direction at a glance without opening each one. Connections now carry an arrowhead pointing at the destination. Nothing about your existing maps changed; they just read correctly now.

The confirmation dialog for an in-place plan change decided its wording from the direction of the change alone, so every downgrade said "nothing is charged today". That is only true when you stay on the same billing period — switching between monthly and annual bills the prorated difference immediately, which meant some downgrades charged a card under a message promising they would not. The dialog now states what will actually happen for your current billing period. No charge behaviour changed; the message did.

Magic links were landing clients on the agency login screen instead of their portal. If you sent a portal invite recently and the client said they could not get in, this was why — the link and their access were always fine. Fixed and verified end to end. Nothing to resend unless the link has since expired.

The reminder sent a few days before a trial converts was going out with a password-reset subject line and a password-reset body. It is now a proper notice: which plan you are moving to, the date it happens, and one link to change or cancel it. If you got a confusing "reset your password" email from us during a trial, that was this, and nothing was wrong with your account.

Cmd/Ctrl+K now opens node search on the map — the shortcut was documented but never actually reachable. Two related fixes: the node drawer no longer closes and discards what you typed when a save fails, and dragging a node now tells you if the new position could not be saved instead of silently reverting on the next reload.

Retainer burn showed the next month’s empty bar for a few hours around every month boundary, and the daily digest could name the wrong day in its subject line. Both now use your workspace timezone, matching the numbers inside them. Workspaces behind UTC saw this most often.

Convert an intake-form lead into a client and three onboarding tasks appear on the new client automatically: the kickoff call, collecting access (GA4, GTM, ad accounts), and building the tracking map — due-dated over the first week. They are ordinary tasks: edit, reassign, or delete them like any other. New clients start with a plan instead of a blank page.

Settings now has a Privacy & cookies card: see whether analytics cookies are on for your browser and switch them on or off in one click, without leaving the app. It shares one preference with phloz.com, so setting it in either place covers both — and analytics stay off until you say otherwise.

The one-click workspace backup download stays a paid feature, but the right to your data does not depend on your plan: email privacy@phloz.com on any tier — including the free tier, and for 30 days after you cancel — and we will send you the same full export at no charge. Our Terms and DPA now say so in writing. Paid plans also see clearer terms and auto-renewal wording at the point of purchase.

The Plans tab can now pull live Search campaigns from a client’s connected Google Ads account — each one becomes a campaign blueprint with its ad groups, RSA headlines and descriptions, keywords with match types, negatives, and geo targeting. Read-only against Google: your live campaigns are never touched. "Import from Google" on the tracking map also lists your Ads accounts now, so mapping a client is a checkbox instead of typing a customer ID — and an empty tracking map greets you with a one-click starter setup instead of a blank canvas.

Clients with a mapped Google Ads account get an Ads insights card: last-30-day spend, clicks and conversions, the ten priciest keywords and search terms by CPC, campaigns being throttled by budget, and any disapproved ads — pulled live and read-only from the Google Ads API, right next to the GA4 insights card.

phloz.com/legal now hosts the full policy set: Terms of Service, Privacy Policy, a GDPR Data Processing Addendum, an Acceptable Use Policy, and a public subprocessor list with change notifications. The client portal links Privacy and Terms too, and signup asks for explicit agreement.

Portal links are now single-use and short-lived: your client clicks the link once, and a secure session keeps them signed in for 30 days — the link itself no longer works if forwarded or leaked. Clients can request a fresh link themselves from the new portal sign-in page, and a Sign out link ends the session on shared machines.

Every intake form now has a copy-paste embed script. Grab it from the form builder, drop it on your site, and the form appears right there — auto-sizing to fit, with submissions landing in your inbox and lead pipeline as usual. Prefer an iframe? That is one click away too.

Every tracking-map node now keeps an edit history. Open a node and expand "History" to see who created it and each change since — health status flips, renamed labels, updated IDs — with names and timestamps. Handy for "when did this pixel get marked broken, and by whom?"

Shift-drag a box (or shift-click) to select several nodes on a tracking map, then set them all to the same health status or delete them together — perfect after spotlighting everything that’s unverified or broken. Setting a batch to Working also stamps them as freshly verified.

The tracking map now has a health legend in the corner showing how many nodes are broken, missing, unverified or working. Click a status to spotlight just those nodes — everything else dims out — so you can glance at a client’s setup and see exactly what needs fixing.

Emails your clients receive from a conversation now carry the team member’s name and email address, not just the agency name. And when the recipient has portal access, the email includes a "Continue in your portal" button — a fresh sign-in link that works for 60 minutes — that lands directly on that conversation.

A full contrast pass over the light theme: status badges, amber warnings, approval pills in the client portal, form errors and delete buttons that were washed out on white now meet proper contrast in both themes.

Running the same stack across clients? The map tab now has "Copy from client" — it clones another client's tracking map (nodes, connections and layout) onto the current one in one click. Copied nodes arrive marked Unverified so you know to swap in the right account IDs for the new client.

When you @-tag a teammate or client contact in a conversation or comment, the tag now displays their name (hover shows the address) — the email only appears when no name is on file.

Changing plans on a subscribed workspace now shows a confirmation that says exactly what happens: upgrades charge the prorated difference to your card on file immediately, downgrades credit unused time to your next invoice. Plan and billing changes are also now limited to the workspace owner.

The app sidebar is now reachable on phones — tap the menu button in the top bar to jump to any section (clients, tasks, messages, tracking health, settings) from anywhere. And every conversation composer, in the app and the client portal, now carries a standing reminder not to share passwords, card details or other sensitive information in messages.

If two people (or two tabs) edit the same plan document, the second save no longer silently overwrites the first — Phloz detects the conflict and asks you to reload before saving. Inbound email processing also got sturdier: a delivery retry from your email provider can no longer create a duplicate message in a conversation.

Onboarding a client that looks like one you already run? Duplicate creates a full copy — profile, contacts, account directory, tasks, plans and tracking map — in one click. You can also import a client export file to recreate a client, which makes moving a client between workspaces (or restoring one) a two-step job. Portal access always starts switched off on the copy, so nothing is shared until you say so.

Need one more teammate without jumping a whole tier? Every paid plan can now add extra seats from the billing page — pick a quantity, check out, and the seats are available immediately. Plan changes also got smoother: upgrades and downgrades apply to your existing subscription (no juggling multiple subscriptions), and every tier change sends a confirmation email.

Client files can now be organised into folders — pick or create one when uploading, move files later, and filter by folder with one click. Files shared to the client portal show up grouped under the same headings, so clients see the structure too.

Conversation notifications, mention alerts and client-facing replies now arrive in a clean branded layout — with your agency’s accent colour on client-facing messages — instead of plain text. Same information, much easier to scan.

Connect your Google account once (Settings → Integrations, read-only — Phloz never changes anything in your accounts) and every client map gets an “Import from Google” button: pick the GA4 properties and GTM containers that belong to that client and they appear as map nodes with their real IDs — no more copy-pasting measurement IDs from five consoles. Re-importing skips what is already mapped.

Owners and admins can export everything about a client — profile, contacts, account IDs, tasks, plans, tracking map, time log — as a single file from the client header. Your clients get a “Report a problem” link in their portal that emails your support address directly, and every team member has a “Send feedback” button in the sidebar that goes straight to the people building Phloz.

The Plans tab now imports the files you already have: download an Ad report or Keyword Planner export from Google Ads and drop it in — it becomes a campaign blueprint or keyword research list, ad groups, match types and all. Prefer a spreadsheet? Grab a blank CSV template from the import dialog. Every plan also exports back to CSV, so nothing is locked in.

Every client gets a Plans tab with planning tools per department. Draft Google Search and Performance Max campaigns (plus Meta and LinkedIn) with live character counters on every headline and description — the same limits Google enforces — along with keywords, negatives, geo targeting and sitelinks. SEO gets page plans with title-tag and meta-description counters, and every department gets keyword research lists and strategy notes. Each plan is internal by default; flip one to “Client can see” and it appears read-only in their portal.

Type @ while writing an email to a client to loop in a teammate: they get notified and it lands in their Mentions inbox, while your client just sees the teammate’s name — never a raw @-handle. Connecting Claude (claude.ai) to your workspace via the custom connector also works now, and the client Overview keeps a single, simpler Accounts editor.

Conversation notifications got a full upgrade: they now show the client’s entire message (not a snippet), come from “ClientCo (Your Agency)” with the conversation as the subject, list which teammates were also notified — and you can simply reply to the email. Your reply is sent to the client and logged in the conversation, exactly as if you’d sent it from the app.

The Team page is read-only for non-admin members (management controls are owner/admin-only), a member’s dashboard counts only the clients they can access, the new-task form puts the client choice front and center (and labels internal tasks as “Internal” everywhere), the Google ID quick fields show their Save button permanently, and conversations whose last message was a note now open on the note tab so @-mentions are right there.

The “New conversation” button on a client can now open with an email instead of an internal note — pick the contact, write the subject and message, and the reply threads straight back into the same conversation. You no longer have to wait for a client to write in first. Teammate @-mentions now autocomplete when starting a conversation with a note, too.

The retainer terms, this month’s burn bar, and the time ledger moved from the (very long) client Overview to their own Retainer tab, with an hours-vs-budget chip in the client header that jumps straight to it. The Overview also folds the Google IDs quick fields into the Accounts card — one place for every account ID.

Portal branding has a new “Portal contact email” field — set a shared inbox like hello@youragency.com and that’s what clients see as their agency contact, instead of the workspace owner’s personal login email.

Tasks belonging to archived clients now stay out of the Tasks page (a pill reveals them when you need the history), an open task links to its client so you always know whose work it is, and the client Files tab accepts drag-and-drop uploads.

Every conversation now has a Participants control: limit which of a client’s contacts can see it in their portal (leave it open to share with the whole client), and choose which teammates get notified when the client replies. When you reply, everyone on the conversation gets a heads-up — not just the one address. Great for a thread that should stay between one stakeholder and a specific person on your team.

Clients can now type “@” in a portal conversation to tag an assigned teammate or one of their own colleagues on the account — the person tagged gets an email, and teammate mentions also show up on your Mentions page and sidebar badge, right alongside internal-note mentions.

The client portal now leads with a “New conversation” button — your clients can open a fresh thread and give it a subject, instead of only replying to existing messages. The name they choose shows on the conversation for both sides.

Added honest Phloz-vs-GoHighLevel comparison and "GoHighLevel alternative" pages (the two are usually complementary — GHL for marketing automation, Phloz for the tracking layer and delivery work). Our Terms and Privacy Policy were also rewritten to be clearer and more complete, and comparison pages now carry a standard trademark/fair-use note.

Priority badges now read clearly in both light and dark themes (they were washed out on light backgrounds), and the task filter row is monochrome — colour on the tasks page now means one thing, priority urgency, and only on the task cards themselves.

Typing quickly in a search box could lose the last few characters as the URL updated behind the scenes. The input now keeps exactly what you type.

The agency logo you upload in branding now shows as your workspace mark in the sidebar and as the browser-tab icon on your client portals — no more placeholder square, no more anonymous tabs.

Task rows and board cards dropped the per-row color soup: departments are now plain labels, and color only fires for urgency — urgent and high priorities show as a single tinted pill. Department and status colors still appear where they act as legends (filters, pickers, group headers).

The dashboard’s browser-tab icon was being swallowed by the login redirect. app.phloz.com tabs now show the Phloz mark.

Set a planned monthly ad budget per platform (Google Ads, Meta, Microsoft, TikTok, LinkedIn) on each client — the clients list now shows the total alongside retainer MRR, plus the website platform and up to six account-ID chips per card. Google Business Profile, Search Console, and Merchant Center also gained fixed quick-fields on the client overview.

Your profile, theme toggle, and the marketing-site link now sit at the top of the sidebar, right under the workspace name — they had drifted below the fold as navigation grew.

The tracking map’s “Add node” dropdown could extend past the bottom of the window, making the last group unreachable. It now caps its height to the available space and scrolls inside the viewport.

Some inbound notifications arrive with no message content at all. Phloz now fetches the full email from the provider by ID when that happens, so the reply text shows up in the thread instead of an empty bubble.

Some inbound client replies arrived with the message content only inside the raw email payload — the thread then showed an address instead of the reply. The inbound parser now decodes the raw email itself (and will never mistake an email address for the message body).

Typing a login URL without https:// (like “agency.com/wp-admin”) now opens the real site — previously the link resolved inside the app. Bare domains are normalized automatically.

The client overview’s platforms card grew up: expanded provider suggestions across website, booking, newsletter, e-commerce, and a new chat category; contact forms now accept multiple providers as chips; every category can carry an admin login URL with a one-click “Log in” button; and a new Business identifiers card records GST/HST, PST, business number, incorporation number, DUNS, and EIN per client.

Cards on the task board can now be dragged to a manual position inside their column — an insertion line shows where the card will land. Columns you never reorder keep sorting by priority and due date, as before.

Intake submissions now move through a lite new-business funnel — new, contacted, proposal, won, lost — with stage counts on the submissions view. Converting a lead to a client marks it won automatically. Deliberately lightweight: no deal values or forecasting.

Unread badges on each client’s conversation rail, an unread dot on global-inbox rows, and an unread-conversations counter on the Messages nav item. Opening a conversation marks it read, and inbox rows deep-link straight to the conversation they reference.

The weekly tracking-health digest now flags clients at or over their monthly retainer hours. The “where the hours went” card splits logged time by department, and time entries can be edited inline after logging.

Set monthly retainer hours per client, log time against tasks, and watch a live burn bar on the client overview. Deliberately lightweight — no invoicing or job costing, just “are we over-serving this retainer?” at a glance.

Every client’s tracking setup now rolls up to a single 0–100 score — on the client report, the Audit tab, the cross-client list, and the CSV export — with week-over-week deltas in the weekly digest.

A weekly email that leads with what changed: clients whose tracking health moved, new audit findings, and (since July) retainer-burn alerts. Sent only when there is something worth reading.

A call-tracking node type for the tracking-infrastructure map, including dynamic number insertion (DNI), plus an audit rule that catches DNI setups that would break session attribution.

Per-client approval policy (none / optional / required) and lock-on-approve: once a client approves a task, it can’t be quietly edited afterwards.

An editable directory of every platform account per client (GA4, GTM, ad accounts) with card chips on the client overview, plus a record of which service providers each client uses.

GA4 nodes gained account/property structure and cross-domain fields; Google product links (Ads, Search Console, Merchant Center, Business Profile) and a GTM link toggle round out the map’s fidelity to real setups.

Message threads now carry titles — name a conversation, rename it later, and start a new conversation on any client without waiting for an inbound email.

Clients can confirm the tracking-health report in their portal. Sign-off snapshots the report state and emails the agency — a paper trail for “yes, we saw it.”

An opt-in scheduled monthly email sends each client a branded tracking-health report with a PDF attachment — agency name, logo, and accent color throughout. Pro tier and above.

Business tier and above can serve the client portal from their own domain, completing the white-label story alongside the earlier “remove Powered by Phloz” option.

A third free tool: paste a page’s HTML and get an on-page SEO audit — title, meta description, canonical, robots, headings, Open Graph, structured data, image alts. Runs entirely in your browser; nothing is uploaded.

One screen ranking every client by tracking health, with CSV export and a per-client print-to-PDF report. The weekly audit engine (17 rules) feeds it automatically.

Paste campaign URLs and catch typo’d UTM keys, case splits, source synonyms, and mediums GA4 buckets as Unassigned. Browser-side, nothing uploaded.

The Phloz MCP server now supports OAuth — connect Claude to your workspace in one click from claude.ai, no token pasting. Reads and gated writes stay scoped to workspace, role, and client assignment.

Connected AI assistants can draft replies to client messages. Drafts land in a review queue — a human always sends or discards; nothing is ever auto-sent.

Phloz ships a built-in MCP server — connect Claude or any MCP client to read clients, tasks, messages, and tracking maps, and perform audited write actions. Growth tier and above.