Adobe Advertising Cloud Install / Embed Tag or SDK | OpsBlu Docs

Adobe Advertising Cloud Install / Embed Tag or SDK

Deployment strategies for Adobe Advertising Cloud conversion tags across web, mobile, and server environments.

Deployment Strategy

  • Preferred: Google Tag Manager with Adobe Advertising Cloud conversion tags for standard and custom events.
  • Enforce consent mode integration with your CMP (OneTrust, Cookiebot) to respect user privacy choices before tags fire.
  • Use GTM variables for environment-specific conversion tag IDs and tracking parameters to avoid mixing dev/staging data with production.
  • Consider server-side conversion tracking via Advertising Cloud API for privacy-compliant tracking and backend events.
  • Leverage Adobe Experience Cloud ID Service (ECID) for cross-device tracking and visitor identification.

Tag Manager Deployment

  • Create conversion tag templates in GTM for each conversion event type (purchase, lead, registration).
  • Build separate tags for view-through and click-through conversion tracking.
  • Bind conversion tag IDs, advertiser IDs, and event parameters to GTM variables per environment.
  • Use GTM Preview mode to validate tag firing, conversion parameters, and consent signal integration before publishing.
  • Test revenue and custom parameter passing to ensure accurate conversion value tracking.
  • Implement Adobe Experience Cloud ID Service for visitor identification across Adobe solutions.

Direct Embed or Hard-Coded Scripts

If GTM is not available, place Adobe Advertising Cloud conversion tags directly on conversion completion pages:

<!-- Adobe Experience Cloud ID Service (load first) -->
<script src="https://assets.adobedtm.com/launch-XXXXX.min.js" async></script>

<!-- Adobe Advertising Cloud Conversion Tag -->
<script>
  var adobeAdCloud = {
    advertiserId: 'YOUR_ADVERTISER_ID',
    conversionTagId: 'YOUR_TAG_ID',
    revenue: 99.99,
    orderId: 'ORD-12345',
    quantity: 1
  };
  // Fire conversion pixel
  var img = new Image();
  img.src = 'https://ad.doubleclick.net/ddm/activity/src=' +
    adobeAdCloud.advertiserId + ';type=conv;cat=' +
    adobeAdCloud.conversionTagId + ';qty=' + adobeAdCloud.quantity +
    ';cost=' + adobeAdCloud.revenue + ';ord=' + adobeAdCloud.orderId + '?';
</script>
  • Include revenue, order ID, and custom parameters as JavaScript variables before the conversion tag.
  • Keep conversion tag IDs environment-aware via server-rendered variables or feature flags.
  • Implement consent checks before initializing conversion tags to comply with GDPR and CCPA requirements.
  • Ensure Adobe Experience Cloud ID Service is loaded before conversion tags for proper visitor tracking.

Mobile & App SDKs

  • Use Adobe Experience Platform Mobile SDK to track app events that mirror web conversion events.
  • Initialize the SDK with your Adobe organization ID and configure Advertising Cloud extension.
  • Manually track conversion events with appropriate event names and parameters aligned with web tracking.
  • Configure lifecycle metrics to track app opens, installations, and engagement.
  • Align event names and parameters between web tags and mobile SDK for consistent cross-platform reporting.
  • Enable cross-device tracking by syncing mobile device IDs with Adobe Experience Cloud ID.

Server-Side Collection (Advertising Cloud API)

  • Deploy Adobe Advertising Cloud Conversion API endpoints on your backend to send server-side conversions.
  • Use conversion API for high-value events that must be tracked reliably (purchases, subscriptions, leads).
  • Send conversion events with advertiser ID, conversion tag ID, transaction details, and timestamp.
  • Include customer match data (hashed email, device ID, ECID) for improved attribution and audience building.
  • Implement retry logic, error logging, and monitoring for API requests to surface failed conversions quickly.
  • Test server-side conversions in Adobe Advertising Cloud Reports before enabling production traffic.

Adobe Analytics Integration

  • Enable Adobe Analytics for Advertising integration to share conversion data bidirectionally.
  • Configure AMO ID (Adobe Media Optimizer ID) parameter passing between Adobe Advertising Cloud and Analytics.
  • Set up Analytics eVars to capture advertising dimensions (campaign, ad group, keyword, placement).
  • Create calculated metrics in Analysis Workspace to combine Analytics and Advertising Cloud data.
  • Validate that viewthrough conversions appear in both Adobe Analytics and Advertising Cloud reports.

Validation Checklist

  • Check browser developer tools Network tab for conversion tag firing on completion pages.
  • Use Adobe Experience Cloud Debugger extension to verify tag status, parameters, and ECID presence.
  • Confirm conversion events appear in Adobe Advertising Cloud Reports within 1-2 hours.
  • Verify Adobe Analytics integration by checking AMO dimensions in Analysis Workspace.
  • Screenshot GTM Preview and conversion reports for documentation and compliance evidence.
  • Test cross-device scenarios to ensure ECID properly links user journeys.

Configuration Recommendations

Tag Type: Use JavaScript-based conversion tags (not image-based) for all new implementations. JavaScript tags support dynamic parameters, enhanced user matching, and can fire on specific user interactions rather than just page loads.

Attribution Windows: Set click-through attribution to 30 days and viewthrough to 1 day as defaults. Adjust based on your sales cycle: B2B campaigns with longer decision cycles benefit from 60-day click windows. Configure in Advertiser Settings → Attribution.

Platform Integration: If you already use Adobe Experience Platform, deploy conversion tracking through the Web SDK rather than standalone tags. This unifies identity (ECID) across Adobe Analytics, Advertising Cloud, and Target without separate tag implementations.

Launch (Tags) Deployment: Use Adobe Experience Platform Tags to manage conversion tags alongside your Analytics implementation. This ensures consistent ECID passing and simplifies tag governance with approval workflows.

Back to top