Control the visibility of the extension attribution on the New Tab page
Verified with Google Chrome — updated on July 10, 2026 Supported on: Microsoft Windows 7 or later
Path in the GPO console
Computer Configuration\Administrative Templates\Google\Google Chrome User Configuration\Administrative Templates\Google\Google Chrome Registry
Software\Policies\Google\Chrome Software\Policies\Google\Chrome - Value name:
-
NTPFooterExtensionAttributionEnabledREG_DWORD - Enabled:
1- Disabled:
0
Other deployment channels
./Device/Vendor/MSFT/Policy/Config/Chrome~Policy~googlechrome~Miscellaneous/NTPFooterExtensionAttributionEnabled OMA-URI published by Google. It requires the Chrome ADMX templates (chrome.admx, google.admx) to be imported in Intune first.
- Google Chrome (Linux) — since version 138
- Google Chrome (Mac) — since version 138
- Google Chrome (Windows) — since version 138
- Google ChromeOS (Google ChromeOS) — since version 138
Source: official Chrome policy list, version 157.0.8103.79 Chrome Enterprise policy page
Description
This policy determines whether an attribution to the extension modifying the New Tab Page (NTP) is displayed in the NTP's footer. By default, if an extension has overridden the standard NTP, a message attributing this change to the specific extension will appear in the footer. This attribution typically includes a link to the relevant extension in the Chrome Web Store. If this policy is left unset or set to true, the extension attribution will be visible on the NTP footer when an extension is controlling the NTP. If this policy is set to false, the attribution to the extension in the NTP footer will be suppressed.
Export Builder
BETAConfigure the state, scope and options, then generate .reg, PowerShell, Intune and SCCM outputs — or add the setting to a multi-setting collection.
These exports write the registry — this is not a managed GPO. ⓘ
Applying both scopes creates an ambiguous configuration (computer takes precedence over user). Only do this intentionally.
.reg file
Windows Registry Editor Version 5.00
; Exported from gporais.com
; Policy: Control the visibility of the extension attribution on the New Tab page
; State: Enabled
; Scope: Computer (HKLM)
; Supported on: Microsoft Windows 7 or later
[HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome]
"NTPFooterExtensionAttributionEnabled"=dword:00000001 More formats (PowerShell, Intune, SCCM)
PowerShell
# Exported from gporais.com
# Policy: Control the visibility of the extension attribution on the New Tab page
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Windows 7 or later
$path = 'HKLM:\Software\Policies\Google\Chrome'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'NTPFooterExtensionAttributionEnabled' -Value 1 -Type DWord Intune XML
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/Chrome~Policy~googlechrome~Miscellaneous/NTPFooterExtensionAttributionEnabled
Data type: String
Value:
<enabled/> Intune Remediation
# === Detection script ===
# Exported from gporais.com
# Policy: Control the visibility of the extension attribution on the New Tab page
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Windows 7 or later
function Test-RegistryValue {
param(
[Parameter(Mandatory = $true)][string]$Path,
[Parameter(Mandatory = $true)][string]$Name,
[object]$Expected,
[ValidateSet('String', 'DWord', 'MultiString')][string]$Kind = 'String',
[switch]$Absent
)
try {
$item = Get-ItemProperty -LiteralPath $Path -Name $Name -ErrorAction Stop
} catch {
return $Absent.IsPresent
}
if ($Absent.IsPresent) { return $false }
$actual = $item.$Name
if ($Kind -eq 'DWord') { return ([int64]$actual) -eq ([int64]$Expected) }
if ($Kind -eq 'MultiString') {
$actualValues = @($actual)
$expectedValues = @($Expected)
if ($actualValues.Count -ne $expectedValues.Count) { return $false }
for ($i = 0; $i -lt $expectedValues.Count; $i++) {
if ([string]$actualValues[$i] -ne [string]$expectedValues[$i]) { return $false }
}
return $true
}
return [string]$actual -eq [string]$Expected
}
$checks = @(
(Test-RegistryValue -Path 'HKLM:\Software\Policies\Google\Chrome' -Name 'NTPFooterExtensionAttributionEnabled' -Expected 1 -Kind DWord)
)
if ($checks -notcontains $false) {
Write-Output 'Compliant'
exit 0
}
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: Control the visibility of the extension attribution on the New Tab page
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Windows 7 or later
$path = 'HKLM:\Software\Policies\Google\Chrome'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'NTPFooterExtensionAttributionEnabled' -Value 1 -Type DWord SCCM scripts
# Exported from gporais.com
# Policy: Control the visibility of the extension attribution on the New Tab page
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Windows 7 or later
# SCCM Configuration Item guidance:
# Create a Configuration Item of type "Setting: Script".
# Discovery script: use the Detection script below.
# Remediation script: use the Remediation script below.
# Compliance rule: the Discovery script output equals 'Compliant'.
# === Detection script ===
# Exported from gporais.com
# Policy: Control the visibility of the extension attribution on the New Tab page
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Windows 7 or later
function Test-RegistryValue {
param(
[Parameter(Mandatory = $true)][string]$Path,
[Parameter(Mandatory = $true)][string]$Name,
[object]$Expected,
[ValidateSet('String', 'DWord', 'MultiString')][string]$Kind = 'String',
[switch]$Absent
)
try {
$item = Get-ItemProperty -LiteralPath $Path -Name $Name -ErrorAction Stop
} catch {
return $Absent.IsPresent
}
if ($Absent.IsPresent) { return $false }
$actual = $item.$Name
if ($Kind -eq 'DWord') { return ([int64]$actual) -eq ([int64]$Expected) }
if ($Kind -eq 'MultiString') {
$actualValues = @($actual)
$expectedValues = @($Expected)
if ($actualValues.Count -ne $expectedValues.Count) { return $false }
for ($i = 0; $i -lt $expectedValues.Count; $i++) {
if ([string]$actualValues[$i] -ne [string]$expectedValues[$i]) { return $false }
}
return $true
}
return [string]$actual -eq [string]$Expected
}
$checks = @(
(Test-RegistryValue -Path 'HKLM:\Software\Policies\Google\Chrome' -Name 'NTPFooterExtensionAttributionEnabled' -Expected 1 -Kind DWord)
)
if ($checks -notcontains $false) {
Write-Output 'Compliant'
exit 0
}
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: Control the visibility of the extension attribution on the New Tab page
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Windows 7 or later
$path = 'HKLM:\Software\Policies\Google\Chrome'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'NTPFooterExtensionAttributionEnabled' -Value 1 -Type DWord Building a multi-setting collection? Add this setting and generate combined .reg / PowerShell / GPO scripts.