A personal LinkedIn writing partner
For founders, executives, and professionals building a personal LinkedIn presence
Personal LinkedIn drafting now behaves more like an editorial partner than a generic copy generator. It asks for a stronger angle when a brief is vague, can learn from reference posts you paste, and suggests better alternatives when an idea needs sharpening. You can also give lasting preferences such as tone, structure, or words to avoid, and those instructions follow you across workspaces. Each new draft therefore begins with the voice and standards you have already established.
Why it matters: Building a recognizable personal voice required repeating the same corrections in every draft. Weak prompts could also produce safe, promotional copy instead of a post that sounded like the person publishing it. That extra uncertainty slowed reviews and made the next practical step harder to choose.
One media library and precise AI reference context
For marketers creating content from product, brand, and visual references
Glowtify now brings crawled visuals, offerings, uploads, and generated images into one media library that assistants can browse when creating content. In chat, you can attach documents, offerings, web pages, and images directly to the message they support, so the assistant receives the right context for that request. Sent messages keep those references visible, while failed sends restore them for another try. Assistants can reuse an existing image as-is or combine several references when a new composition is needed.
Why it matters: Useful source material was split between different tools, and references could lose their connection to the instruction they were meant to support. Teams spent time finding assets again or explaining which document and image the assistant should use.
Glowtify fits B2B and service businesses
For B2B, service, manufacturing, and non-ecommerce teams
Glowtify now uses broader business language across setup, Business DNA, marketing strategy, and everyday workspace controls. References that assumed every organization ran an online store have been replaced with terms that also fit services, manufacturing, B2B sales, and organizations without checkout flows. The account container is presented consistently as a Workspace, while offerings can describe products or services. Demo content also reflects a Canadian B2B manufacturer, making examples more useful beyond ecommerce.
Why it matters: Store-first wording made service and B2B teams translate the product into their own business model. It could create doubt about whether recommendations, setup questions, and examples were meant for them. That extra uncertainty slowed reviews and made the next practical step harder to choose.
Google Ads Performance Max across Glowtify
For marketers and agencies coordinating Google Ads campaign plans
Performance Max planning is now available across the current Google Ads experience in Glowtify. Teams can include this campaign type when shaping an advertising plan instead of limiting the mix to earlier formats. The same workflow keeps campaign choices and scheduling context together, making it easier to prepare a complete Google Ads program. This release focuses on bringing the already-built Performance Max planning experience into regular customer use, without adding unsupported promises about results.
Why it matters: Teams planning a broader Google Ads mix had to work around a missing campaign option or leave Glowtify to complete the plan. That split made it harder to keep paid-media decisions alongside the rest of the marketing calendar.
More reliable publishing images and previews
For content teams publishing blogs and social posts with branded visuals
Publishing visuals now travel through more dependable paths from creation to the final channel. Shopify blog drafts recover when visibility was never selected, featured images are prepared in a publish-ready format, and WordPress image handling avoids a common authorization failure. Social profile logos, avatars, video thumbnails, and post-performance previews are stored with durable references that continue to load over time. The result is a steadier handoff between what teams see in Glowtify and what appears in publishing and reporting views.
Why it matters: An image could look ready during creation yet fail, disappear, or break later because a draft setting or temporary reference did not survive publishing. Those surprises created rework and made previews harder to trust. That extra uncertainty slowed reviews and made the next practical step harder to choose.
Fewer onboarding dead ends
For new and invited users completing their first Glowtify setup
Onboarding now handles two frustrating return paths without trapping the user. Someone who accepted a workspace invitation before finishing setup can skip the irrelevant store-connection screen, complete the quick name step, and enter the invited workspace. The key-moments step also loads correctly for anonymous users instead of falling into an error page. Together, these changes keep setup moving when a user arrives through an invitation or resumes an unfinished journey.
Why it matters: People could be blocked before reaching the workspace they had been invited to, even though access was already waiting for them. Others encountered a full-page error during a standard onboarding step and had no clear way forward.
Clearer feedback in everyday creation
For marketers reviewing AI actions, calendar content, and email designs
Everyday creation surfaces now give clearer feedback about what Glowtify is doing. Chat stops cleanly after presenting an action card instead of adding a second, duplicate response. Calendar cards show a loading skeleton while media is being generated, then refresh automatically when the real thumbnail is ready. Email creation also warns when a custom font may not be supported by common inboxes, helping teams choose a safer fallback before sending.
Why it matters: Duplicate chat replies made completed actions look uncertain, while blank calendar thumbnails could be mistaken for missing media. Unsupported email fonts could also produce a different design for recipients than the one a creator expected.
