@cesteral/amazon-dsp-mcp 1.0.0

package/dist/mcp-server/prompts/definitions/cross-platform-campaign-setup.prompt.d.ts

@@ -0,0 +1,4 @@
+import type { Prompt } from "@modelcontextprotocol/sdk/types.js";
+export declare const crossPlatformCampaignSetupPrompt: Prompt;
+export declare function getCrossPlatformCampaignSetupMessage(args?: Record<string, string>): string;
+//# sourceMappingURL=cross-platform-campaign-setup.prompt.d.ts.map

package/dist/mcp-server/prompts/definitions/cross-platform-campaign-setup.prompt.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"cross-platform-campaign-setup.prompt.d.ts","sourceRoot":"","sources":["../../../../src/mcp-server/prompts/definitions/cross-platform-campaign-setup.prompt.ts"],"names":[],"mappings":"AAGA,OAAO,KAAK,EAAE,MAAM,EAAE,MAAM,oCAAoC,CAAC;AAQjE,eAAO,MAAM,gCAAgC,EAAE,MAiB9C,CAAC;AAEF,wBAAgB,oCAAoC,CAAC,IAAI,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,GAAG,MAAM,CA0R1F"}

package/dist/mcp-server/prompts/definitions/cross-platform-campaign-setup.prompt.js

