DigitalPilot MCP User Guide

Who This Guide Is For

This guide is for non-technical users who want to use the DigitalPilot MCP server confidently for reporting, lead monitoring, webhooks, forms, and Google Ads tasks.

What You Can Do

With the digitalpilot MCP server, you can ask your AI assistant to:

• check your workspace connection
• review traffic and lead performance
• monitor target accounts
• manage webhooks and test event payloads
• create/manage lead capture forms
• view and optimize Google Ads data

Before You Start

1) Confirm you are connected

Ask your assistant to run get_workspace_info.

You should see:

• your workspace/tag ID
• connected user email
• granted scopes
• optional Google Ads IDs (if Ads is connected)

If this does not return expected info, reconnect/authenticate first.

2) Start read-only, then make changes

Best practice:

• List and review existing objects.
• Make one controlled change at a time.
• Re-check results after each change.

Everyday Workflows

Weekly Traffic & Lead Review

Use this sequence each week:

• get_report_channel - See how channels are performing.
• get_report_utm - See campaign/source/medium attribution.
• get_report_overview (optionally high_intent: true) - Identify high-intent companies.
• list_leads - Review lead volume and source quality.
• get_domain_activities (for specific domains) - Understand account-level behavior over time.

Tip: Use from and to dates in YYYY-MM-DD format.

Target Account Tracking (ABM)

When running account-based workflows:

• list_target_account_lists - Check existing lists.
• create_target_account_list - Create a new list if needed.
• add_target_accounts - Add domains to track.
• list_target_accounts_in_list - Validate members.
• remove_target_account - Remove outdated accounts.

Tip: Use clean domains like acme.com (not full URLs).

Webhooks (Alerts & Automations)

If you need events sent to another system:

• create_webhook - Set destination URL + subscriptions: high_intent, target_accounts, lead_capture.
• list_webhooks - Confirm setup.
• get_webhook_test_payload - Test payload format before going live.

Recommended: Always set a signing_secret in production.

Lead Capture Forms

To launch or update forms:

• list_forms - Review existing forms first.
• create_form - Create a new form (title is required).
• get_form - Validate saved config.
• update_form - Improve fields/pages/style/options.
• delete_form - Remove unused forms.

Google Ads: Safe Operating Flow

For Ads tasks, use this order:

• get_workspace_info - Verify Ads context/scopes.
• google_ads_list_campaigns - Review campaign state first.

Use change tools carefully:

• google_ads_create_campaign
• google_ads_update_campaign
• google_ads_add_keywords
• google_ads_add_negative_keywords

Use planning/reporting tools:

• google_ads_get_search_terms_report
• google_ads_generate_keyword_ideas
• google_ads_run_gaql

Important notes:

• Campaign budgets are in micros (5000000 = $5/day).
• New campaigns default to PAUSED unless explicitly enabled.

Quick Prompts You Can Reuse

• Run a weekly traffic review for the last 7 days and show channel + UTM + lead highlights.
• Show me high-intent companies this week and list top domains to prioritize.
• Create a target account list called Q2 ICP and add these domains: ...
• Set up a webhook for high_intent and lead_capture, then show me a test payload.
• List current campaigns, identify low-performing areas, and suggest keyword actions.

Common Mistakes to Avoid

• Running Google Ads changes before confirming workspace/customer context.
• Creating duplicates because existing forms/webhooks/lists were not listed first.
• Using full URLs instead of normalized domains for target accounts.
• Assuming test payloads are real historical events (they are sample structures).
• Mixing grouped reports (channel, utm) with row-level company data (overview).

Troubleshooting Checklist

If results look wrong or empty:

• confirm date range format: YYYY-MM-DD
• check pagination (page, limit)
• verify scope/access in get_workspace_info
• ensure the workspace has data in that time window
• re-run list tools to confirm object IDs before updates/deletes