Adobe Advertising Cloud Troubleshooting & Debugging | OpsBlu Docs

Adobe Advertising Cloud Troubleshooting & Debugging

Fix Adobe Advertising Cloud conversion pixel failures, Analytics attribution mismatches, and DSP delivery issues.

Symptom Library

  • Conversion tags not firing or ev. pixel requests missing from Network tab
  • Attribution discrepancies between Adobe Analytics and Advertising Cloud (look for s_ecid cookie conflicts)
  • DSP campaign under-delivery or zero-impression line items
  • Search and DSP campaign sync failures showing "Sync Error" in Campaign Management
  • Creative assets rejected with error codes CR-001 through CR-015
  • Audience segment activation delays exceeding the expected 24-hour SLA

Debugging with Adobe Experience Platform Debugger

The Adobe Experience Platform Debugger extension (Chrome/Firefox) is the primary tool for validating Advertising Cloud tags.

  1. Install the extension and navigate to your conversion page.
  2. Open the Debugger and select the Adobe Advertising Cloud tab.
  3. Verify the ev. pixel fires with the correct ev_transid, ev_conversionType, and ev_revenue parameters.
  4. Check that the everesttech.net domain request returns a 200 status (a 403 indicates domain allowlist misconfiguration).
  5. Confirm the s_ecid first-party cookie is set, which bridges Analytics and Advertising Cloud identity.
// Expected pixel request in Network tab:
// GET https://ad.everesttech.net/px/[ADVERTISER_ID]/ev?ev_conversionType=purchase&ev_revenue=49.99&ev_transid=ORDER-12345

Common DSP Error Codes

Code Meaning Fix
DSP-4001 Budget exhausted at package level Increase package budget or redistribute across line items
DSP-4003 No eligible inventory for targeting criteria Broaden geo or audience targeting; check deal ID validity
DSP-4010 Creative failed audit (third-party verification) Review IAS/DoubleVerify flags and resubmit creative
DSP-4022 Frequency cap reached across all users in segment Increase cap or expand audience pool
DSP-5001 Internal bid engine timeout Retry; if persistent, contact Adobe support with campaign ID

Search and DSP Campaign Sync Issues

When Search campaigns fail to sync with DSP reporting:

  1. Verify the AMO ID (s_kwcid parameter) is appending correctly to landing page URLs.
  2. In Adobe Analytics, confirm the Advertising Analytics integration is active under Admin > Report Suites.
  3. Check that the ef_id click identifier passes through landing page redirects without being stripped.
  4. For Search-to-Analytics attribution, confirm the Classification Importer ran within the last 24 hours (Admin > Classification Importer > Job Status).

Creative Asset Validation

Creative rejections are common with strict IAB specifications:

  • Display: Verify file size under 150KB (expanded 300KB max), dimensions match placement, and click-through URL uses HTTPS.
  • Video: Confirm VAST 3.0/4.0 compliance. Test your VAST tag at https://videovalidator.com before uploading.
  • Native: Ensure headline stays under 25 characters and description under 90 characters. Images must be at least 627x627px.
  • Audio: Files must be MP3 or AAC, 15 or 30 seconds, and under 1MB.

Conversion Tracking Validation with Adobe Analytics

To reconcile Advertising Cloud conversions with Analytics:

  1. Open Analytics Workspace and create a segment where AMO ID exists.
  2. Compare AMO Click-throughs (Advertising Cloud metric) with Instances on the Analytics conversion event.
  3. A discrepancy over 15% typically indicates tag timing issues. Check that the Analytics beacon fires before the Advertising Cloud pixel on the conversion page.
  4. For view-through conversions, verify the impression cookie window (default 60 days) matches your Analytics lookback window.

Channel-Specific Troubleshooting

DSP (Demand-Side Platform) Delivery Issues