@@ -0,0 +1,299 @@
+export const crossPlatformCampaignSetupPrompt = {
+    name: "cross_platform_campaign_setup",
+    description: "Guide for setting up a coordinated multi-platform campaign across DV360 (dv360-mcp), The Trade Desk (ttd-mcp), Google Ads (gads-mcp), Meta Ads (meta-mcp), LinkedIn (linkedin-mcp), TikTok (tiktok-mcp), Pinterest (pinterest-mcp), Snapchat (snapchat-mcp), and Amazon DSP (amazon-dsp-mcp). Covers platform selection, budget allocation, naming conventions, and phased launch.",
+    arguments: [
+        {
+            name: "totalBudget",
+            description: "Total campaign budget across all platforms (e.g., '50000' for $50,000)",
+            required: false,
+        },
+        {
+            name: "objective",
+            description: "Campaign objective: 'awareness', 'consideration', or 'conversion' (default: conversion)",
+            required: false,
+        },
+    ],
+};
+export function getCrossPlatformCampaignSetupMessage(args) {
+    const totalBudget = args?.totalBudget || "{totalBudget}";
+    const objective = args?.objective || "conversion";
+    return `# Cross-Platform Coordinated Campaign Setup
+
+Total Budget: \$${totalBudget}
+Objective: \`${objective}\`
+
+This workflow guides you through setting up campaigns across multiple ad platforms in a coordinated manner. You must be connected to the relevant MCP servers.
+
+---
+
+## Step 1: Platform Selection
+
+Choose platforms based on your objective and audience:
+
+| Objective | Recommended Platforms | Rationale |
+|-----------|----------------------|-----------|
+| **Awareness** | DV360 + Meta + TikTok + Pinterest | DV360 for programmatic display/video reach, Meta/TikTok for social reach, Pinterest for visual discovery |
+| **Consideration** | DV360 + TTD + Meta + LinkedIn | Broad programmatic reach with social engagement and B2B professional targeting |
+| **Conversion** | Google Ads + Meta + TTD + Amazon DSP | Search intent (Google) + social retargeting (Meta) + programmatic (TTD) + retail intent (Amazon) |
+| **B2B** | LinkedIn + Google Ads + Meta | Professional audience targeting on LinkedIn, search intent, social retargeting |
+| **Gen Z / Video** | TikTok + Snapchat + Meta | Short-form video engagement across Gen Z/Millennial audiences |
+| **Shopping / E-commerce** | Pinterest + Meta + Google Ads + Amazon DSP | Visual discovery + social + search + retail intent |
+| **Full-Funnel** | All 9 platforms | Maximum reach across all touchpoints |
+
+---
+
+## Step 2: Budget Allocation
+
+Split the total budget across platforms. Common allocation strategies:
+
+### Performance-Based (Recommended for existing campaigns)
+Allocate based on historical CPA/ROAS data. Use the \`cross_platform_performance_comparison\` prompt to gather data first.
+
+### Equal Split (New campaigns with no history)
+
+| Platform | Allocation | Budget |
+|----------|-----------|--------|
+| DV360 | 15% | \$${totalBudget} × 0.15 |
+| TTD | 15% | \$${totalBudget} × 0.15 |
+| Google Ads | 15% | \$${totalBudget} × 0.15 |
+| Meta | 15% | \$${totalBudget} × 0.15 |
+| LinkedIn | 10% | \$${totalBudget} × 0.10 |
+| TikTok | 10% | \$${totalBudget} × 0.10 |
+| Pinterest | 10% | \$${totalBudget} × 0.10 |
+| Snapchat | 5% | \$${totalBudget} × 0.05 |
+| Amazon DSP | 5% | \$${totalBudget} × 0.05 |
+
+### Objective-Weighted
+
+| Platform | Awareness | Consideration | Conversion | B2B | Shopping |
+|----------|-----------|---------------|------------|-----|----------|
+| DV360 | 25% | 20% | 10% | 5% | 5% |
+| TTD | 15% | 15% | 15% | 5% | 10% |
+| Google Ads | 5% | 15% | 30% | 20% | 20% |
+| Meta | 20% | 20% | 15% | 15% | 20% |
+| LinkedIn | 5% | 10% | 5% | 35% | 2% |
+| TikTok | 15% | 10% | 10% | 5% | 8% |
+| Pinterest | 10% | 5% | 5% | 0% | 20% |
+| Snapchat | 5% | 5% | 5% | 0% | 5% |
+| Amazon DSP | 0% | 0% | 5% | 15% | 10% |
+
+---
+
+## Step 3: Naming Convention
+
+Use consistent naming across all platforms for easy cross-platform tracking:
+
+**Pattern:** \`{Brand}_{Objective}_{Platform}_{Geo}_{Audience}_{YYYYMM}\`
+
+**Examples:**
+- \`Acme_Conv_DV360_US_Retargeting_202603\`
+- \`Acme_Conv_TTD_US_Retargeting_202603\`
+- \`Acme_Conv_GADS_US_Search_202603\`
+- \`Acme_Conv_META_US_Lookalike_202603\`
+- \`Acme_B2B_LI_US_Professionals_202603\`
+- \`Acme_Aware_TT_US_GenZ_202603\`
+- \`Acme_Shop_PIN_US_ShoppingIntent_202603\`
+- \`Acme_Aware_SNAP_US_GenZ_202603\`
+- \`Acme_Conv_AMZN_US_Retargeting_202603\`
+
+---
+
+## Step 4: Create Campaigns on Each Platform
+
+### DV360 (via dv360-mcp)
+
+Use the \`full_campaign_setup_workflow\` prompt for detailed guidance.
+
+Key steps:
+1. Create Campaign (PAUSED status)
+2. Create Insertion Order (DRAFT status)
+3. Create Line Items (DRAFT status)
+4. Assign targeting
+5. Activate via \`entity_activation_workflow\`
+
+⚠️ **DV360 budget values are in micros** (1,000,000 = $1.00)
+
+### The Trade Desk (via ttd-mcp)
+
+Use the \`ttd_campaign_setup_workflow\` prompt for detailed guidance.
+
+Key steps:
+1. Create Campaign
+2. Create Ad Groups with RTBAttributes
+3. Create Ads and link Creatives
+4. Set availability to "Available"
+
+⚠️ **TTD budget values are in dollars** ($100.00 = 100.00)
+
+### Google Ads (via gads-mcp)
+
+Use the \`gads_campaign_setup_workflow\` prompt for detailed guidance.
+
+Key steps:
+1. Create Campaign Budget
+2. Create Campaign (PAUSED)
+3. Create Ad Groups
+4. Create Keywords (for Search)
+5. Create Responsive Search Ads
+6. Enable campaign
+
+⚠️ **Google Ads budget values are in micros** (1,000,000 = $1.00)
+
+### Meta Ads (via meta-mcp)
+
+Use the \`meta_campaign_setup_workflow\` prompt for detailed guidance.
+
+Key steps:
+1. Create Campaign (PAUSED)
+2. Create Ad Creative
+3. Create Ad Sets with targeting
+4. Create Ads
+5. Activate
+
+⚠️ **Meta budget values are in cents** (5000 = $50.00)
+
+### LinkedIn Ads (via linkedin-mcp)
+
+Use the \`linkedin_campaign_setup_workflow\` prompt for detailed guidance.
+
+Key steps:
+1. Create Campaign Group (ACTIVE or PAUSED)
+2. Create Campaign with targeting criteria and CPM bid
+3. Create Creative linked to the campaign
+4. Activate via \`linkedin_bulk_update_status\`
+
+⚠️ **LinkedIn budget values are in dollars** ($100.00 = 100.00)
+
+Best for: B2B, professional audiences, job title/company/skill targeting
+
+### TikTok Ads (via tiktok-mcp)
+
+Use the \`tiktok_campaign_setup_workflow\` prompt for detailed guidance.
+
+Key steps:
+1. Create Campaign with objective and budget
+2. Create Ad Group with targeting and schedule
+3. Upload creatives via \`tiktok_upload_video\` or \`tiktok_upload_image\`
+4. Create Ads referencing the creative
+5. Enable via \`tiktok_bulk_update_status\`
+
+⚠️ **TikTok budget values are in dollars** ($100.00 = 100.00)
+
+Best for: Short-form video, Gen Z/Millennial audiences, entertainment and lifestyle brands
+
+### Pinterest (via pinterest-mcp)
+
+Use the \`pinterest_campaign_setup_workflow\` prompt for detailed guidance.
+
+Key steps:
+1. Create Campaign (ACTIVE or PAUSED)
+2. Create Ad Groups with targeting_spec
+3. Upload/identify Pinterest Pin to promote
+4. Create Ads referencing the Pin by pin_id
+5. Activate via \`pinterest_bulk_update_status\`
+
+⚠️ **Pinterest budget values are in micro-currency** (50000000 = $50.00)
+
+Best for: E-commerce, lifestyle, food/beauty brands — high visual discovery and shopping intent
+
+### Snapchat (via snapchat-mcp)
+
+Use the \`snapchat_campaign_setup_workflow\` prompt for detailed guidance.
+
+Key steps:
+1. Create Campaign with objective and budget
+2. Create Ad Squad (Ad Group) with targeting and placement
+3. Upload creative via \`snapchat_upload_media\`
+4. Create Ads referencing the creative
+5. Activate via \`snapchat_bulk_update_status\`
+
+⚠️ **Snapchat budget values are in micro-currency** (1 = $0.000001, so $100.00 = 100000000)
+
+Best for: Gen Z audiences, AR lenses, video/story formats
+
+### Amazon DSP (via amazon-dsp-mcp)
+
+Use the \`amazon_dsp_campaign_setup_workflow\` prompt for detailed guidance.
+
+Key steps:
+1. Create Order (equivalent to Campaign) with flight dates and budget
+2. Create Line Item with targeting and bid
+3. Create Creative and attach to Line Item
+4. Activate Order
+
+⚠️ **Amazon DSP budget values are numeric amounts**. Confirm the advertiser account currency before comparing with other platforms.
+
+Best for: Retail/commerce intent, first-party Amazon audience data, programmatic display
+
+---
+
+## Step 5: Budget Value Reference
+
+Critical — each platform uses different units:
+
+| Platform | Unit | $100.00 Budget | $5.00 Bid | Best For |
+|----------|------|---------------|-----------|----------|
+| **DV360** | Micros | 100000000 | 5000000 | Programmatic display/video |
+| **TTD** | Advertiser currency | 100.00 | 5.00 | Programmatic DSP |
+| **Google Ads** | Micros | 100000000 | 5000000 | Search intent |
+| **Meta** | Cents | 10000 | 500 | Social retargeting |
+| **LinkedIn** | Account currency | 100.00 | 5.00 | B2B professional audiences |
+| **TikTok** | Account currency | 100.00 | 5.00 | Short-form video, Gen Z |
+| **Pinterest** | Micro-currency | 100000000 | 5000000 | Visual discovery, shopping |
+| **Snapchat** | Micro-currency | 100000000 | 5000000 | Gen Z, AR/video |
+| **Amazon DSP** | Dollars | 100.00 | 5.00 | Retail/commerce intent |
+
+---
+
+## Step 6: Phased Launch
+
+Don't activate all platforms simultaneously. Launch in phases to monitor:
+
+### Phase 1: Pilot (Week 1)
+- Launch on **one platform** (e.g., Google Ads for conversion, Meta for awareness)
+- Allocate 25% of total budget
+- Establish baseline CPA/ROAS
+
+### Phase 2: Expand (Week 2)
+- Add **second platform** (e.g., Meta or TTD)
+- Compare performance with Phase 1 baseline
+- Adjust bids based on early results
+
+### Phase 3: Full Launch (Week 3+)
+- Activate remaining platforms
+- Use \`cross_platform_performance_comparison\` prompt to monitor
+- Reallocate budget based on performance data
+
+---
+
+## Step 7: Cross-Platform Tracking
+
+Set up consistent conversion tracking across platforms:
+
+1. **UTM parameters**: Use consistent UTM source/medium/campaign across all platforms
+2. **Conversion pixels**: Ensure all platforms track the same conversion events
+3. **Attribution window**: Note that each platform uses different attribution models — cross-platform CPA comparisons are directional
+
+---
+
+## Post-Launch Monitoring
+
+After all platforms are live:
+
+1. **Daily**: Check pacing on each platform
+2. **Weekly**: Run \`cross_platform_performance_comparison\` to compare metrics
+3. **Bi-weekly**: Reallocate budget from underperformers to top performers
+4. **Monthly**: Review overall campaign ROAS and adjust strategy
+
+---
+
+## Gotchas
+
+- **Create campaigns PAUSED/DRAFT on all platforms first**, then activate in a controlled sequence
+- **Budget units differ per platform** — double-check the conversion table above
+- **Targeting alignment**: Try to match audiences across platforms as closely as possible for valid comparisons
+- **Creative formats differ**: Each platform has different ad format requirements — plan creative assets accordingly
+- **Time zones**: Campaigns on different platforms may use different timezone settings — align flight dates carefully
+`;
+}
+//# sourceMappingURL=cross-platform-campaign-setup.prompt.js.map

