Marketing and design news: September 24, 2026
This week’s marketing and design news calls for practical decisions about campaigns, customer data, and creative production. Six announcements published between September 17 and September 24 deserve a closer look before teams change budgets or workflows.
Pinterest and Metricool bring different perspectives on advertising decisions. Google adds tools for campaign integrations. Adobe addresses both marketing operations and production software. Meta introduces another set of uses for wearable displays.
Our selection focuses on changes with a clear application for businesses, including teams serving Mexico, the United States, and Canada. We separate confirmed announcements from GDS recommendations throughout this edition. Regional access, account eligibility, and rollout timing still need checking before implementation.
We did not add a packaging launch simply to complete a category list. The production and brand implications below apply to packaging teams without presenting an unrelated announcement as packaging news.
TL;DR
- Review campaign scores alongside actual sales, lead quality, and contribution margins.
- Test new advertising integrations in a controlled environment before changing live campaigns.
- Check the September InDesign security bulletin against each production computer’s installed version.
- Treat wearable announcements as research opportunities until availability and business value are clear.
- Give each proposed change an owner, a limited test, and a measurable acceptance condition.
Pinterest adds a campaign setup score
Published September 21. Pinterest introduced a campaign score covering setup, creative mix, and signal strength. Its announcement connects the feature with Performance+ and provides recommendations within campaign creation and editing. This is a platform assessment of campaign configuration, rather than a direct measurement of business profit. Read Pinterest’s announcement.
What this means for a brand
GDS recommendation: use the score to organize questions, then check those questions against commercial results. A campaign can follow platform guidance while promoting a product with weak margins. An attractive dashboard number cannot answer whether customers returned their orders or sales staff accepted the leads.
Before acting on a recommendation, write down the specific problem you want to solve. A homeware retailer might need more qualified product visits. A consulting firm might need fewer irrelevant inquiries. Those goals call for different acceptance criteria, even when both accounts receive similar setup advice.
Ask the creative team to label each proposed variation by its purpose. One asset can explain the product’s scale. Another can answer a delivery concern. A third can show how someone uses it. This makes the creative review more useful than comparing superficial color changes.
Keep a change log that connects each adjustment with its date, cost, and expected effect. Review the destination page at the same time. If the ad promises a delivery option, customers should find that option without searching through unrelated copy.
A sensible first test changes one meaningful variable within an agreed budget. Check completed purchases or accepted leads before expanding the test. Keep an unchanged comparison where the account structure and available volume allow a fair assessment.
Metricool publishes its 2026 social advertising study
Published September 21. Metricool released a study covering 628,969 campaigns from 44,355 advertisers across Meta and TikTok. It compares the first six months of 2025 and 2026. These are aggregated observations from the study sample, not predicted results for an individual advertiser. Read Metricool’s study overview.
How to use a benchmark without turning it into a promise
GDS recommendation: start with your own account’s commercial definition of success. A lower click cost can still produce expensive customers. A higher lead count can create extra work if the sales team rejects most inquiries. Compare completed outcomes before choosing a channel from a headline.
For a business operating across countries, separate each market before drawing conclusions. Language, delivery coverage, purchase value, and sales capacity can change the meaning of a result. Do not apply a global average to a Mexican campaign as if it were a local forecast.
Build a short comparison sheet with spend, qualified outcomes, and the period being measured. Record the campaign objective and attribution window beside the numbers. If those definitions differ, flag the comparison instead of forcing the rows into one ranking.
A useful discussion with an agency starts with a question such as, “Which part of our acquisition process needs testing?” That question leaves room for a creative change, a landing page correction, or a new channel. Moving the full budget immediately would make the diagnosis harder.
For an online store, review our e-commerce marketing guidance alongside your account data. Choose one limited experiment and define its stopping condition. Treat the study as context for that decision, with its sample and timeframe kept visible in the brief.
Google releases Ads API v25.2
Announced September 23. Google’s v25.2 release adds capabilities including competitive percentile data, asset-group tracking fields, and draft generation for moving Smart campaigns toward Performance Max. The update concerns the Ads API used by software integrations. It does not mean every advertiser must change a campaign immediately. Read the September 23 entry in Google’s developer archive.
The operational question comes before the upgrade
GDS recommendation: ask whoever maintains your advertising connection whether these changes solve an existing reporting or workflow problem. An account managed entirely through the standard interface may have no immediate development task. An agency with custom reports should check which integrations actually use the API.
Document the current owner, version, and data destination for each relevant connection. Include the reports that a client sees, not just the systems a developer recognizes. This helps catch a change that works technically but quietly breaks a familiar business report.
For tracking changes, agree on a naming convention before testing the implementation. Campaign names, source labels, and landing page parameters should describe the same activity. A neat technical setup becomes less useful when the sales report groups that traffic under an unrelated label.
Use a test environment or a limited account when available. Compare one known campaign’s output before and after the change. Confirm that the destination URL, reporting labels, and conversion definitions remain intelligible to the people using them.
Keep automatic campaign creation separate from approval to spend. A generated draft still needs someone to review its offer, assets, audience assumptions, and budget. Record that approval explicitly. The practical benefit of a new integration depends on the time it saves without weakening those checks.
Adobe updates Experience Platform connections
Released September 22. Adobe’s Experience Platform notes include automatic token refresh for the Facebook destination and a new Salesforce CRM authentication option rolling out during the week. The release also covers data management and audience tools. Teams should check each feature’s availability in their environment. Read Adobe’s dated release notes.
Check whether the handoff still reaches the right people
GDS recommendation: use this release as a reason to inspect one customer-data handoff from beginning to end. List where information originates, who can access it, and which destination receives it. A connection can appear healthy while sending a field that the receiving team cannot use.
Choose a permitted test record rather than copying a real customer’s information into an informal troubleshooting channel. Confirm the expected field names and values. Record whether the destination accepted the record, when it arrived, and how an operator would notice a failure.
Give ownership of the connection to a role, with a backup person documented. Staff changes should not leave a campaign dependent on an account nobody can maintain. Keep authentication handling within approved tools and avoid placing secrets in shared creative briefs.
For a smaller business without Experience Platform, the same review can be useful without buying new software. Trace a website inquiry into the existing customer-management process. Ask the sales team whether source information survives and whether someone receives an actionable notification.
This is a proposed operational check, not a claim that the release changes your current setup. Complete it with the system owner before replacing credentials or removing an older connection. Compare the observed result with the expected result, then keep the evidence with the change record.
Adobe issues an InDesign security update
Published September 22. Adobe’s InDesign bulletin lists affected versions and recommends updates to 21.6 or 20.5.5, depending on the installed branch. It describes application denial-of-service issues and reports no known exploitation in the wild. Teams should use the bulletin to identify their applicable update. Read bulletin APSB26-145.
Protect the delivery process while updating
GDS recommendation: treat this as a production task with a named owner. Record the installed version on each relevant workstation. Include freelancers or suppliers who exchange editable files when your contract and workflow permit that check. Do not assume everyone uses the same release.
Before changing a production environment, preserve the project files and their linked assets. Select a representative document for a controlled opening and export test. Compare its typography, image links, and output with the approved reference. This is a quality check, not a reason to ignore the security notice.
A packaging or print team can add the check to an existing preflight handoff. Identify who approves the final export and where the approved file lives. Keep that approved output distinct from a working file saved during testing, so a supplier does not receive the wrong version.
For a campaign close to delivery, coordinate timing with the production owner and IT support. A rushed update without a recovery plan can complicate an already tight schedule. A documented update with a brief test gives the team a clearer basis for proceeding.
Our packaging design brief guide explains the information teams should agree before artwork and printing. Add software and delivery ownership to that conversation where relevant. Record the update result rather than assuming a successful installation proves every document is ready for production.
Meta expands Ray-Ban Display features and markets
Announced September 23. Meta presented new navigation functions, a personalized hologram for calls, and an Explore app for Ray-Ban Display. It also announced expansion to five markets, including Canada. Some navigation functions are scheduled for later in the month. This announcement does not establish availability in Mexico. Read Meta’s announcement.
Explore a customer task before funding an experience
GDS interpretation: these developments give design teams a reason to study short, contextual interactions. They do not establish demand for a particular brand experience. Begin with a customer task that already exists, such as finding an entrance, understanding a product, or getting support.
Write that task as a short scenario with a clear ending. A visitor arriving at a store needs the correct entrance and opening hours. A customer comparing products needs understandable differences. A decorative effect that does not help complete the task belongs lower on the priority list.
Test the wording first on an ordinary phone or printed prototype. Ask someone unfamiliar with the project to explain what they would do next. Confusing instructions will remain confusing on a smaller display, even when the presentation looks impressive during an internal demonstration.
For businesses in Canada, check actual device and feature availability before arranging a trial. For teams in Mexico, keep the exercise at the research stage until the relevant access is confirmed. Do not promote a local experience on the strength of an announcement about another market.
Set aside questions about consent, public spaces, and support responsibilities for qualified review before any deployment. A useful prototype should reveal those questions early. Evaluate whether the proposed interaction saves effort for customers, and document what remains uncertain before requesting a production budget.
A focused review for your team
Decide what needs attention this week
Start with work that affects an existing commitment. A production update may matter more than an experimental channel when a print deadline is near. A broken inquiry handoff may deserve attention before another campaign launches. Rank tasks by the consequence of leaving them unresolved.
Assign one owner to each selected action and agree on what completion looks like. “Review advertising” is too broad. “Compare accepted leads from two campaigns using the same reporting period” gives the team a specific result to deliver.
Keep the source date beside each task. A research report can remain useful after launch week, while a limited rollout may change quickly. Recheck availability at implementation time rather than treating this edition as permanent product documentation.
Give each test a useful record
A one-page test record should explain the customer problem, the proposed change, and the evidence required. Add the responsible person, review date, and spending limit. Include an unchanged reference when a comparison is practical.
Separate observations from explanations. “The form received fewer submissions” is an observation. “The new message discouraged unsuitable prospects” is a hypothesis until lead quality supports it. This distinction helps prevent a promising narrative from replacing a proper review.
When a result is unclear, record the uncertainty and the next check. Small samples, changing offers, and different sales follow-up can complicate a comparison. A useful decision can be to gather better information before committing more money.
Connect the news with your brand plan
Use a brand audit before a rebrand when campaign changes expose inconsistent promises or visual rules. A new tool will not resolve uncertainty about who the business serves or what customers should understand.
Bring the selected actions into your existing marketing and design planning. Our GDS services cover related brand and digital work. If you need help defining a focused project, contact the studio with the business problem and the evidence already available.
This edition was checked on September 24, 2026. Source dates identify the announcements or releases, while the suggested tests are GDS editorial recommendations. No campaign results or customer gains are claimed for these proposals.
