Globax Intelligence
Globax 资讯
聚合平台政策、出海运营、海外推广和 AI 工具趋势，把外部资讯沉淀为可执行的选题、指南与工具线索。
4第 4 页继续浏览统一资讯流中的历史内容。
Feed
全部资讯
采集新闻和站内文章统一按最新时间排列。
OPAI 采集OpenAI appoints Dali Rajic as Chief Revenue OfficerOpenAI appoints Dali Rajic as Chief Revenue Officer to lead its global revenue organization and help businesses realize the full value of AI.原文OpenAI News2026-08-13OPAI 采集From assistance to execution: How enterprises put AI to workOpenAI research reveals how enterprises are adopting agentic AI, using ChatGPT and Codex, and how frontier firms are pulling ahead in AI adoption.原文OpenAI News2026-08-12OPAI 采集How RingCentral builds AI-native work from engineering to opsSee how RingCentral uses ChatGPT Work and Codex to accelerate AI product development and centralize operational intelligence across engineering and operations.原文OpenAI News2026-08-12HAAI 采集A Preview of DuckDB v2.0Hacker News 热门讨论，当前分数 252。原文Hacker News Top Stories2026-08-17HAAI 采集AI-Generated GitHub Copilot “Autofix” Allowed Compromise of Snowflake's JiraHacker News 热门讨论，当前分数 129。原文Hacker News Top Stories2026-08-17HAAI 采集Launch HN: Speko (YC S26) – OpenRouter for Voice AIHacker News 热门讨论，当前分数 35。原文Hacker News Top Stories2026-08-17HAAI 采集How to disable or avoid intrusive AIHacker News 热门讨论，当前分数 92。原文Hacker News Top Stories2026-08-17GO跨境电商采集Google Ads language targeting changes starting September 2026We're making changes to language targeting for Search, AI Max for Search, and Performance Max campaigns in Google Ads, simplifying campaign management while maintaining a high-quality ad experience. Effective late September 2026: For Search and AI Max for Search campaigns, the campaign-level language targeting setting will be removed. Search ads will automatically match based on the language of your ads. For Performance Max campaigns, the way language targeting is used will be updated: On Google Search: The campaign-level language setting will no longer be used for ads shown on Google Search. Language matching will function the same as Search campaigns, using the language of your ads. On other channels (like YouTube, Display, Discover, Gmail): The campaign-level language setting you select will continue to be used to guide who sees your ads. In cases where multiple eligible campaigns exist within your account, AI-based ad group prioritization will select the most relevant ad language. Historically, the language criterion in the Google Ads API allowed you to manually specify target languages for your campaigns. These language criteria will still be returned when querying even though they are not used for targeting. Any mutates to add or update Search campaign CampaignCriterion.language will result in a ContextError.OPERATION_NOT_PERMITTED_FOR_CONTEXT error. For Performance Max campaigns, there will be no error as language targeting may be used on other channels. What should I change for the Google Ads API? While existing Search and AI Max for Search campaigns will continue to operate without disruption (as their language settings will not apply), we recommend the following code updates: Stop setting language criteria : For new Search campaigns: Stop including language criteria when creating or updating Search campaigns when sending Google Ads API requests. For existing Search campaigns: You may optionally remove existing language criteria from your Search campaigns for cleanliness, though it is not strictly required as they will not apply. Focus on Ad and Landing Page Language: Ensure your ad creatives and landing pages are clearly structured in the intended languages. Search ads will primarily use these signals, alongside user language preferences, for matching. Where can I get support? For technical support issues, please reach out to us using the support form . If you have any questions or want to discuss this post, please reach out to us on our “Google Advertising and Measurement Community” Discord server . - Dora Sun - Google Ads API Team原文Google Ads Developer Blog2026-08-14GO跨境电商采集Migrate Campaign-level Broad Match and Automatically Created Assets to AI MaxThe legacy automigrations are divided into two separate phases: Phase 1 ( Campaign-level Broad Match and Automatically Created Assets ), which starts September 1, 2026. Phase 2 (Dynamic Search Ads), which has been rescheduled to February 2027. 1. Campaign broad and ACA auto-migration: September 1 – September 30, 2026 On September 1, 2026 , Google Ads will begin automatically upgrading Search campaigns using Campaign-level Broad Match (CB) or standalone Automatically Created Assets (ACA) to AI Max. The migration job will roll out progressively throughout the month. To find the campaigns that have been migrated at any point during the month: SELECT campaign.id, campaign.name, campaign.aca_migration_date_time, campaign.broad_match_migration_date_time FROM campaign WHERE campaign.aca_migration_date_time > '1970-01-01 00:00:00' AND campaign.broad_match_migration_date_time > '1970-01-01 00:00:00' Default migrated configurations To support campaign management continuity and minimize performance volatility, campaigns will be migrated in-place to equivalent AI Max settings. Campaign-Level Broad Match (CB): Text Customization (TC): OPT_OUT ( OFF ) Final URL Expansion (FUE): OPT_OUT ( OFF ) Search Term Matching (STM): true ( ON ) by default Brand Lists: Existing brand inclusions and exclusions are preserved and moved into the new setup in-place. Standalone Automatically Created Assets (ACA): Text Customization (TC): OPT_IN ( ON ) by default Final URL Expansion (FUE): OPT_OUT ( OFF ) Search Term Matching (STM): true ( ON ) by default 2. API creation blocks and legacy cleanup To prevent the creation of new legacy structures ahead of the auto-migration, strict enforcement blocks are now in place across the developer surfaces: Legacy creation end of life (August 3, 2026): Creating new Campaign-level Broad Match configurations or legacy Automatically Created Assets (ACA) is now blocked across the UI, Google Ads Editor, and all versions of the API. 3. API versioning lifecycle and support grace period How you manage these features depends on the API version your integration targets: New API versions (post-September 1, 2026) Any new versions of the Google Ads API released after September 1, 2026, will completely remove the legacy entities used to create or manage: Campaign-level Broad Match settings Automatically Created Assets Older API versions (grace period) Active support: Previously released API versions that are currently active will temporarily continue to support legacy ACA and Broad Match settings. Sunset timeline: You can continue to edit and manage these legacy setups through older API versions until those specific versions reach their standard scheduled sunset (typically one year after their introduction, around September 2027 ). At that point, all remaining legacy entities will be permanently removed. 4. Dynamic Search Ads automigration February 2027 Your active legacy DSA campaigns are excluded from the September auto-migrations and will continue to serve as normal. However, prepare for the upcoming DSA timeline: September 2026: Google will launch in-account pre-migration banners in the UI to warn unmigrated advertisers of the upcoming transition and encourage voluntary one-click upgrades by selecting “Upgrade Your Dynamic Search Ads (DSAs) to AI Max” under Campaign Settings | Dynamic Search Ads setting. January 15, 2027: Official MSA reminder notification will be sent to all impacted accounts. February 1–28, 2027: Automigration begins. The ability to create new DSA ad groups will be permanently removed, and unmigrated DSA campaigns will automatically upgrade to standard Search ad groups with AI Max enabled. Developer action plan Audit your integration: Identify any scripts, external tools, or client libraries still attempting to create or edit campaign-level broad match settings or legacy ACA. Move to standard entities: Begin updating your campaign construction workflows to use standard Search campaigns with the AI Max settings bundle (Uber Toggle, Text Customization, and Search Term Matching). Handle grandfathered read-only entities: Be prepared to handle API error codes if your integration attempts to modify (rather than pause or delete) legacy Expanded Dynamic Search ads (eDSAs) or criteria once they transition to standard ad groups. Bob Hancock, Google Ads API Team原文Google Ads Developer Blog2026-08-12GO跨境电商采集Query report data with the Campaign Manager 360 APIYou can now use the reportData.query endpoint in the Campaign Manager 360 API to synchronously query your campaign performance data and retrieve structured JSON data directly in the response. The new reportData.query endpoint offers a simplified option for report data retrieval compared to the standard reporting API workflow : Queries run synchronously with a 60-second execution limit, making this endpoint ideal for real-time dashboards and ad-hoc data explorations. Report data is returned as structured JSON directly in the HTTP response, which eliminates file management overhead. You no longer need to create a preconfigured Report resource to fetch data, as you can specify your dimensions, metrics, and filters directly in the request body. The existing Reports service is still recommended for retrieval of large datasets, scheduled jobs, or applications that rely on downloadable report files (CSV or Excel). This service requires multiple steps: developers must create and manage Report configurations , trigger a run of the report , poll for status updates, and download the report file . Get Started --> Get Started Review the Query Report Data guide to learn more about request parameters, pagination, and best practices. Compare reporting approaches on the Reporting Overview . Check out the reportData.query REST reference documentation. If you have any questions or need technical support, please reach out to Campaign Manager 360 API Support . - Lindsey Volta, on behalf of the Campaign Manager 360 API Team原文Google Ads Developer Blog2026-08-12GO跨境电商采集Google Ads API pilot: Secure API Access to your Manager AccountsThe Google Ads API is piloting a security feature designed for securing API access to Google Ads manager accounts. We are seeking developers who would like to participate in this pilot project and provide us with feedback. What are we offering? The new pilot program protects accounts under a Google Ads manager hierarchy by restricting access to sensitive API methods such as account management, user management, and billing API calls to a pre-approved allowlist of Google Cloud projects. This happens in the following phases: You sign up for the pilot program, and share the customer ID of your top-level Google Ads manager account. Google performs an audit of the API activity of all the accounts under the Google Ads manager account to identify the list of applications and their Google Cloud project numbers. Google works with you to establish an allowlist of approved applications and projects as a new mechanism for controlling API access to sensitive methods. After the Google Ads manager account is secured, any unapproved application that tries to make sensitive API calls to any account under the protected manager account will fail. This security measure provides benefits: Enhanced Security: Lowers the risk of account takeovers by malicious applications by helping to restrict access so that only verified tools can perform sensitive operations, even if your credentials are compromised. Improved Visibility: Provides advertisers with a clear and concise view of exactly which applications have access to their advertising data and are performing sensitive actions on their accounts. How do I join this program? To participate in this program, express your interest by filling out the application form . You should provide your contact email address and the customer ID of the top-level Google Ads manager account that you want to secure. If Google selects your account for participation in the pilot program, then we will reach out to you using the email address you provided, and list the next steps required to secure the accounts under your Google Ads manager account under this pilot program. How do I authorize new applications under this program? If you are participating in this program and want to allowlist a new application to make sensitive API calls to the accounts under the protected Google Ads manager account, let us know the Google Cloud project number of the application by filling out the form . If you don’t have these details, you can reach out to your application developer for this information. Google will make the necessary changes within 10 business days and let you know. How do I stop participating in this program? If you are participating in this program and want to stop your participation, contact Google Ads API support using the same email address you used when signing up for this program and let us know the reason why you are opting out of this program. Google will make the necessary changes within 10 business days and let you know. What happens if I unlink an account from a protected top-level manager account? If you unlink an account from the hierarchy under a protected top-level manager account the account loses the API protection offered under this program. What happens if I link a new account under a protected top-level manager account? If you link an account under the hierarchy of a protected top-level manager account, the newly linked account will inherit the protection from the top-level manager account. In addition, if a newly linked account has existing applications, but those applications are not already authorized by the manager account, they might fail and may need to be authorized . If you have more questions about this pilot program, you can contact support . - Anash P. Oommen , Google Ads API Team原文Google Ads Developer Blog2026-08-03GO跨境电商采集Data Manager API updates: RemoveAllAudienceMembers method, ingestion field warnings, expanded address dataThe latest release of the Data Manager API introduces features that simplify audience management, enhance ingestion workflows with field-level warnings, and enable more granular user-provided data for Google Analytics. Remove all audience members Use the new RemoveAllAudienceMembers method to clear all members from specified user lists in a single operation. The optional removeAsOfTime parameter lets you target only those members added before a specific timestamp. This is particularly useful when you need to perform a full refresh (or "replace all") of your audience data, allowing you to clear the existing list and populate it with a new set of users. Ingestion field warnings Data Manager API ingestion responses now include detailed field-level warnings for validation issues on optional fields. If the API detects validation issues with optional fields, your ingestion request will succeed and the rest of your ingestion data will still be processed. Validation failures for required fields will continue to fail the entire request following the fast-fail model . If any optional field you provide is invalid, the response from IngestEventsRequest or IngestAudienceMembersRequest includes a field_warnings field with a list of FieldWarning objects. Each warning provides a specific reason ( WarningReason ), a descriptive message, and the location of the field in the request where the issue occurred. Additional address data for Google Analytics events You can now provide additional user address information when ingesting events to Google Analytics destinations. Along with the given_name , family_name , region_code , and postal_code fields, AddressInfo resource now supports: address_line (street address) city administrative_area (state or province) Also, you can now use the existing user-provided data ( user_data ) field to meet the Identifiers requirement for multi-source events sent to web data streams . This gives you another option when you don't have the ad_identifiers.gclid , user_id , or client_id for a multi-source event. Get started Learn how to implement the new RemoveAllAudienceMembers method for your workflow: Google Ads Customer Match Display & Video 360 Customer Match See the Ingestion warnings section of the Understand API errors guide to learn how to check your responses for warnings. Start sending events to Google Analytics with the Data Manager API: Send recommended and custom events Upgrade from Measurement Protocol Recommended events reference Build faster with AI agent skills: We recently introduced new Data Manager API agent skills to help you speed up your integrations. Explore the new skills in the Google Skills GitHub repository to get more accurate, efficient guidance directly within your AI-assisted coding environment. If you have any questions or want to discuss this post, please reach out to us on our "Google Advertising and Measurement Community" Discord server . You can also contact us through the support page if you have an issue or need help with the API. If you're interested in becoming a data partner, please fill out the Partner Interest Form . - Lindsey Volta, on behalf of the Data Manager API Team原文Google Ads Developer Blog2026-07-30GO跨境电商采集Launching Structured Data Files v10.1Today we’re announcing the general availability of Structured Data Files v10.1 . All users can now use v10.1 when downloading and uploading SDFs in the Display & Video 360 interface. SDF v10.1 includes the following changes: The ability to specify whether a YouTube video asset identified in a Video ID or Related Videos column contains content that was created or edited with AI. Read more about AI labeling in ads using SDF . Support for digital out-of-home Insertion Order and Line Item resources. New columns identifying the Display & Video 360 creatives in use by ads and ad groups. Updated options for the Inventory Mode column of Line Item files. See the release notes for the details on the changes in v10.1. If you are using a version previous to v10, it is now deprecated. Follow the instructions in our migration guide to migrate to v10 from any available version. If you have any questions or want to discuss this post, please reach out to us on our “Google Advertising and Measurement Community” Discord server . - Trevor Mulchay, Display & Video 360 API Team原文Google Ads Developer Blog2026-07-29GO跨境电商采集Support for AI Content Labeling using the Campaign Manager and Display & Video 360 APIsAs the use of AI becomes more prevalent, transparency is key. In the last week, we have launched updates in both the Campaign Manager 360 API and Display & Video 360 API that add new optional fields to resources in both APIs, which allow you to label a creative or creative asset as having been created or edited with AI. Labels will be applied to ads with such assets serving in regions with local AI labeling regulations. As of today, those regions are the European Union (EU), India, and New York state. Read more about AI content labeling at the Campaign Manager 360 Help Center and Display & Video 360 Help Center . In both APIs, this configuration is set using the optional syntheticContentAttestationStatus field in relevant resources. Setting this field to IS_SYNTHETIC applies the label in the regions listed above, while setting it to NOT_SYNTHETIC confirms that the content does not require a label. You can also leave the field unset. A label will not be applied if the field is left unset. However, once the field is set for a resource, it can’t be unset and may only be updated to be either IS_SYNTHETIC or NOT_SYNTHETIC . If you have any questions regarding the Campaign Manager API, contact Campaign Manager 360 API support . If you have any questions regarding Display & Video 360 API or Structured Data Files, or want to discuss this post, reach out to us on the #display-video-360-api or #structured-data-files channels on Discord. Using Campaign Manager 360 API In the Campaign Manager 360 API, this configuration is set in Creative resources. The syntheticContentAttestationStatus field can be set at resource creation using creatives.insert or updated for existing resources using creatives.patch and creatives.update . For more information about how synthetic content labels work in Campaign Manager 360 API, see our guide page . Using Display & Video 360 API In the Display & Video 360 API, this configuration is set in Creative and AdAsset resources. The syntheticContentAttestationStatus field can be set at resource creation using advertisers.creatives.create , advertisers.adAssets.create , advertisers.adAssets.bulkCreate and advertisers.adAssets.upload . It can also be set or updated for existing resources using advertisers.creatives.patch and advertisers.adAssets.patch . For more information about how synthetic content labels work in Display & Video 360 API, see our guide page . Using Display & Video 360 Structured Data Files Starting in Structured Data Files (SDF) v10.1, which is scheduled to launch in the coming weeks, you will be able to add labels when using YouTube videos as video assets in Ad files or as related videos in Line Item files. More details on this implementation will be provided in the upcoming launch announcement of SDF v10.1 and the associated reference documentation. - Trevor Mulchay, Display & Video 360 API Team原文Google Ads Developer Blog2026-07-28GO跨境电商采集Passkey authentication requirement for the Google Ads APIAs part of improving security for Google Ads accounts, the Google Ads API will start requiring passkeys for Google Ads API users . This is part of a broader change in Google Ads that requires passkeys to authorize sensitive actions in your Google Ads account. These important security updates will start rolling out from August 5, 2026 , and will be enabled for all users over the next few weeks. What is changing? Once this change goes live, users following the user authentication workflow to generate new OAuth 2.0 refresh tokens for Google Ads API will always be required to authenticate using a passkey. If you haven't created a passkey, you will be asked to create one, and use it to complete the authentication workflow. Other forms of authentication that use password alone, or 2-factor authentication (2FA) mechanisms such as Time-based One-Time Password ( TOTP ) or SMS-based codes will be disallowed. What action do I need to take? You may be affected by this change, depending on the authentication workflow that your application uses. Service account workflow : Service account workflows are not affected by this change, so no action is required. We strongly recommend using service account workflow for applications that require automated or offline workflows. User authentication workflow : If your app generates OAuth 2.0 refresh tokens for users, you will be affected as follows: Existing OAuth refresh tokens are not affected by this change. They will continue to work as usual, and you won’t be prompted for reauthorization when obtaining OAuth access tokens. New users will be challenged to authorize with a passkey. A 7-day security delay may apply before a new passkey becomes trusted and operational. To ensure it’s ready for use when you need it, create your passkey at your earliest convenience. To set up a passkey, Go to g.co/passkeys . Click Create a Passkey to sign in to the Security Key Manager. Create a passkey by following the steps provided by your device. What other platforms are affected by this change? Google products that use Google Ads API, such as Google Ads Editor , Google Ads scripts , BigQuery Data Transfer Service or Data Studio to manage Google Ads will also start requiring a passkey-based authentication. If you don’t have passkeys enabled, you will be prompted to add one. To learn more about how to set up passkeys, visit the Help Center . If you encounter issues, you can contact support . For any questions or further discussion regarding this update, please connect with us on the "Google Advertising and Measurement Community" Discord server . - Anash P. Oommen , Google Ads API Team原文Google Ads Developer Blog2026-07-27SH跨境电商采集Shop Campaigns performance data now available via ShopifyQLThe shop_campaign_insights schema is now available in the ShopifyQL . Analytics and reporting apps can query Shop Campaigns performance data on behalf of authorized merchants using the existing shopifyqlQuery field with read_reports scope. Available data Campaign-level and segment-level metrics including ad spend, sales, orders, ROAS, average order value, and average customer acquisition cost. Data is available by campaign name, customer segment, and time dimensions from hourly to yearly in the merchant's shop timezone. How to get started Query shop_campaign_insights using the same shopifyqlQuery field you use for other ShopifyQL schemas. No new scopes or integration work required if you already query ShopifyQL. Schema reference: shop_campaign_insights Building with ShopifyQL ShopifyQL API reference Also new: Analytics Web Components let you embed Shop Campaigns metrics directly in your app UI using with no data storage required. The Analytics Annotations API lets you create annotations on merchant analytics charts (e.g., "campaign started," "budget changed").原文Shopify Changelog2026-08-10SH跨境电商采集Standard storefront events and actions now support cart attributesThe updateCart standard action now updates cart attributes, and a new shopify:cart:attributes-update event fires whenever an attributes update is initiated. Before this, changing an attribute meant calling the Storefront API yourself, and nothing told your app when one changed. The action now handles attributes like any other cart update, and the event fires whether your app, the theme, or another app made the change. It carries the full new set of attributes and a promise for the result, so you can update your UI right away and roll it back if the cart declines the change. Learn more in the event reference and the updated updateCart reference .原文Shopify Changelog2026-08-06SH跨境电商采集Draft order and transfer/shipment inventory is moving from reserved to committedWe're consolidating how in-progress inventory holds are represented. Inventory that was previously tracked under the reserved quantity state for draft orders, transfers, and shipments is being moved to the committed quantity state. This change aligns these holds with how order inventory is already represented, so that committed reflects all inventory that is spoken for but not yet fulfilled. What's changing For draft orders, transfers, and shipments, quantities that previously appeared under reserved will now appear under committed . This is a one-time data migration that applies only to active draft orders and open transfers/shipments that are still holding inventory when the change runs. Completed, cancelled, or already-released holds are not modified, because they no longer hold reserved inventory. What's not changing available and on_hand quantities are unaffected. Total inventory is unchanged, and quantities are only moving between two “unavailable” buckets. Both reserved and committed remain valid, queryable quantity names. No fields are removed or renamed. Sellable inventory ( available ) is not affected, so this does not change what buyers can purchase. What you may need to do If your app reads InventoryLevel.quantities(names: ["reserved"]) , expect reserved values to decrease for affected shops, with a corresponding increase in committed . If you currently rely on reserved to detect draft-order or transfer/shipment holds specifically, you should read committed instead going forward. No code changes are required to keep existing queries working; only the values shift between the two states. Reporting note Merchants using inventory adjustment reports (for example, reports that break out adjustments by inventory state) will see reserved values migrate to committed , plus a one-time correction entry when the migration runs. This correction only covers active draft orders and open transfers/shipments at the time of migration. on_hand and available totals are unchanged, and historical data before the migration remains as-is. Related docs InventoryLevel — the quantities(names: [...]) field: https://shopify.dev/docs/api/admin-graphql/latest/objects/InventoryLevel InventoryQuantity — the object returned per name: https://shopify.dev/docs/api/admin-graphql/latest/objects/InventoryQuantity原文Shopify Changelog2026-08-05SH跨境电商采集WebMCP support for Liquid and Hydrogen storefrontsOnline stores now expose WebMCP tools that AI agents can call. Agents can search your catalog, manage the shopper's cart, and go to checkout on the shopper's behalf, all in the tab they're looking at. The tools work through WebMCP , a proposed web standard that lets a page register tools with the browser. Without it, agents have to read every page's code and simulate clicks, which is slow and error-prone. The tools are live today on every Liquid storefront and on the Hydrogen developer preview . There's nothing to install or configure. Everything an agent does happens on the shopper's live session. Cart tools call the same standard storefront actions that apps use, so if your theme opens a cart drawer on updates, agents trigger it too. Here's what agents can call: Catalog: search_catalog , browse_store , get_product , and show_variant Cart: get_cart , update_cart , and cancel_cart Checkout and orders: proceed_to_checkout and manage_orders Other content: search_shop_policies_and_faqs WebMCP is still an emerging standard, and agent support is currently limited to Chromium-based browsers through an origin trial . Shopify is helping shape the specification alongside Google and Microsoft. Learn more in the WebMCP docs . If you're building your own agent, see Build commerce agents .原文Shopify Changelog2026-08-05SH跨境电商采集Oxygen is now available on development storesYou can now deploy Hydrogen storefronts to Oxygen from dev stores . Previously, Oxygen hosting required a paid plan. Note that development stores don't include public environments, so deployment URLs always require a store login. Learn more about supported plans .原文Shopify Changelog2026-08-03