package/dist/mcp-server/prompts/definitions/cross-platform-campaign-setup.prompt.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"cross-platform-campaign-setup.prompt.js","sourceRoot":"","sources":["../../../../src/mcp-server/prompts/definitions/cross-platform-campaign-setup.prompt.ts"],"names":[],"mappings":"AAWA,MAAM,CAAC,MAAM,gCAAgC,GAAW;IACtD,IAAI,EAAE,+BAA+B;IACrC,WAAW,EACT,oXAAoX;IACtX,SAAS,EAAE;QACT;YACE,IAAI,EAAE,aAAa;YACnB,WAAW,EAAE,wEAAwE;YACrF,QAAQ,EAAE,KAAK;SAChB;QACD;YACE,IAAI,EAAE,WAAW;YACjB,WAAW,EACT,yFAAyF;YAC3F,QAAQ,EAAE,KAAK;SAChB;KACF;CACF,CAAC;AAEF,MAAM,UAAU,oCAAoC,CAAC,IAA6B;IAChF,MAAM,WAAW,GAAG,IAAI,EAAE,WAAW,IAAI,eAAe,CAAC;IACzD,MAAM,SAAS,GAAG,IAAI,EAAE,SAAS,IAAI,YAAY,CAAC;IAElD,OAAO;;kBAES,WAAW;eACd,SAAS;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;oBAiCJ,WAAW;kBACb,WAAW;yBACJ,WAAW;mBACjB,WAAW;uBACP,WAAW;qBACb,WAAW;wBACR,WAAW;sBACb,WAAW;wBACT,WAAW;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAyOlC,CAAC;AACF,CAAC"}

