A landing page is going offline. Legal just updated the unsubscribe link. A partner campaign now redirects to a new address. You need to find every email and personalization block that contains the old URL — before the next send goes out with a broken link.

In the Adobe Campaign console, there is no global search across campaigns. acc downloads your entire instance as local files — search for any URL across all deliveries and blocks in seconds, with the search tool you already use.

Preparation

Requirements: acc installed and authenticated. Refer to Getting started.

What will be downloaded:

  • Delivery HTML and text sources as .html and .txt files
  • Personalization blocks as .html and .txt files
  • Options as .xml files
  • JavaScript codes as .js files

Walkthrough

1. Pull your instance

From your project folder:

acc instance pull

To target only the most relevant metadata and reduce pull time:

acc instance pull --metadata nms:delivery,nms:includeView,xtk:option,xtk:javascript

2. Search for the URL

Windows Explorer — right-click the project folder, open in Explorer, and type the URL in the search bar. Results appear across all file types.

VS Code — open the folder and use Ctrl+Shift+F (global search). Results are grouped by file with line-level context, which makes it easier to identify whether the URL is in an <a href>, a src attribute, or a JavaScript variable.

Notepad++ — Search > Find in Files, set the directory to your project root, and enter the URL in the search field.

3. Identify the scope

A URL found in:

  • A delivery file — that specific delivery is affected
  • A personalization block — all deliveries using that block are affected (search for the block’s internal name across deliveries to get the full list)
  • A JavaScript code — the function calling that URL needs to be updated and redeployed
  • An option — update via Administration > Platform > Options

Validation & troubleshooting

No results, but you know the URL exists

Check that the relevant schemas are included in your acc.config.json. Deliveries are not pulled by default unless nms:delivery is declared in the schemas array. Refer to Configuration reference.

Too many results

Narrow the delivery date range with DaysAgo(90) in your configuration, or search within a specific subfolder by opening only that subfolder in VS Code.

URL appears in a personalization block source but not in deliveries

The block is referenced by name in deliveries, not inlined. Search for the block’s internal name (e.g. includeView_unsubscribe) across delivery files to find all affected deliveries.

Going further

Audit hardcoded URLs

A URL that appears directly in a delivery file rather than via a personalization block or option will not update automatically when the URL changes. Any direct match in a .html delivery file is a candidate to be replaced by a shared block or getOption("myUrl").

Track changes over time

Run acc instance pull after updating the URL. Under Git, git diff shows exactly which files changed — confirming the update was applied everywhere. Refer to Improve Code Traceability with acc CLI and Git.