When line items show zero or low impressions:

  1. Check inventory availability: Navigate to Inventory > On-Demand and verify the deal IDs attached to your package are active. Expired private marketplace deals silently block delivery.
  2. Review bid floors: If CPMs are set below exchange floor prices, impressions will not be won. Raise the bid cap by 20-30% and monitor for 4 hours before adjusting further.
  3. Validate audience segments: Under Audiences > All Segments, confirm the matched user count exceeds 10,000. Segments below this threshold are too small for most exchanges.
  4. Frequency cap conflicts: Package-level and line-item-level frequency caps stack. If the package is set to 3/day and the line item to 2/day, the effective cap is 2/day.
  5. Viewability pre-bid filters: Overly strict viewability thresholds (above 70%) combined with narrow geo targeting can eliminate most available inventory.

Search Campaign Sync Failures

When Google Ads or Microsoft Advertising campaigns fail to sync:

  1. Verify the engine account connection under Search > Accounts. A red status icon indicates an expired OAuth token---click Reauthorize to refresh.
  2. Check that auto-tagging is enabled in the engine account. Adobe Advertising Cloud requires gclid (Google) or msclkid (Microsoft) to pass through.
  3. Review the sync log under Search > Tools > Sync Log for specific error codes. SYNC-3001 indicates a permissions issue; SYNC-3005 means the account was paused at the engine level.
  4. For bulk sheet upload failures, confirm the file uses UTF-8 encoding and that column headers match the current template (download a fresh template from Tools > Bulksheets).

Social Campaign Tracking Gaps

When social campaign data is incomplete or missing:

  1. Confirm the social platform connector is active under Integrations > Social Channels.
  2. Social impression data typically lags 4-6 hours. Do not troubleshoot gaps that are less than 6 hours old.
  3. Verify that UTM parameters on social ad URLs include utm_source, utm_medium, and utm_campaign for fallback attribution in Adobe Analytics.
  4. For Facebook/Instagram campaigns, check that the Meta Conversions API server-side integration is not sending duplicate events that inflate conversion counts.

Adobe Experience Platform Integration Errors

Segment Sync Failures

When AEP audience segments do not appear in Advertising Cloud:

  1. In AEP, navigate to Destinations > Adobe Advertising Cloud and verify the destination status is Active.
  2. Check that the segment evaluation schedule has run. Batch segments update every 24 hours; streaming segments should propagate within 15 minutes.
  3. Confirm the identity namespace used in the segment matches what Advertising Cloud expects (typically ECID or email_lc_sha256).
  4. Review the dataflow monitoring dashboard in AEP for failed activation runs with error DEST-4XX codes.

Identity Resolution Issues

  1. Verify the s_ecid first-party cookie is being set on all domains where conversion pages live. Missing cookies break cross-device identity stitching.
  2. In the AEP Identity Graph, check that Advertising Cloud visitor IDs (AMID) are correctly linked to Analytics ECIDs.
  3. For CRM onboarding mismatches, confirm the hashing algorithm (SHA-256, lowercase, trimmed) matches between your upload file and AEP schema expectations.

Data Connector Timeout Errors

  1. AEP data connector timeouts (error CONN-5001) typically occur during large historical backfills. Reduce the backfill window to 7 days and run multiple sequential jobs.
  2. If real-time streaming connectors timeout, check the AEP status page (status.adobe.com) for platform incidents.
  3. Increase the connector retry limit from the default of 3 to 5 under Destinations > Destination Details > Configuration.

Common Error Messages

Error Message Cause Fix
403 Forbidden on everesttech.net Your domain is not on the Advertising Cloud pixel allowlist Submit your domain via Adobe Customer Care or add it under Admin > Advertiser Settings > Authorized Domains
SYNC-3001: Insufficient permissions The OAuth token for the connected search engine lacks campaign management scope Reauthorize the engine account with an admin-level user under Search > Accounts
SYNC-3005: Account paused at engine level The Google Ads or Microsoft Advertising account was paused or suspended externally Reactivate the account directly in the search engine, then trigger a manual sync
CR-007: Creative exceeds maximum file size Display creative file size exceeds the IAB spec limit (150KB initial load) Compress images, reduce animation frames, or split into polite-load assets
DSP-4003: No eligible inventory Targeting criteria are too narrow to match available bid requests Broaden geographic, audience, or contextual targeting; verify deal IDs are not expired
CONV-2001: Duplicate transaction ID The same ev_transid value was sent more than once within the deduplication window Ensure your order confirmation page generates a unique transaction ID per purchase and does not fire on page refresh
API-429: Rate limit exceeded More than 100 API requests were made within a 60-second rolling window Implement exponential backoff starting at 2 seconds; batch report requests where possible
DEST-4012: Segment activation failed An AEP audience segment could not be pushed to the Advertising Cloud destination Check that the segment contains at least 100 qualified profiles and that the destination connection has not expired