package/dist/mcp-server/prompts/definitions/cross-platform-performance.prompt.d.ts

@@ -0,0 +1,4 @@
+import type { Prompt } from "@modelcontextprotocol/sdk/types.js";
+export declare const crossPlatformPerformancePrompt: Prompt;
+export declare function getCrossPlatformPerformanceMessage(args?: Record<string, string>): string;
+//# sourceMappingURL=cross-platform-performance.prompt.d.ts.map

package/dist/mcp-server/prompts/definitions/cross-platform-performance.prompt.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"cross-platform-performance.prompt.d.ts","sourceRoot":"","sources":["../../../../src/mcp-server/prompts/definitions/cross-platform-performance.prompt.ts"],"names":[],"mappings":"AAGA,OAAO,KAAK,EAAE,MAAM,EAAE,MAAM,oCAAoC,CAAC;AAQjE,eAAO,MAAM,8BAA8B,EAAE,MAY5C,CAAC;AAEF,wBAAgB,kCAAkC,CAAC,IAAI,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,GAAG,MAAM,CA8JxF"}

package/dist/mcp-server/prompts/definitions/cross-platform-performance.prompt.js

@@ -0,0 +1,170 @@
+export const crossPlatformPerformancePrompt = {
+    name: "cross_platform_performance_comparison",
+    description: "Guide for comparing campaign performance across DV360 (via dbm-mcp), The Trade Desk (ttd-mcp), Google Ads (gads-mcp), and Meta Ads (meta-mcp). Normalizes metrics, identifies top performers, and recommends budget reallocation.",
+    arguments: [
+        {
+            name: "dateRange",
+            description: "Date range for comparison (e.g., LAST_7_DAYS, LAST_30_DAYS, or custom YYYY-MM-DD format)",
+            required: false,
+        },
+    ],
+};
+export function getCrossPlatformPerformanceMessage(args) {
+    const dateRange = args?.dateRange || "LAST_7_DAYS";
+    return `# Cross-Platform Performance Comparison
+
+Date Range: \`${dateRange}\`
+
+This workflow coordinates across multiple MCP servers to gather, normalize, and compare campaign performance. You must be connected to all relevant servers.
+
+---
+
+## Step 1: Gather Metrics from Each Platform
+
+### DV360 (via dbm-mcp)
+
+\`\`\`json
+{
+  "tool": "dbm_get_performance_metrics",
+  "params": {
+    "campaignId": "{dv360CampaignId}",
+    "profileId": "{dv360AdvertiserId}",
+    "dateRange": "${dateRange}"
+  }
+}
+\`\`\`
+
+Key metrics returned: impressions, clicks, spend, CPM, CTR, CPA, ROAS.
+
+### The Trade Desk (via ttd-mcp)
+
+\`\`\`json
+{
+  "tool": "ttd_get_report",
+  "params": {
+    "reportName": "Cross-Platform Comparison",
+    "dateRange": "${dateRange}",
+    "dimensions": ["CampaignId", "CampaignName"],
+    "metrics": ["Impressions", "Clicks", "TotalCostAdvertiserCurrency", "Conversions", "Revenue"],
+    "profileIds": ["{ttdAdvertiserId}"]
+  }
+}
+\`\`\`
+
+### Google Ads (via gads-mcp)
+
+\`\`\`json
+{
+  "tool": "gads_get_insights",
+  "params": {
+    "customerId": "{gadsCustomerId}",
+    "entityType": "campaign",
+    "dateRange": "${dateRange}"
+  }
+}
+\`\`\`
+
+### Meta Ads (via meta-mcp)
+
+\`\`\`json
+{
+  "tool": "meta_get_insights",
+  "params": {
+    "entityId": "{metaCampaignId}",
+    "fields": ["impressions", "clicks", "spend", "cpm", "ctr", "cpc", "conversions", "cost_per_action_type"],
+    "datePreset": "last_7d"
+  }
+}
+\`\`\`
+
+---
+
+## Step 2: Normalize Metrics
+
+Each platform reports metrics differently. Normalize to a common format:
+
+| Metric | DV360 (dbm-mcp) | TTD (ttd-mcp) | Google Ads (gads-mcp) | Meta (meta-mcp) |
+|--------|-----------------|---------------|----------------------|-----------------|
+| **Spend** | USD (from report) | Advertiser currency | Micros (÷ 1,000,000) | Cents (÷ 100) |
+| **CPM** | Calculated | Calculated | Micros (÷ 1,000,000) | Cents (÷ 100) |
+| **CPC** | Calculated | Calculated | Micros (÷ 1,000,000) | Cents (÷ 100) |
+| **CTR** | Ratio (0-1) | Ratio (0-1) | Ratio (0-1) | Percentage string |
+| **Conversions** | Bid Manager metric | \`Conversions\` field | \`conversions\` metric | \`conversions\` field |
+
+### Normalization formulas:
+
+- **Google Ads micros → USD**: Divide by 1,000,000
+- **Meta cents → USD**: Divide by 100
+- **Meta CTR string → number**: Parse "1.23%" to 0.0123
+- **CPM**: (Spend / Impressions) × 1,000
+- **CTR**: Clicks / Impressions
+- **CPA**: Spend / Conversions
+- **ROAS**: Revenue / Spend
+
+---
+
+## Step 3: Compare in Normalized Table
+
+Present results in a unified format:
+
+| Platform | Campaign | Impressions | Clicks | CTR | Spend (USD) | CPM (USD) | CPA (USD) | ROAS |
+|----------|----------|-------------|--------|-----|-------------|-----------|-----------|------|
+| DV360 | {name} | {n} | {n} | {%} | \${n} | \${n} | \${n} | {n}x |
+| TTD | {name} | {n} | {n} | {%} | \${n} | \${n} | \${n} | {n}x |
+| Google Ads | {name} | {n} | {n} | {%} | \${n} | \${n} | \${n} | {n}x |
+| Meta | {name} | {n} | {n} | {%} | \${n} | \${n} | \${n} | {n}x |
+
+---
+
+## Step 4: Identify Winners and Losers
+
+Rank platforms by key efficiency metrics:
+
+### By CPA (lower is better)
+1. Best CPA platform → candidate for budget increase
+2. Worst CPA platform → candidate for budget decrease or pause
+
+### By ROAS (higher is better)
+1. Best ROAS platform → highest return on investment
+2. Worst ROAS platform → losing money if < 1.0
+
+### By CPM (context-dependent)
+- Low CPM + low CTR → cheap but ineffective (awareness only)
+- High CPM + high CTR → expensive but effective (consider if CPA is good)
+
+---
+
+## Step 5: Recommend Budget Reallocation
+
+Based on the comparison, suggest budget moves:
+
+### Conservative Approach (low risk)
+- Shift 10-15% of budget from worst performer to best performer
+- Monitor for 1 week before making further changes
+
+### Aggressive Approach (high confidence)
+- Shift 25-30% of budget from worst performer to best performer
+- Pause campaigns on platforms with ROAS < 0.5
+
+### Execution
+
+For each platform where budget changes are needed:
+
+- **DV360**: Use \`dv360_update_entity\` (via dv360-mcp) to adjust IO/Line Item budgets
+- **TTD**: Use \`ttd_update_entity\` (via ttd-mcp) to adjust campaign/ad group budgets
+- **Google Ads**: Use \`gads_update_entity\` (via gads-mcp) to adjust campaign budgets
+- **Meta**: Use \`meta_update_entity\` (via meta-mcp) to adjust campaign/ad set budgets
+
+---
+
+## Gotchas
+
+- **Date ranges differ by platform**: DV360 uses Bid Manager presets (LAST_7_DAYS), TTD uses date strings, Google Ads uses date ranges in GAQL, Meta uses datePreset or timeRange. Align dates carefully.
+- **Currency differences**: Ensure all platforms report in the same currency before comparing. TTD reports in advertiser currency, others in USD by default.
+- **Attribution models differ**: Each platform attributes conversions differently. Cross-platform CPA comparisons are directional, not exact.
+- **Data freshness varies**: Meta has up to 48-hour lag. DV360 reports are async. TTD and Google Ads are near-real-time. Compare data from the same time window.
+- **Impression counting differs**: Viewability standards vary by platform. CPM comparisons should account for this.
+- **Not all campaigns are comparable**: Only compare campaigns targeting similar audiences, geos, and objectives. A brand awareness campaign on DV360 shouldn't be compared with a direct response campaign on Google Ads.
+`;
+}
+//# sourceMappingURL=cross-platform-performance.prompt.js.map

