> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.method.security/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.method.security/_mcp/server. # Start a new Campaign > Deploy a Package against an Environment to start populating the Targeting funnel. A Campaign wires together an Environment, a scan schedule, and one or more Targeting Packages. The Campaign wizard walks you through six steps: **Environment**, **Input data**, **Intel & No Strike**, **Scan setup**, **Targeting**, and **Review**. For background on Campaigns and the Targeting funnel, see [Targeting](/platform/core-platform/targeting). --- ## Create a Campaign #### Open the Campaign wizard From the Targeting application, click **New Campaign** in the top-right corner. This opens the Campaign wizard. #### Select an Environment Choose where the Campaign runs. Pick an existing Environment from the list or create a new one inline by entering a name. ![New Campaign wizard on step 1 of 6, showing a searchable list of existing environments and a New environment form at the bottom where you enter a name](/_fern-img/f6873fa228a3a4115ca2df8915955f2e86a9166a9ff5d4284a63c3e7e7d3b8ef.webp) Campaigns run on an Environment. You can determine which scans, Agents, and Policies apply to this Environment. If you create a new Environment here, you seed it with input data in the next step. For a full walkthrough of Environment settings, see [Create a new Environment](/guides/platform-setup/create-a-new-environment). #### Add input data Seed the assets in scope for this Campaign. These become the Object Sets for scanning in Automator. These produce additional Object Sets for use in the Targeting workflow. ![New Campaign wizard on step 2 of 6 showing the Input data screen. The Add input data section has Critical Domains and CIDR Ranges tabs. A Critical Domains field shows example.com entered.](/_fern-img/2525483743e6d579232cda7b00794bf9ac1300a94ac016a42fed8c99a54e5f5b.webp) * **Critical Domains**: Organizational domains for this Environment (e.g. `example.com` or `mail.example.com`). * **CIDR Ranges**: IP ranges to include in network discovery in standard CIDR format (e.g. `10.0.0.0/24`). #### Set up Intelligence and No Strike List Give Method context to work from and protect the Objects that must stay off-limits. Both sections are optional. ![New Campaign wizard on step 3 of 6 showing the Intelligence and No Strike List screen. The Intelligence section has a PDF upload area. The No Strike List section shows an Add to No-Strike List form with Individual Objects and Filter-Based tabs, with Filter Name and Filter Definition fields.](/_fern-img/0ab7eaa33ac3f5775fd0898ad2bdc1c284b64f3018b684b38909343834ec70a2.webp) **Intelligence** Upload PDFs under **Environment Intelligence** to give Agents documentation and context about this environment. Agents use this material when reasoning about Targets. **No Strike List** Add Protection Rules to keep Objects off-limits for all automated actions in this Campaign. You can protect Objects two ways: * **Individual Objects**: select specific Objects by name * **Filter-Based**: define a query that matches a class of Objects Filter-based rules are the more scalable option. Common examples: ![No Strike List Protection Rules showing a filter-based rule named Personally Identifiable Information, scoped to the Demo Environment with a Property Search on Files, File Name, Contains PII, and a No Strike List Preview section](/_fern-img/239d753beebc0ef14587c6e5f71f1f4d3df98a07294e59eb85f113c1039592de.webp) ![No Strike List Protection Rules showing a filter-based rule named Third Party Services, scoped to the Demo Environment with Object Type set to FQDNs and a Text Search for salesforce.com, with a No Strike List Preview and Add to No-Strike List section](/_fern-img/b363889b5ad05599cc78b9da1f16634da3f5ba70d2745344ee151e3d79159782.webp) #### Configure scan setup Set how often Method runs scans, when they may run, and where scan tasks execute. If the Environment you selected already has scheduled scans configured, Method shows a **Scans already wired up** screen instead. Each Campaign caps at one scan setup per Environment to avoid scanning the same surface twice. You can adjust cadence and hours for scanning via the Automator page. ![Scan setup screen showing Scans already wired up with a message that the environment already has scheduled task runs configured and won't create more. A list of existing paused scans is shown including DNS Enumerate, Web Pentest, Web Discover, CDN Discover, and others.](/_fern-img/cc02093bd5a2b0f47f77d1f0b0217a8a38c9e8d84ef9c903efb00e58d0f38c80.webp) For new scan setups, configure the following: ![Scan setup screen showing the Run scans toggle set to On, a Scan picker prompting you to seed Objects first, an Environment variables section, a Schedule set to Daily, and an Operating hours section with a time range of 09:00 AM to 05:00 PM](/_fern-img/b489d8e72ec258f1daf0c14bb24d37b608ab7a2b3c11d38dd1bd75a9e2e402bc.webp) * **Run scans**: toggle on to run and schedule scan tasks against your seeded Objects. Toggle off to use the Environment's existing data without running new scans. * **Scan**: select which scan Method runs against your seeded Objects. Seed Objects in the previous step to unlock this picker. * **Schedule**: how often the scan runs. Daily is the default. You can rebalance cadence later from the Automator page. * **Operating hours**: the hours of the day this scan may NOT run. Set a start and end time to create a blackout window. Use the **Preset** dropdown for common patterns and select the applicable timezone. ![Lower portion of the scan setup screen showing an operating hours timeline preview with green bars indicating allowed hours, a days of the week selector with Mon through Fri selected, and a Scan location section with a world map showing a cloudagents Jackal pinned at coordinates 38.3632, -91.4429](/_fern-img/4a64aaeb2046bc2b3bc29fac98ba82794737c69f99741af32ede73e800d9fdd1.webp) * **Days of the week**: toggle which days the scan may run. * **Scan location**: optionally pin scan tasks to a specific Jackal. Leave empty to use the default cloud scan scope. #### Select Targeting Packages Choose how Method targets the Objects this Campaign discovers. Select from your existing Packages, or build a new one inline. ![Targeting step showing existing custom packages (Cloud Bucket Targeting Package, New package, Web Targeting Package) with checkboxes, and a Need something custom section with Clone a package and Build from scratch options](/_fern-img/da4b72b945b3d0db7cb045b3128b2278e8e3e20c0fbb8332a9e702d0b01115c8.webp) Select any saved Packages this Campaign should apply as-is. If you need something different, use **Clone a package** to start from an existing Package and edit the copy, or **Build from scratch** to hand-pick Triggers, Agents, and Rules of Engagement. For a full walkthrough on building a Package, see [Build a custom Package](/guides/targeting/build-a-custom-package). #### Review and launch Review your Campaign configuration: the Environment, scan setup, and Targeting configuration. ![Review screen showing a summary of the Campaign with Environment section (Platform Demo, Using existing), Scan setup section (schedule, days, DNS resolvers), and Targeting section (Triggers and Rules of Engagement). A green banner at the bottom confirms that hitting Launch wires the environment, schedules, and Target Packages together.](/_fern-img/bbd00b8bcb73fc8f5511f2fcbab0afb9c377efd942d2d5ac8d629c29893a6938.webp) When everything looks correct, click **Launch Campaign**. Method wires the Environment, scan schedule, and Target Packages together and starts enrolling Targets as soon as the first scan completes. --- ## What happens next Once launched, your Packages run on the schedule you configured. Method evaluates Objects in the Environment against each Package's Triggers, and matching Objects enter the Targeting funnel as Potential Targets. As Agents work through them, the **Targeting** and **Priority** tabs begin to populate. ## Next steps * [Build a custom Package](/guides/targeting/build-a-custom-package): define your own Triggers, Agents, and Rules of Engagement * [Review and act on Targets](/guides/targeting/review-and-act-on-targets): triage funnel results and act on findings * [Targeting](/platform/core-platform/targeting): understand funnel statuses and how Targets advance