API Troubleshooting

OAuth Authentication Failures

  1. Adobe Advertising Cloud APIs use OAuth 2.0 via Adobe IMS. If you receive a 401 Unauthorized, regenerate the access token at https://ims-na1.adobelogin.com/ims/token/v3.
  2. Ensure the API integration in Adobe Developer Console has the Advertising Cloud product profile assigned. Missing profiles return 403 even with a valid token.
  3. Access tokens expire after 24 hours. Use the refresh token flow for unattended scripts rather than hardcoding tokens.
  4. For service-account (JWT) authentication, verify the private key has not expired and the metascopes field includes ent_advertising_cloud_sdk.

Rate Limiting and Quota Errors

  1. The Advertising Cloud API enforces a limit of 100 requests per minute per integration. Monitor the X-RateLimit-Remaining response header to stay within bounds.
  2. When you receive API-429, wait for the duration specified in the Retry-After header before sending the next request.
  3. Batch reporting endpoints (/reports/batch) can combine up to 10 report definitions in a single call, significantly reducing request counts.
  4. For high-volume integrations, request an elevated quota through your Adobe account team.

Report API Timeout Handling

  1. Report requests covering more than 90 days of data or containing more than 50 dimensions may timeout. Split into smaller date ranges.
  2. Use the asynchronous report endpoint (POST /reports/async) for queries expected to run longer than 30 seconds. Poll the status endpoint until state returns COMPLETED.
  3. If a report returns 504 Gateway Timeout, reduce the number of metrics and breakdowns requested, then retry.
  4. Cache report results on your side for dashboards that refresh frequently. Advertising Cloud data finalizes 48 hours after the activity date.

Troubleshooting Checklist

Use this ordered checklist when diagnosing any Advertising Cloud issue:

  1. Pixel fires: Open DevTools Network tab, filter for everesttech.net, and confirm a 200 response.
  2. Parameters present: Verify ev_transid, ev_conversionType, and ev_revenue are populated with correct values.
  3. Cookie set: Confirm the s_ecid first-party cookie exists on the conversion domain.
  4. Analytics integration: In Adobe Analytics Workspace, validate that AMO ID dimension is populated for the date range in question.
  5. DSP delivery: In Campaign Management, check line item pacing is above 80% and no error codes are showing.
  6. Search sync: Under Search > Tools > Sync Log, confirm the last successful sync is within 6 hours.
  7. AEP segments: In the AEP Destinations dashboard, verify the Advertising Cloud destination activation status is green.
  8. API health: If using the API, check that the access token is valid and X-RateLimit-Remaining is above zero.

Escalation & Communication

  • Adobe Customer Care: File tickets with the campaign ID, DSP error code, and timestamp range.
  • Adobe Professional Services for complex multi-solution implementation issues.
  • Adobe Experience League Community for peer-sourced solutions and workarounds.
  • Include Network > HAR export from the Debugger when filing pixel-related tickets.
  • For urgent delivery issues affecting live campaigns, use the Priority 1 ticket classification to trigger the 4-hour SLA.

Preventive Maintenance

  • Weekly conversion tracking validation: compare Advertising Cloud vs. Analytics conversion counts.
  • Monthly DSP delivery audit: flag any line item delivering under 80% of budget.
  • Quarterly creative asset compliance review against updated IAB specs.
  • Run the Adobe Experience Platform Debugger on key conversion pages after each site deployment.
  • Monitor everesttech.net pixel response times; latency over 500ms degrades attribution accuracy.
  • Monthly review of AEP destination connection health to catch expired tokens before they break segment sync.
  • Bi-weekly API integration audit: verify token expiry dates and refresh token validity.
Nach oben