package/dist/mcp-server/prompts/definitions/cross-platform-performance.prompt.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"cross-platform-performance.prompt.js","sourceRoot":"","sources":["../../../../src/mcp-server/prompts/definitions/cross-platform-performance.prompt.ts"],"names":[],"mappings":"AAWA,MAAM,CAAC,MAAM,8BAA8B,GAAW;IACpD,IAAI,EAAE,uCAAuC;IAC7C,WAAW,EACT,mOAAmO;IACrO,SAAS,EAAE;QACT;YACE,IAAI,EAAE,WAAW;YACjB,WAAW,EACT,0FAA0F;YAC5F,QAAQ,EAAE,KAAK;SAChB;KACF;CACF,CAAC;AAEF,MAAM,UAAU,kCAAkC,CAAC,IAA6B;IAC9E,MAAM,SAAS,GAAG,IAAI,EAAE,SAAS,IAAI,aAAa,CAAC;IAEnD,OAAO;;gBAEO,SAAS;;;;;;;;;;;;;;;;oBAgBL,SAAS;;;;;;;;;;;;;;oBAcT,SAAS;;;;;;;;;;;;;;;;oBAgBT,SAAS;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA0G5B,CAAC;AACF,CAAC"}

package/dist/mcp-server/prompts/definitions/entity-duplication-workflow.prompt.d.ts

@@ -0,0 +1,4 @@
+import type { Prompt } from "@modelcontextprotocol/sdk/types.js";
+export declare const amazonDspEntityDuplicationWorkflowPrompt: Prompt;
+export declare function getAmazonDspEntityDuplicationWorkflowMessage(args?: Record<string, string>): string;
+//# sourceMappingURL=entity-duplication-workflow.prompt.d.ts.map

package/dist/mcp-server/prompts/definitions/entity-duplication-workflow.prompt.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"entity-duplication-workflow.prompt.d.ts","sourceRoot":"","sources":["../../../../src/mcp-server/prompts/definitions/entity-duplication-workflow.prompt.ts"],"names":[],"mappings":"AAGA,OAAO,KAAK,EAAE,MAAM,EAAE,MAAM,oCAAoC,CAAC;AAQjE,eAAO,MAAM,wCAAwC,EAAE,MAqBtD,CAAC;AAEF,wBAAgB,4CAA4C,CAC1D,IAAI,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,GAC5B,MAAM,CAkLR"}