{
  "schemaVersion": "1.2.0",
  "schema": "https://hivesilo.com/evidence/company-fact-sheet.schema.json",
  "slug": "adobe-experience",
  "product": "Adobe Experience",
  "url": "https://hivesilo.com/integrations/adobe-experience",
  "title": "Adobe Experience Integration: Scored Buyer Profiles | HiveSilo",
  "description": "Adobe Experience integration with HiveSilo: scored website buyers streamed to Adobe Experience Platform profiles and written to Marketo Engage leads by documented APIs.",
  "reviewed": "2026-11-11",
  "connectionStatus": "available",
  "image": {
    "width": 1800,
    "height": 1195,
    "group": "crm",
    "alt": "Illustrative enterprise office at dusk for the Adobe Experience integration workflow",
    "heroVariants": [
      {
        "path": "/img/integrations/adobe-experience-integration-crm-480.854e22807114.webp",
        "width": 480,
        "height": 319,
        "bytes": 21216
      },
      {
        "path": "/img/integrations/adobe-experience-integration-crm-768.3a4946822424.webp",
        "width": 768,
        "height": 510,
        "bytes": 47770
      },
      {
        "path": "/img/integrations/adobe-experience-integration-crm-1200.742eae743649.webp",
        "width": 1200,
        "height": 797,
        "bytes": 98032
      },
      {
        "path": "/img/integrations/adobe-experience-integration-crm-1800.bc95e30e4f11.webp",
        "width": 1800,
        "height": 1195,
        "bytes": 169500
      }
    ],
    "socialImage": {
      "path": "/og/adobe-experience-integration-intelligence.f40a6dd0cbcd.png",
      "width": 1200,
      "height": 630,
      "bytes": 771400
    },
    "retiredSocialImages": [],
    "sourceSha256": "40f59dc928a0",
    "source": "AI-generated illustrative scene; not a vendor or customer facility",
    "illustrative": true
  },
  "content": {
    "inventoryId": "P708",
    "slug": "adobe-experience",
    "product": "Adobe Experience",
    "shortName": "Adobe Experience",
    "niche": "crm-platforms",
    "connectionStatus": "available",
    "reviewed": "2026-11-11",
    "contentVersion": "1.2.0",
    "title": "Adobe Experience Integration: Scored Buyer Profiles | HiveSilo",
    "description": "Adobe Experience integration with HiveSilo: scored website buyers streamed to Adobe Experience Platform profiles and written to Marketo Engage leads by documented APIs.",
    "primaryKeyword": "Adobe Experience integration",
    "secondaryKeywords": [
      "Adobe Experience Platform streaming ingestion API",
      "Adobe Real-Time CDP HTTP API source",
      "Marketo Engage lead API integration",
      "Adobe Experience buyer intent data",
      "HiveSilo Adobe Experience"
    ],
    "sources": [
      {
        "id": "P708-D01",
        "title": "Adobe Experience Platform: Streaming Ingestion Overview",
        "url": "https://experienceleague.adobe.com/en/docs/experience-platform/ingestion/streaming/overview",
        "supports": "Streaming ingestion lets users stream profile records and ExperienceEvents to Experience Platform; guidance is 1000 requests per second, or 10000 individual messages per second; the enforced limit becomes 60 requests per minute when using synchronous validation; guardrails are bound to the organization's license usage entitlement.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P708-D02",
        "title": "Adobe Experience Platform: Stream Record Data Using Streaming Ingestion APIs",
        "url": "https://experienceleague.adobe.com/en/docs/experience-platform/ingestion/tutorials/streaming-record-data",
        "supports": "Record data is sent with POST /collection/{CONNECTION_ID} on https://dcs.adobedc.net, with an optional syncValidation=true query parameter that Adobe describes as intended for development purposes and rate limited to 60 times per minute per CONNECTION_ID; the body names the schema in schemaRef and carries the record in xdmEntity; the tutorial builds the schema on the XDM Individual Profile class.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P708-D03",
        "title": "Adobe Experience Platform: HTTP API Source Connector Overview",
        "url": "https://experienceleague.adobe.com/en/docs/experience-platform/sources/connectors/streaming/http",
        "supports": "The HTTP API source connector streams data to Experience Platform and is supported by Data Prep functions, which map non XDM-compliant data to an XDM-compliant dataset.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P708-D04",
        "title": "Adobe Experience Platform: Create an HTTP API Streaming Connection Using the Flow Service API",
        "url": "https://experienceleague.adobe.com/en/docs/experience-platform/sources/api-tutorials/create/streaming/http",
        "supports": "POST /flowservice/connections on https://platform.adobe.io/data/foundation creates the streaming connection; dataType supports xdm and raw; setting authenticationRequired to true creates an authenticated connection, which Adobe says users sending Personally Identifiable Information should create; the streaming endpoint URL is returned as inletUrl; an authenticated connection rejects a missing or expired Authorization header with HTTP 401.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P708-D05",
        "title": "Adobe Experience Platform: Authenticate and Access Experience Platform APIs",
        "url": "https://experienceleague.adobe.com/en/docs/experience-platform/landing/platform-apis/api-authentication",
        "supports": "OAuth Server-to-Server is the only token generation method supported moving forward and the Service Account (JWT) method is deprecated; calls carry Authorization: Bearer, x-api-key and x-gw-ims-org-id; a new access token must be generated every 24 hours; the account needs developer and user permissions for an Experience Platform product profile, and a system administrator grants attribute-based access control permissions.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P708-D06",
        "title": "Adobe Experience Platform: Getting Started with the Schema Registry API",
        "url": "https://experienceleague.adobe.com/en/docs/experience-platform/xdm/api/getting-started",
        "supports": "The TENANT_ID ensures that resources an organization creates are namespaced properly and contained within that organization; Schema Registry calls use the x-sandbox-name header and https://platform.adobe.io/data/foundation/schemaregistry paths.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P708-D07",
        "title": "Adobe Marketo Engage Developer Guide: Leads",
        "url": "https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/rest/lead-database/leads",
        "supports": "POST /rest/v1/leads.json creates or updates up to 300 records per request; action accepts createOrUpdate, createOnly, updateOnly or createDuplicate and defaults to createOrUpdate; lookupField defaults to email; the lead object has standard fields and optional custom fields; POST /rest/v1/leads/push.json requires programName and input and accepts optional source and reason; leads are read with GET /rest/v1/leads.json and a filterType.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P708-D08",
        "title": "Adobe Marketo Engage Developer Guide: Authentication",
        "url": "https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/rest/authentication",
        "supports": "Marketo REST APIs use 2-legged OAuth 2.0; a custom service that belongs to an API-Only user provides the Client ID and Client Secret; a new access token has a lifespan of 3,600 seconds; support for the access_token query parameter was removed on August 31, 2026 and the Authorization header is to be used.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P708-D09",
        "title": "Adobe Marketo Engage Developer Guide: REST API",
        "url": "https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/rest/rest-api",
        "supports": "Each subscription is allocated 50,000 API calls per day; each instance is limited to 100 API calls per 20 seconds and ten concurrent API calls; standard calls have a maximum body size of 1 MB; the SOAP API is deprecated as of July 31st, 2026; an API Only user is given a role and attached to a Custom service in LaunchPoint.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P708-D10",
        "title": "Adobe Marketo Engage Developer Guide: Marketo Integration Best Practices",
        "url": "https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/rest/marketo-integration-best-practices",
        "supports": "API quota, rate and concurrency capacity is shared by all API services and users in an instance; exceeding the rate limit returns error code 606; Adobe suggests each third-party integration stay at 50 calls per 20 seconds or fewer and batch records into as few calls as possible.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P708-D11",
        "title": "Adobe Experience Platform: Destination SDK Overview",
        "url": "https://experienceleague.adobe.com/en/docs/experience-platform/destinations/destination-sdk/overview",
        "supports": "Destination SDK is how a productized destination is added to the Experience Platform catalog, with access through the Adobe Technology Partner Program and submission for Adobe's review. HiveSilo does not claim a catalog listing.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P708-D12",
        "title": "Adobe Experience Platform: Sandboxes Overview",
        "url": "https://experienceleague.adobe.com/en/docs/experience-platform/sandbox/home",
        "supports": "Sandboxes partition a single Experience Platform instance into separate virtual environments; a development sandbox can be used exclusively for development and testing with non-production profiles; API calls name the sandbox in the x-sandbox-name header; access to non-production sandboxes is granted through the Adobe Admin Console.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P708-D13",
        "title": "Adobe Experience Platform: Audit Logs Overview",
        "url": "https://experienceleague.adobe.com/en/docs/experience-platform/landing/governance-privacy-security/audit-logs/overview",
        "supports": "Audit logs record who performed what action and when, for resources including datasets, destinations and sandboxes; viewing and exporting them needs the View User Activity Log access control permission; logs are retained for 365 days.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P708-D14",
        "title": "Adobe Experience Platform: Segmentation Service Overview",
        "url": "https://experienceleague.adobe.com/en/docs/experience-platform/segmentation/home",
        "supports": "Segmentation Service creates audiences through segment definitions or other sources from Real-Time Customer Profile data; supported evaluation methods are streaming segmentation, batch segmentation and edge segmentation.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P708-D15",
        "title": "Adobe Experience Platform: Destinations Overview",
        "url": "https://experienceleague.adobe.com/en/docs/experience-platform/destinations/home",
        "supports": "Destinations are pre-built integrations that send audiences or datasets from Experience Platform to marketing automation platforms, digital advertising platforms and more; activating them is governed by access control permissions such as View Destinations.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P708-D16",
        "title": "Adobe Experience Platform: Data Governance Overview",
        "url": "https://experienceleague.adobe.com/en/docs/experience-platform/data-governance/home",
        "supports": "Data Governance has three elements, Labels, Policies and Enforcement; data usage labels are applied at the schema field level, including Identity \"I\" labels for data that can identify or contact a specific person; data usage policies describe which marketing actions are allowed on labeled data.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P708-D17",
        "title": "Adobe Marketo Engage Developer Guide: Activities",
        "url": "https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/rest/lead-database/activities",
        "supports": "POST /rest/v1/activities/external.json adds custom activities to lead records, up to 300 activity records at a time; a custom activity type must be approved before records are added; maximum 10 custom activities and 20 attributes each; an approved type gets a corresponding Smart List trigger and filter.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P708-D18",
        "title": "Adobe Marketo Engage Developer Guide: Smart Campaigns",
        "url": "https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/rest/assets/smart-campaigns",
        "supports": "POST /rest/v1/campaigns/{id}/trigger.json (Request Campaign) passes leads through a trigger campaign whose flow uses a Campaign is Requested trigger with Web Service API as its source; each call accepts a maximum of 100 leads.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P708-D19",
        "title": "Adobe Marketo Engage Developer Guide: Opportunities",
        "url": "https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/rest/lead-database/opportunities",
        "supports": "Marketo provides APIs for reading and writing opportunity records, queried with GET /rest/v1/opportunities.json; the Opportunity Role object links opportunities to leads; Opportunity APIs are read-only for subscriptions with SFDC Sync or Microsoft Dynamics Sync enabled.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "HSF1",
        "title": "HiveSilo capability overview",
        "url": "https://hivesilo.com/evidence/features.md",
        "supports": "Published HiveSilo capabilities: buyer intelligence with Tier 1, Tier 2 and Tier 3 qualification, Revenue Seeker, AdBrain, offline conversion feedback, AI Governance & Control, bot defense, business insights and client-controlled privacy; typical deployment of approximately 72 hours to set up and 7 days to go-live, subject to fit, readiness and scope.",
        "reviewed": "2026-11-11"
      }
    ],
    "hero": {
      "h1": "Adobe Experience. Give your profiles a first-party buyer score.",
      "lede": "Adobe Experience is a family of products. This page covers Adobe Experience Platform with Real-Time CDP, and Marketo Engage. HiveSilo scores the buyers on your own website and sends that evidence to them through the APIs Adobe documents.",
      "imageLines": [
        "Your Adobe customer profile.",
        "A buyer score from your own site."
      ]
    },
    "problem": {
      "heading": "A profile updates. Does it show a buyer?",
      "summary": "Adobe Experience brings your customer data together and acts on it. A score for how seriously someone was buying on your website has to come from somewhere.",
      "question": "What should a profile or a lead say about buying intent?",
      "paragraphs": [
        "An enquiry adds a person to Marketo Engage or updates a profile in Adobe Experience Platform with a name, an email address and a source. Two records can look alike while one person shows strong buying intent and the other was never a real buyer. The teams that build audiences and follow up decide what to do with the context the record carries.",
        "Adobe provides its own profile, audience, scoring and journey tools, and those remain the starting point. HiveSilo adds one more input: first-party behavior on your own website, scored for buying intent and screened for invalid traffic, then sent to the schema fields and lead fields your administrator chooses."
      ]
    },
    "value": {
      "heading": "Feed buyer evidence into the Adobe tools you already run.",
      "summary": "HiveSilo does not replace an Adobe audience, journey or scoring model. It supplies a score, a tier and the reasons behind them as data those tools can use.",
      "decisions": [
        {
          "title": "Who belongs in the audience.",
          "body": "Use observed buying intent as one more attribute when your team defines who to reach."
        },
        {
          "title": "Who sales should call.",
          "body": "Give Marketo Engage a current buyer score and tier on the lead before hand-off."
        },
        {
          "title": "What to stop paying for.",
          "body": "See which sources send buyers and which send traffic that never becomes a conversation."
        }
      ],
      "capabilities": [
        {
          "heading": "Profile records, streamed to your connection.",
          "body": "Your team creates an HTTP API streaming connection in Adobe Experience Platform. HiveSilo posts records to the endpoint that connection returns. The fields that hold the score sit in your own schema, in your tenant namespace.",
          "output": "A profile record carrying a buyer score and intent tier in fields you define.",
          "sourceIds": [
            "P708-D02",
            "P708-D04",
            "P708-D06"
          ]
        },
        {
          "heading": "A Marketo Engage lead, created or updated.",
          "body": "HiveSilo sends leads to the Marketo Engage Leads endpoint with the createOrUpdate action, matched on the lookup field you choose. Adobe documents that one request can create or update up to 300 records.",
          "output": "One lead per buyer, with score and tier in standard or custom fields.",
          "sourceIds": [
            "P708-D07"
          ]
        },
        {
          "heading": "Mapping on your side, if you prefer.",
          "body": "Adobe documents a raw data type for the HTTP API source, with Data Prep functions that map incoming data to an XDM-compliant dataset. Your team can keep the mapping inside Adobe Experience Platform.",
          "output": "Scored records mapped to your schema by rules your team owns.",
          "sourceIds": [
            "P708-D03",
            "P708-D04"
          ]
        }
      ]
    },
    "integration": {
      "heading": "How HiveSilo connects to Adobe Experience",
      "statusNote": "The connection is activated for each client on request, inside that client's own Adobe Experience Platform organization and sandbox or Marketo Engage instance, with the schemas, fields and permissions their administrator approves.",
      "intro": "Adobe Experience is a product family, so each row names the product it covers and a page in Adobe's public documentation. HiveSilo calls the Adobe API outbound to write these records; it does not ask Adobe to call into your systems. In this workflow it does not read profiles, audiences, leads or opportunities back from Adobe; any read is a separate permission you would grant. Adobe Experience Platform and Real-Time CDP are covered by the same streaming ingestion route.",
      "tableCaption": "What HiveSilo sends to Adobe Experience Platform, Real-Time CDP and Marketo Engage, and the documented route for each item",
      "flows": [
        {
          "sends": "A buyer who identifies themselves on your website",
          "lands": "Adobe Experience Platform and Real-Time CDP: a profile record in your dataset",
          "route": "POST to the streaming endpoint of your HTTP API connection, https://dcs.adobedc.net/collection/{CONNECTION_ID}. The body names your schema in schemaRef and carries the record in xdmEntity.",
          "sourceIds": [
            "P708-D02",
            "P708-D04"
          ]
        },
        {
          "sends": "Buyer score, Tier 1, Tier 2 or Tier 3 qualification, campaign and source context",
          "lands": "Adobe Experience Platform: fields in your own XDM schema",
          "route": "Fields your team defines through the Schema Registry, namespaced by your TENANT_ID. As an alternative, a raw connection lets Data Prep map incoming fields to your schema.",
          "sourceIds": [
            "P708-D03",
            "P708-D04",
            "P708-D06"
          ]
        },
        {
          "sends": "A scored lead for marketing and sales",
          "lands": "Marketo Engage: a lead, created or updated",
          "route": "POST /rest/v1/leads.json with action createOrUpdate, which is the default, and a lookupField that defaults to email. Up to 300 records per request.",
          "sourceIds": [
            "P708-D07"
          ]
        },
        {
          "sends": "A short reason for the score and a suggested next step",
          "lands": "Marketo Engage: standard or custom fields on the lead",
          "route": "The same Leads request body. Adobe documents that the lead object holds standard fields and optional custom fields that users create as needed.",
          "sourceIds": [
            "P708-D07"
          ]
        },
        {
          "sends": "A dated record of a high-intent visit",
          "lands": "Marketo Engage: a custom activity on the lead",
          "route": "POST /rest/v1/activities/external.json, up to 300 activity records per call. Your team creates and approves the custom activity type first; Adobe allows a maximum of 10 custom activities.",
          "sourceIds": [
            "P708-D17"
          ]
        },
        {
          "sends": "A scored lead tied to a campaign",
          "lands": "Marketo Engage: a lead with activity attributed to a named program",
          "route": "POST /rest/v1/leads/push.json with the required programName and input, and optional source and reason strings.",
          "sourceIds": [
            "P708-D07"
          ]
        }
      ],
      "facts": [
        {
          "label": "Access you grant in Adobe Experience Platform",
          "body": "Platform API calls use OAuth Server-to-Server credentials from Adobe Developer Console, tied to an Experience Platform product profile, with permissions a system administrator grants. A new access token is generated every 24 hours. Adobe says data with personal information should use an authenticated streaming connection.",
          "sourceIds": [
            "P708-D04",
            "P708-D05"
          ]
        },
        {
          "label": "Access you grant in Marketo Engage",
          "body": "A custom service that belongs to an API-Only user provides the Client ID and Client Secret. That user's roles and permissions set what the service may do. An access token lasts 3,600 seconds.",
          "sourceIds": [
            "P708-D08",
            "P708-D09"
          ]
        },
        {
          "label": "Limits to plan for",
          "body": "Marketo Engage: 50,000 API calls per day per subscription, 100 calls per 20 seconds and ten concurrent calls per instance, shared with your other integrations. Adobe Experience Platform streaming: guidance of 1000 requests per second, and 60 requests per minute with synchronous validation.",
          "sourceIds": [
            "P708-D01",
            "P708-D09",
            "P708-D10"
          ]
        },
        {
          "label": "Deprecations to know",
          "body": "Marketo Engage removed support for the access_token query parameter on August 31, 2026; the token goes in the Authorization header, which is the route used. Adobe also lists the Marketo SOAP API and the Experience Platform JWT credential method as deprecated.",
          "sourceIds": [
            "P708-D05",
            "P708-D08",
            "P708-D09"
          ]
        },
        {
          "label": "Control stays with you",
          "body": "The streaming connection, the schema, the product profile and the Marketo API-Only user all live in your Adobe accounts. Your administrators decide what the integration may write and can change or remove that access.",
          "sourceIds": [
            "P708-D04",
            "P708-D05",
            "P708-D08"
          ]
        }
      ],
      "questionsHeading": "Who, what, when, where, how and why",
      "questions": [
        {
          "label": "Who",
          "body": "Enterprises that run Adobe Experience Platform, Real-Time CDP or Marketo Engage and want those teams to see buying intent from the company website. Your Adobe administrators grant the access.",
          "sourceIds": [
            "P708-D05",
            "P708-D08"
          ]
        },
        {
          "label": "What",
          "body": "A scored lead or profile record, a buyer score, an intent tier, a short reason for them, a suggested next step, and campaign and source context.",
          "sourceIds": [
            "P708-D02",
            "P708-D07"
          ]
        },
        {
          "label": "When",
          "body": "When a visitor identifies themselves on your website, for example through an enquiry form, and again when a returning buyer's score changes.",
          "sourceIds": [
            "HS1"
          ]
        },
        {
          "label": "Where",
          "body": "In your own Adobe organization and sandbox, or your own Marketo Engage instance, in the dataset or on the lead your teams already use.",
          "sourceIds": [
            "P708-D04",
            "P708-D07",
            "HS4"
          ]
        },
        {
          "label": "How",
          "body": "Outbound calls to Adobe's documented APIs: streaming ingestion to an HTTP API connection you create, and the Marketo Engage Leads REST endpoints with a Bearer token in the Authorization header.",
          "sourceIds": [
            "P708-D02",
            "P708-D07",
            "P708-D08"
          ]
        },
        {
          "label": "Why",
          "body": "Adobe brings your customer data together and acts on it. HiveSilo knows how the buyer behaved on your website before the enquiry. Together your teams work from both.",
          "sourceIds": [
            "HS1",
            "HS2"
          ]
        }
      ],
      "summary": "Adobe Experience brings your customer data together and acts on it. HiveSilo scores buying intent on your own website, screens invalid traffic and sends a Tier 1, Tier 2 or Tier 3 qualification to Adobe Experience Platform profiles, for Real-Time CDP, by streaming ingestion, and to Marketo Engage leads by REST API, under access your administrators grant. Customer identities stay in your Adobe organization and your own confidential environment.",
      "summarySourceIds": [
        "P708-D02",
        "P708-D07",
        "HSF1",
        "HS4"
      ],
      "features": {
        "heading": "Where each HiveSilo capability meets Adobe Experience",
        "intro": "Each row pairs a published HiveSilo capability with the Adobe feature it works with, and names the Adobe product. Scope is agreed for each client. Rows that read from Adobe need a separate permission from your administrators.",
        "rows": [
          {
            "capability": "Buyer intelligence and three-tier qualification",
            "feature": "Adobe Experience Platform: fields in your own XDM Individual Profile schema. Marketo Engage: standard and custom lead fields",
            "gain": "Audience builders and lead owners see a buyer score and a Tier 1, Tier 2 or Tier 3 qualification on the profile or lead they already use.",
            "sourceIds": [
              "P708-D02",
              "P708-D06",
              "P708-D07",
              "HSF1"
            ]
          },
          {
            "capability": "AI firewall, bot defense and site protection",
            "feature": "Marketo Engage: lead creation through the Leads endpoint. Adobe Experience Platform: records sent by streaming ingestion",
            "gain": "Invalid traffic is screened before it becomes a lead or profile record your programs and audiences have to work.",
            "sourceIds": [
              "P708-D01",
              "P708-D07",
              "HSF1"
            ]
          },
          {
            "capability": "AdBrain",
            "feature": "Real-Time CDP: Segmentation Service audiences built from Real-Time Customer Profile data, and destinations that send audiences to digital advertising platforms",
            "gain": "Your team can use the qualification field in an audience it defines and activate that audience through destinations it already runs, under Adobe's own permissions and policies.",
            "sourceIds": [
              "P708-D14",
              "P708-D15",
              "HSF1"
            ]
          },
          {
            "capability": "Offline conversions, qualified-demand scaling and outcome measurement",
            "feature": "Marketo Engage: opportunity records and the Opportunity Role object that links them to leads",
            "gain": "With a read permission you grant, opportunity outcomes can inform the qualified-buyer feedback sent to supported advertising platforms.",
            "sourceIds": [
              "P708-D19",
              "HSF1"
            ]
          },
          {
            "capability": "Revenue Seeker",
            "feature": "Marketo Engage: lead records read through the Leads endpoints",
            "gain": "With a read permission you grant, Marketo Engage can be one of the authorized sources searched for revenue opportunities, which go to your own salespeople. HiveSilo cannot see those records.",
            "sourceIds": [
              "P708-D07",
              "HSF1"
            ]
          },
          {
            "capability": "AI Governance & Control",
            "feature": "Marketo Engage: Request Campaign, which only runs a trigger campaign your team built with a Campaign is Requested trigger. Marketo custom activities, which become Smart List triggers and filters",
            "gain": "Any follow-up a score starts is a campaign your team built and activated, so a person stays in charge of the outreach.",
            "sourceIds": [
              "P708-D17",
              "P708-D18",
              "HS6"
            ]
          },
          {
            "capability": "Business insights and oversight",
            "feature": "Adobe Experience Platform: audit logs, which record who performed what action and when and are retained for 365 days",
            "gain": "Your administrators can review activity on the datasets and destinations involved, with the View User Activity Log permission.",
            "sourceIds": [
              "P708-D13",
              "HSF1"
            ]
          },
          {
            "capability": "Client-controlled privacy and verification",
            "feature": "Adobe Experience Platform: authenticated streaming connections, sandboxes, and Data Governance labels and policies applied at the schema field level",
            "gain": "Customer identities stay in your Adobe organization and your confidential environment, outside HiveSilo's visibility, and your data stewards decide how the score fields may be used.",
            "sourceIds": [
              "P708-D04",
              "P708-D12",
              "P708-D16",
              "HS4",
              "HSF1"
            ]
          }
        ]
      },
      "capture": {
        "heading": "How the buying signals are captured and linked",
        "paragraphs": [
          "Lightweight first-party instrumentation on your own website reads pseudonymous behavior from your visitors. HiveSilo scores those non-PII signals. Anything that could identify a person travels from your website into your own per-tenant confidential enclave, not into HiveSilo's shared platform.",
          "An anonymous session has a score but no Adobe profile or lead. The link is made when the visitor identifies themselves on your website, for example through an enquiry form. That match happens inside your enclave, and the scored profile record or Marketo Engage lead is written to your Adobe account from there."
        ],
        "sourceIds": [
          "HS3",
          "HS4"
        ]
      },
      "setup": {
        "heading": "What your Adobe Experience team does",
        "intro": "The connection is configuration in your Adobe accounts plus activation on the HiveSilo side. These are the steps on your side. Skip the ones for Adobe products you do not run.",
        "steps": [
          {
            "title": "Define the schema fields.",
            "body": "In Adobe Experience Platform, add the fields for score, tier and reason to your schema through the Schema Registry. They sit in your tenant namespace.",
            "sourceIds": [
              "P708-D06"
            ]
          },
          {
            "title": "Create the streaming connection.",
            "body": "Create an HTTP API streaming connection and note the endpoint URL it returns. Adobe says data with personal information should use an authenticated connection.",
            "sourceIds": [
              "P708-D04"
            ]
          },
          {
            "title": "Grant Experience Platform access.",
            "body": "Create OAuth Server-to-Server credentials in Adobe Developer Console, tied to a product profile, and have a system administrator grant the permissions the dataset needs.",
            "sourceIds": [
              "P708-D05"
            ]
          },
          {
            "title": "Set up Marketo Engage access.",
            "body": "Create an API-Only user with a role limited to the agreed writes, and attach it to a custom service that provides the Client ID and Client Secret.",
            "sourceIds": [
              "P708-D08",
              "P708-D09"
            ]
          },
          {
            "title": "Choose the lead fields and any custom activity.",
            "body": "Name the lookup field and the lead fields for score and tier. If a custom activity is used, create and approve its type before records are added.",
            "sourceIds": [
              "P708-D07",
              "P708-D17"
            ]
          },
          {
            "title": "Test in a development sandbox first.",
            "body": "Adobe documents development sandboxes for development and testing with non-production profiles, named in the x-sandbox-name header. The syncValidation query parameter, intended for development purposes, returns immediate feedback on a streamed record.",
            "sourceIds": [
              "P708-D12",
              "P708-D02"
            ]
          },
          {
            "title": "Switch on production.",
            "body": "Repeat the connection and schema in your production sandbox once the development result is accepted.",
            "sourceIds": [
              "P708-D04",
              "P708-D12"
            ]
          }
        ],
        "timeline": "HiveSilo's published typical deployment is approximately 72 hours to set up and 7 days to live mapping and go-live, subject to fit, customer readiness and agreed scope. The Adobe steps above run on your own change process.",
        "timelineSourceIds": [
          "HSF1"
        ]
      },
      "preview": {
        "heading": "What your team sees on the Marketo Engage lead",
        "note": "Illustrative example, not an Adobe screen. Field and activity names are chosen by your administrator. The score shown is HiveSilo's published specimen.",
        "sourceIds": [
          "HS8"
        ],
        "fields": [
          {
            "label": "Source",
            "value": "Website"
          },
          {
            "label": "HiveSilo buyer score (custom field)",
            "value": "3,790 of 5,000"
          },
          {
            "label": "HiveSilo qualification (custom field)",
            "value": "Tier 1"
          },
          {
            "label": "Traffic check (custom field)",
            "value": "Screened as genuine"
          }
        ],
        "task": {
          "label": "Custom activity on the lead",
          "subject": "Tier 1 buying intent on the website",
          "body": "Strong buying intent on your website this week. Traffic screened as genuine. Suggested next step: pass to sales today."
        }
      }
    },
    "example": {
      "heading": "Two new leads. One nurture program. Who goes to sales?",
      "setup": "Illustrative workflow: two people fill in the same form on one morning and both become leads in Marketo Engage. One shows strong buying intent and is qualified Tier 1; the other shows little and is Tier 3.",
      "nativeBaseline": "Marketo Engage stores both leads and runs the programs and scoring your team has configured. That process stays as it is.",
      "inputs": [
        "The lead as it exists in Marketo Engage, with its program and source.",
        "HiveSilo's score and Tier 1, Tier 2 or Tier 3 qualification for the website sessions behind each enquiry, in the fields your administrator chose.",
        "A short reason for each score, including any invalid-traffic concern."
      ],
      "decision": "The team passes the Tier 1 buyer to sales and leaves the second lead in the standard program.",
      "output": "Two leads whose fields show HiveSilo's score and tier, available to the rules and views your team builds.",
      "owner": "Your marketing operations team owns the programs and the hand-off rule, and the lead owner decides the outreach. HiveSilo supplies evidence; it does not send messages on their behalf in this workflow.",
      "hold": "Hold automated outreach when the score is low, the traffic-quality concern is unresolved or contact permission is unclear.",
      "record": "Your team records the outcome in Marketo Engage as usual, so your own reporting can compare score with result. HiveSilo does not read that outcome back in this workflow.",
      "sourceIds": [
        "P708-D07"
      ]
    },
    "governance": {
      "intro": "A score informs your team. It does not act for them.",
      "example": "Decide in advance which Adobe actions a score may start and which need a person. Writing a field is different from adding someone to an audience or pushing a lead into a program. Keep the Marketo API-Only user's role limited to the agreed writes, grant the Experience Platform credential only the permissions the dataset needs, and route anything outside that scope to the named owner first."
    },
    "privacy": {
      "intro": "Your Adobe customer profile stays in your Adobe organization.",
      "detail": "The profile's or lead's identity is written to your own Adobe account from the environment you control. HiveSilo's shared platform works with permitted non-PII signals and scores. Adobe recommends an authenticated streaming connection for data that includes personal information, your schema sets which fields exist, and Adobe's own permissions continue to apply to everyone who reads them."
    },
    "outcomes": {
      "intro": "Bring website buying evidence to the Adobe Experience profile and the Marketo Engage lead, so the audience, the hand-off and the source review start from the same facts.",
      "panels": [
        "Rank Marketo Engage leads and Adobe Experience Platform profiles by observed buying intent.",
        "Find the sources and pages your strongest Adobe Experience profiles have in common, then do more of that.",
        "Review spend on sources whose leads score low and rarely progress in Marketo Engage.",
        "Screen invalid traffic before it becomes a lead or profile your Adobe programs have to work.",
        "Revisit existing Adobe profiles and leads whose website behavior shows renewed interest."
      ]
    },
    "fit": {
      "intro": "Most useful where Adobe Experience Platform or Marketo Engage is where customer data is acted on and the website is a material source of leads.",
      "good": [
        "Enterprises that build audiences in Real-Time CDP and want a first-party intent attribute.",
        "Marketing operations teams that hand leads from Marketo Engage to sales.",
        "Teams able to name the schema fields, the lead fields and the decision a score should inform."
      ],
      "consider": [
        "Adobe's own scoring, audience and journey tools may already answer the question for some teams.",
        "Adobe Experience Platform fields must exist in your schema before a record can carry them.",
        "The Marketo Engage daily quota and rate limit are shared with your other integrations.",
        "Adobe Experience covers more products than those named here. Ask about any other product before assuming it is in scope."
      ]
    },
    "connection": {
      "heading": "Agree the Adobe product, the schema and the access.",
      "paragraphs": [
        "Confirm which Adobe Experience product is the target: Adobe Experience Platform with Real-Time CDP, Marketo Engage, or both. For Experience Platform, your team creates the HTTP API streaming connection and the schema fields that hold the score and tier. For Marketo Engage, your administrator creates the API-Only user, its role and the custom service, and names the lookup field.",
        "The connection is available and is activated for each client on request. Public documentation establishes what the Adobe APIs support; your licensed products, your agreements with Adobe and your agreement with HiveSilo determine the scope that is switched on."
      ],
      "sourceIds": [
        "P708-D04",
        "P708-D06",
        "P708-D08",
        "HS10"
      ]
    },
    "faqs": [
      {
        "question": "Does HiveSilo connect to Adobe Experience?",
        "answer": "Yes. The Adobe Experience connection is available and is activated for each client on request. It covers Adobe Experience Platform with Real-Time CDP, and Marketo Engage, using Adobe's documented APIs with access your administrators grant.",
        "sourceIds": [
          "P708-D02",
          "P708-D07",
          "HS2"
        ]
      },
      {
        "question": "Which Adobe Experience products and objects are in scope?",
        "answer": "Adobe Experience Platform and Real-Time CDP: profile records streamed to an HTTP API source connection, in fields of your own schema. Marketo Engage: leads, their standard and custom fields, program attribution through Push Lead, and custom activities. Other Adobe Experience products and objects are agreed for each client and are not described here.",
        "sourceIds": [
          "P708-D03",
          "P708-D04",
          "P708-D07",
          "P708-D17"
        ]
      },
      {
        "question": "Can the Adobe connection be tested before production?",
        "answer": "Yes, in Adobe Experience Platform. Your team creates the HTTP API streaming connection in a development sandbox, which Adobe documents for development and testing with non-production profiles, and HiveSilo posts records to the endpoint URL it returns. The syncValidation parameter gives immediate feedback on a record, at up to 60 requests per minute.",
        "sourceIds": [
          "P708-D02",
          "P708-D04",
          "P708-D12"
        ]
      },
      {
        "question": "Will it create duplicate leads in Marketo Engage?",
        "answer": "The Leads call uses the createOrUpdate action, which Adobe documents as the default, with a lookup field that defaults to email. A lead that matches is updated and one that does not is created. Your own deduplication rules still apply.",
        "sourceIds": [
          "P708-D07"
        ]
      },
      {
        "question": "How is access granted and removed?",
        "answer": "In Adobe Experience Platform, through OAuth Server-to-Server credentials tied to a product profile and permissions a system administrator grants. In Marketo Engage, through a custom service owned by an API-Only user. Both are managed, and can be withdrawn, in your Adobe accounts.",
        "sourceIds": [
          "P708-D05",
          "P708-D08"
        ]
      },
      {
        "question": "Does HiveSilo read data back from Adobe?",
        "answer": "Not in this workflow. HiveSilo writes the score, tier and reason; audiences, journeys and reporting on them stay with your team in Adobe. Reading leads or opportunities would be a separate permission you grant on the Marketo API-Only user. The Marketo token travels in the Authorization header; Adobe removed the access_token query parameter on August 31, 2026.",
        "sourceIds": [
          "P708-D08",
          "P708-D19"
        ]
      },
      {
        "question": "Does it use up our Marketo Engage API quota?",
        "answer": "Each call counts toward your subscription's daily allocation, which Adobe gives as 50,000 calls, and the instance limit of 100 calls per 20 seconds. Capacity is shared by all API services in the instance, so batches of up to 300 records keep the call count down.",
        "sourceIds": [
          "P708-D07",
          "P708-D09",
          "P708-D10"
        ]
      },
      {
        "question": "Is HiveSilo listed in the Adobe Experience Platform catalog?",
        "answer": "No listing or program membership is claimed. Adobe adds productized destinations to its catalog through Destination SDK and its own review. This connection instead sends data into a streaming connection your team creates in your own organization.",
        "sourceIds": [
          "P708-D11"
        ]
      }
    ],
    "relationshipContext": {
      "privacyContext": "The profile's or lead's identity is written to your own Adobe account from the environment you control. HiveSilo's shared platform receives permitted non-PII signals and scores. Adobe product profiles, access control permissions and Marketo roles continue to govern who can read what is written.",
      "diagramLabels": [
        "Customer identities stay in your Adobe organization",
        "Permitted non-PII website signals and buyer scores",
        "HiveSilo: buyer score, tier and reasons"
      ],
      "reviewIntentSentences": [
        "An Adobe Experience review should start with the profiles, audiences, scoring and journeys already configured in your Adobe products.",
        "An Adobe Experience review of the connection should confirm which product is in scope, the schema fields and the permissions the credentials hold.",
        "When you review Adobe Experience with HiveSilo, ask which audience or sales decision a website buyer score would change."
      ],
      "sourceIds": [
        "P708-D04",
        "P708-D05",
        "HS3",
        "HS4"
      ]
    }
  },
  "shared": {
    "privacyModel": "Customer identities and re-identifiable data stay in the customer-controlled environment; only permitted non-PII signals and scores cross the configured boundary. Account, billing and support records are separate.",
    "governanceSteps": [
      {
        "title": "Request",
        "detail": "An AI proposes an action"
      },
      {
        "title": "Check",
        "detail": "Policy and authority"
      },
      {
        "title": "Approve",
        "detail": "Named owner, when required"
      },
      {
        "title": "Act",
        "detail": "Within permitted scope"
      },
      {
        "title": "Record",
        "detail": "Keep the action, outcome and accountable owner traceable."
      }
    ],
    "outcomes": [
      {
        "value": "3,790",
        "prefix": "",
        "suffix": "of 5,000",
        "label": "UHNW buyer score",
        "note": "Illustrative score"
      },
      {
        "value": "4–6×",
        "prefix": "",
        "suffix": "",
        "label": "Reported conversion lift",
        "note": "Closed-revenue outcomes"
      },
      {
        "value": "31%",
        "prefix": "Up to",
        "suffix": "",
        "label": "Reported ad-spend savings",
        "note": "Bot and invalid-traffic filtering"
      },
      {
        "value": "99.9999%",
        "prefix": "",
        "suffix": "",
        "label": "Bot detection",
        "note": "Observed client results"
      },
      {
        "value": "5–21%",
        "prefix": "",
        "suffix": "",
        "label": "Revenue lift from existing data",
        "note": "HiveSilo-reported client results"
      }
    ],
    "outcomeContext": "Published outcomes include client-reported results and illustrative, unaudited ranges. The owned-data revenue range was supplied by HiveSilo; request the measurement context in your briefing. Results vary.",
    "botDetectionGoal": "99.9999999% is a goal, not an achieved result."
  },
  "sources": [
    {
      "id": "P708-D01",
      "title": "Adobe Experience Platform: Streaming Ingestion Overview",
      "url": "https://experienceleague.adobe.com/en/docs/experience-platform/ingestion/streaming/overview",
      "supports": "Streaming ingestion lets users stream profile records and ExperienceEvents to Experience Platform; guidance is 1000 requests per second, or 10000 individual messages per second; the enforced limit becomes 60 requests per minute when using synchronous validation; guardrails are bound to the organization's license usage entitlement.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P708-D02",
      "title": "Adobe Experience Platform: Stream Record Data Using Streaming Ingestion APIs",
      "url": "https://experienceleague.adobe.com/en/docs/experience-platform/ingestion/tutorials/streaming-record-data",
      "supports": "Record data is sent with POST /collection/{CONNECTION_ID} on https://dcs.adobedc.net, with an optional syncValidation=true query parameter that Adobe describes as intended for development purposes and rate limited to 60 times per minute per CONNECTION_ID; the body names the schema in schemaRef and carries the record in xdmEntity; the tutorial builds the schema on the XDM Individual Profile class.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P708-D03",
      "title": "Adobe Experience Platform: HTTP API Source Connector Overview",
      "url": "https://experienceleague.adobe.com/en/docs/experience-platform/sources/connectors/streaming/http",
      "supports": "The HTTP API source connector streams data to Experience Platform and is supported by Data Prep functions, which map non XDM-compliant data to an XDM-compliant dataset.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P708-D04",
      "title": "Adobe Experience Platform: Create an HTTP API Streaming Connection Using the Flow Service API",
      "url": "https://experienceleague.adobe.com/en/docs/experience-platform/sources/api-tutorials/create/streaming/http",
      "supports": "POST /flowservice/connections on https://platform.adobe.io/data/foundation creates the streaming connection; dataType supports xdm and raw; setting authenticationRequired to true creates an authenticated connection, which Adobe says users sending Personally Identifiable Information should create; the streaming endpoint URL is returned as inletUrl; an authenticated connection rejects a missing or expired Authorization header with HTTP 401.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P708-D05",
      "title": "Adobe Experience Platform: Authenticate and Access Experience Platform APIs",
      "url": "https://experienceleague.adobe.com/en/docs/experience-platform/landing/platform-apis/api-authentication",
      "supports": "OAuth Server-to-Server is the only token generation method supported moving forward and the Service Account (JWT) method is deprecated; calls carry Authorization: Bearer, x-api-key and x-gw-ims-org-id; a new access token must be generated every 24 hours; the account needs developer and user permissions for an Experience Platform product profile, and a system administrator grants attribute-based access control permissions.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P708-D06",
      "title": "Adobe Experience Platform: Getting Started with the Schema Registry API",
      "url": "https://experienceleague.adobe.com/en/docs/experience-platform/xdm/api/getting-started",
      "supports": "The TENANT_ID ensures that resources an organization creates are namespaced properly and contained within that organization; Schema Registry calls use the x-sandbox-name header and https://platform.adobe.io/data/foundation/schemaregistry paths.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P708-D07",
      "title": "Adobe Marketo Engage Developer Guide: Leads",
      "url": "https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/rest/lead-database/leads",
      "supports": "POST /rest/v1/leads.json creates or updates up to 300 records per request; action accepts createOrUpdate, createOnly, updateOnly or createDuplicate and defaults to createOrUpdate; lookupField defaults to email; the lead object has standard fields and optional custom fields; POST /rest/v1/leads/push.json requires programName and input and accepts optional source and reason; leads are read with GET /rest/v1/leads.json and a filterType.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P708-D08",
      "title": "Adobe Marketo Engage Developer Guide: Authentication",
      "url": "https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/rest/authentication",
      "supports": "Marketo REST APIs use 2-legged OAuth 2.0; a custom service that belongs to an API-Only user provides the Client ID and Client Secret; a new access token has a lifespan of 3,600 seconds; support for the access_token query parameter was removed on August 31, 2026 and the Authorization header is to be used.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P708-D09",
      "title": "Adobe Marketo Engage Developer Guide: REST API",
      "url": "https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/rest/rest-api",
      "supports": "Each subscription is allocated 50,000 API calls per day; each instance is limited to 100 API calls per 20 seconds and ten concurrent API calls; standard calls have a maximum body size of 1 MB; the SOAP API is deprecated as of July 31st, 2026; an API Only user is given a role and attached to a Custom service in LaunchPoint.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P708-D10",
      "title": "Adobe Marketo Engage Developer Guide: Marketo Integration Best Practices",
      "url": "https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/rest/marketo-integration-best-practices",
      "supports": "API quota, rate and concurrency capacity is shared by all API services and users in an instance; exceeding the rate limit returns error code 606; Adobe suggests each third-party integration stay at 50 calls per 20 seconds or fewer and batch records into as few calls as possible.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P708-D11",
      "title": "Adobe Experience Platform: Destination SDK Overview",
      "url": "https://experienceleague.adobe.com/en/docs/experience-platform/destinations/destination-sdk/overview",
      "supports": "Destination SDK is how a productized destination is added to the Experience Platform catalog, with access through the Adobe Technology Partner Program and submission for Adobe's review. HiveSilo does not claim a catalog listing.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P708-D12",
      "title": "Adobe Experience Platform: Sandboxes Overview",
      "url": "https://experienceleague.adobe.com/en/docs/experience-platform/sandbox/home",
      "supports": "Sandboxes partition a single Experience Platform instance into separate virtual environments; a development sandbox can be used exclusively for development and testing with non-production profiles; API calls name the sandbox in the x-sandbox-name header; access to non-production sandboxes is granted through the Adobe Admin Console.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P708-D13",
      "title": "Adobe Experience Platform: Audit Logs Overview",
      "url": "https://experienceleague.adobe.com/en/docs/experience-platform/landing/governance-privacy-security/audit-logs/overview",
      "supports": "Audit logs record who performed what action and when, for resources including datasets, destinations and sandboxes; viewing and exporting them needs the View User Activity Log access control permission; logs are retained for 365 days.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P708-D14",
      "title": "Adobe Experience Platform: Segmentation Service Overview",
      "url": "https://experienceleague.adobe.com/en/docs/experience-platform/segmentation/home",
      "supports": "Segmentation Service creates audiences through segment definitions or other sources from Real-Time Customer Profile data; supported evaluation methods are streaming segmentation, batch segmentation and edge segmentation.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P708-D15",
      "title": "Adobe Experience Platform: Destinations Overview",
      "url": "https://experienceleague.adobe.com/en/docs/experience-platform/destinations/home",
      "supports": "Destinations are pre-built integrations that send audiences or datasets from Experience Platform to marketing automation platforms, digital advertising platforms and more; activating them is governed by access control permissions such as View Destinations.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P708-D16",
      "title": "Adobe Experience Platform: Data Governance Overview",
      "url": "https://experienceleague.adobe.com/en/docs/experience-platform/data-governance/home",
      "supports": "Data Governance has three elements, Labels, Policies and Enforcement; data usage labels are applied at the schema field level, including Identity \"I\" labels for data that can identify or contact a specific person; data usage policies describe which marketing actions are allowed on labeled data.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P708-D17",
      "title": "Adobe Marketo Engage Developer Guide: Activities",
      "url": "https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/rest/lead-database/activities",
      "supports": "POST /rest/v1/activities/external.json adds custom activities to lead records, up to 300 activity records at a time; a custom activity type must be approved before records are added; maximum 10 custom activities and 20 attributes each; an approved type gets a corresponding Smart List trigger and filter.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P708-D18",
      "title": "Adobe Marketo Engage Developer Guide: Smart Campaigns",
      "url": "https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/rest/assets/smart-campaigns",
      "supports": "POST /rest/v1/campaigns/{id}/trigger.json (Request Campaign) passes leads through a trigger campaign whose flow uses a Campaign is Requested trigger with Web Service API as its source; each call accepts a maximum of 100 leads.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P708-D19",
      "title": "Adobe Marketo Engage Developer Guide: Opportunities",
      "url": "https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/rest/lead-database/opportunities",
      "supports": "Marketo provides APIs for reading and writing opportunity records, queried with GET /rest/v1/opportunities.json; the Opportunity Role object links opportunities to leads; Opportunity APIs are read-only for subscriptions with SFDC Sync or Microsoft Dynamics Sync enabled.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "HSF1",
      "title": "HiveSilo capability overview",
      "url": "https://hivesilo.com/evidence/features.md",
      "supports": "Published HiveSilo capabilities: buyer intelligence with Tier 1, Tier 2 and Tier 3 qualification, Revenue Seeker, AdBrain, offline conversion feedback, AI Governance & Control, bot defense, business insights and client-controlled privacy; typical deployment of approximately 72 hours to set up and 7 days to go-live, subject to fit, readiness and scope.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "HS0",
      "title": "HiveSilo: industry coverage",
      "url": "https://hivesilo.com",
      "supports": "First-party description of buyer intelligence across 12 luxury niches.",
      "reviewed": "2026-10-25"
    },
    {
      "id": "HS1",
      "title": "HiveSilo: platform",
      "url": "https://hivesilo.com/platform",
      "supports": "Published intent, sales-prioritization and traffic-quality capabilities.",
      "reviewed": "2026-10-25"
    },
    {
      "id": "HS2",
      "title": "HiveSilo: integration scope",
      "url": "https://hivesilo.com/integrations",
      "supports": "Named destinations, scoped activation and customer-controlled dispatch.",
      "reviewed": "2026-10-25"
    },
    {
      "id": "HS3",
      "title": "HiveSilo: security architecture",
      "url": "https://hivesilo.com/security-architecture",
      "supports": "Documented confidential processing, BYOK and customer control.",
      "reviewed": "2026-10-25"
    },
    {
      "id": "HS4",
      "title": "HiveSilo: data handling",
      "url": "https://hivesilo.com/data-handling",
      "supports": "Customer identity custody, pseudonymous-data boundaries and separate account records.",
      "reviewed": "2026-10-25"
    },
    {
      "id": "HS5",
      "title": "HiveSilo: published outcomes",
      "url": "https://hivesilo.com/case-studies",
      "supports": "Existing first-party outcomes material, with client-reported and illustrative descriptions.",
      "reviewed": "2026-10-25"
    },
    {
      "id": "HS6",
      "title": "HiveSilo: AI agentic governance",
      "url": "https://hivesilo.com/ai-agentic-governance",
      "supports": "Published pre-action policy checks, default denial, human checkpoints, scoped stop controls and governance receipts.",
      "reviewed": "2026-10-25"
    },
    {
      "id": "HS7",
      "title": "HiveSilo: AI implementation layer",
      "url": "https://hivesilo.com/ai-implementation-layer",
      "supports": "Published combined implementation model for intelligence, confidential processing and AI governance.",
      "reviewed": "2026-10-25"
    },
    {
      "id": "HS8",
      "title": "HiveSilo: bot-detection results and buyer-score specimen",
      "url": "https://hivesilo.com/",
      "supports": "The homepage presents 99.9999% bot detection as observed client results, 99.9999999% as a goal, and a 3,790-of-5,000 UHNW buyer-score specimen.",
      "reviewed": "2026-10-25"
    },
    {
      "id": "HS9",
      "title": "HiveSilo: owned-data revenue result briefing",
      "url": "https://hivesilo.com/contact",
      "supports": "HiveSilo supplied a 5–21% client revenue increase range for existing-data workflows on 25 October 2026.",
      "reviewed": "2026-10-25"
    },
    {
      "id": "HS10",
      "title": "HiveSilo: enterprise agreements and responsibility",
      "url": "https://hivesilo.com/terms",
      "supports": "Signed enterprise agreements govern the engagement and take precedence over website summaries.",
      "reviewed": "2026-10-26"
    }
  ],
  "articleText": "Enterprise CRM & customer data Adobe Experience + HiveSilo Available View scope HiveSilo / Integrations / Adobe Experience Adobe Experience. Give your profiles a first-party buyer score. Adobe Experience is a family of products. This page covers Adobe Experience Platform with Real-Time CDP, and Marketo Engage. HiveSilo scores the buyers on your own website and sends that evidence to them through the APIs Adobe documents. Contact HiveSilo Explore the fit Start with a conversation. No client records needed. Your Adobe customer profile. A buyer score from your own site. Your client list stays yours. The value AI control Your data What you could gain Let’s talk FAQs & evidence A profile updates. Does it show a buyer? Adobe Experience brings your customer data together and acts on it. A score for how seriously someone was buying on your website has to come from somewhere. What should a profile or a lead say about buying intent? An enquiry adds a person to Marketo Engage or updates a profile in Adobe Experience Platform with a name, an email address and a source. Two records can look alike while one person shows strong buying intent and the other was never a real buyer. The teams that build audiences and follow up decide what to do with the context the record carries. Adobe provides its own profile, audience, scoring and journey tools, and those remain the starting point. HiveSilo adds one more input: first-party behavior on your own website, scored for buying intent and screened for invalid traffic, then sent to the schema fields and lead fields your administrator chooses. An Adobe Experience review should start with the profiles, audiences, scoring and journeys already configured in your Adobe products. [P708-D04] [P708-D05] [HS3] [HS4] Feed buyer evidence into the Adobe tools you already run. HiveSilo does not replace an Adobe audience, journey or scoring model. It supplies a score, a tier and the reasons behind them as data those tools can use. Talk through your use case Who belongs in the audience. Use observed buying intent as one more attribute when your team defines who to reach. Who sales should call. Give Marketo Engage a current buyer score and tier on the lead before hand-off. What to stop paying for. See which sources send buyers and which send traffic that never becomes a conversation. Available The connection is activated for each client on request, inside that client's own Adobe Experience Platform organization and sandbox or Marketo Engage instance, with the schemas, fields and permissions their administrator approves. How HiveSilo connects to Adobe Experience Adobe Experience brings your customer data together and acts on it. HiveSilo scores buying intent on your own website, screens invalid traffic and sends a Tier 1, Tier 2 or Tier 3 qualification to Adobe Experience Platform profiles, for Real-Time CDP, by streaming ingestion, and to Marketo Engage leads by REST API, under access your administrators grant. Customer identities stay in your Adobe organization and your own confidential environment. [P708-D02] [P708-D07] [HSF1] [HS4] What your team sees on the Marketo Engage lead Source Website HiveSilo buyer score (custom field) 3,790 of 5,000 HiveSilo qualification (custom field) Tier 1 Traffic check (custom field) Screened as genuine Custom activity on the lead Tier 1 buying intent on the website Strong buying intent on your website this week. Traffic screened as genuine. Suggested next step: pass to sales today. Illustrative example, not an Adobe screen. Field and activity names are chosen by your administrator. The score shown is HiveSilo's published specimen. [HS8] What HiveSilo sends and the route Adobe Experience documents Adobe Experience is a product family, so each row names the product it covers and a page in Adobe's public documentation. HiveSilo calls the Adobe API outbound to write these records; it does not ask Adobe to call into your systems. In this workflow it does not read profiles, audiences, leads or opportunities back from Adobe; any read is a separate permission you would grant. Adobe Experience Platform and Real-Time CDP are covered by the same streaming ingestion route. What HiveSilo sends to Adobe Experience Platform, Real-Time CDP and Marketo Engage, and the documented route for each item HiveSilo sends Where it lands in Adobe Experience Documented route A buyer who identifies themselves on your website Adobe Experience Platform and Real-Time CDP: a profile record in your dataset POST to the streaming endpoint of your HTTP API connection, https://dcs.adobedc.net/collection/{CONNECTION_ID}. The body names your schema in schemaRef and carries the record in xdmEntity. [P708-D02] [P708-D04] Buyer score, Tier 1, Tier 2 or Tier 3 qualification, campaign and source context Adobe Experience Platform: fields in your own XDM schema Fields your team defines through the Schema Registry, namespaced by your TENANT_ID. As an alternative, a raw connection lets Data Prep map incoming fields to your schema. [P708-D03] [P708-D04] [P708-D06] A scored lead for marketing and sales Marketo Engage: a lead, created or updated POST /rest/v1/leads.json with action createOrUpdate, which is the default, and a lookupField that defaults to email. Up to 300 records per request. [P708-D07] A short reason for the score and a suggested next step Marketo Engage: standard or custom fields on the lead The same Leads request body. Adobe documents that the lead object holds standard fields and optional custom fields that users create as needed. [P708-D07] A dated record of a high-intent visit Marketo Engage: a custom activity on the lead POST /rest/v1/activities/external.json, up to 300 activity records per call. Your team creates and approves the custom activity type first; Adobe allows a maximum of 10 custom activities. [P708-D17] A scored lead tied to a campaign Marketo Engage: a lead with activity attributed to a named program POST /rest/v1/leads/push.json with the required programName and input, and optional source and reason strings. [P708-D07] Access you grant in Adobe Experience Platform Platform API calls use OAuth Server-to-Server credentials from Adobe Developer Console, tied to an Experience Platform product profile, with permissions a system administrator grants. A new access token is generated every 24 hours. Adobe says data with personal information should use an authenticated streaming connection. [P708-D04] [P708-D05] Access you grant in Marketo Engage A custom service that belongs to an API-Only user provides the Client ID and Client Secret. That user's roles and permissions set what the service may do. An access token lasts 3,600 seconds. [P708-D08] [P708-D09] Limits to plan for Marketo Engage: 50,000 API calls per day per subscription, 100 calls per 20 seconds and ten concurrent calls per instance, shared with your other integrations. Adobe Experience Platform streaming: guidance of 1000 requests per second, and 60 requests per minute with synchronous validation. [P708-D01] [P708-D09] [P708-D10] Deprecations to know Marketo Engage removed support for the access_token query parameter in August 2026; the token goes in the Authorization header, which is the route used. Adobe also lists the Marketo SOAP API and the Experience Platform JWT credential method as deprecated. [P708-D05] [P708-D08] [P708-D09] Control stays with you The streaming connection, the schema, the product profile and the Marketo API-Only user all live in your Adobe accounts. Your administrators decide what the integration may write and can change or remove that access. [P708-D04] [P708-D05] [P708-D08] Where each HiveSilo capability meets Adobe Experience Each row pairs a published HiveSilo capability with the Adobe feature it works with, and names the Adobe product. Scope is agreed for each client. Rows that read from Adobe need a separate permission from your administrators. Where each HiveSilo capability meets Adobe Experience HiveSilo capability Adobe Experience feature it works with What you gain Buyer intelligence and three-tier qualification Adobe Experience Platform: fields in your own XDM Individual Profile schema. Marketo Engage: standard and custom lead fields Audience builders and lead owners see a buyer score and a Tier 1, Tier 2 or Tier 3 qualification on the profile or lead they already use. [P708-D02] [P708-D06] [P708-D07] [HSF1] AI firewall, bot defense and site protection Marketo Engage: lead creation through the Leads endpoint. Adobe Experience Platform: records sent by streaming ingestion Invalid traffic is screened before it becomes a lead or profile record your programs and audiences have to work. [P708-D01] [P708-D07] [HSF1] AdBrain Real-Time CDP: Segmentation Service audiences built from Real-Time Customer Profile data, and destinations that send audiences to digital advertising platforms Your team can use the qualification field in an audience it defines and activate that audience through destinations it already runs, under Adobe's own permissions and policies. [P708-D14] [P708-D15] [HSF1] Offline conversions, qualified-demand scaling and outcome measurement Marketo Engage: opportunity records and the Opportunity Role object that links them to leads With a read permission you grant, opportunity outcomes can inform the qualified-buyer feedback sent to supported advertising platforms. [P708-D19] [HSF1] Revenue Seeker Marketo Engage: lead records read through the Leads endpoints With a read permission you grant, Marketo Engage can be one of the authorized sources searched for revenue opportunities, which go to your own salespeople. HiveSilo cannot see those records. [P708-D07] [HSF1] AI Governance & Control Marketo Engage: Request Campaign, which only runs a trigger campaign your team built with a Campaign is Requested trigger. Marketo custom activities, which become Smart List triggers and filters Any follow-up a score starts is a campaign your team built and activated, so a person stays in charge of the outreach. [P708-D17] [P708-D18] [HS6] Business insights and oversight Adobe Experience Platform: audit logs, which record who performed what action and when and are retained for 365 days Your administrators can review activity on the datasets and destinations involved, with the View User Activity Log permission. [P708-D13] [HSF1] Client-controlled privacy and verification Adobe Experience Platform: authenticated streaming connections, sandboxes, and Data Governance labels and policies applied at the schema field level Customer identities stay in your Adobe organization and your confidential environment, outside HiveSilo's visibility, and your data stewards decide how the score fields may be used. [P708-D04] [P708-D12] [P708-D16] [HS4] [HSF1] How the buying signals are captured and linked Lightweight first-party instrumentation on your own website reads pseudonymous behavior from your visitors. HiveSilo scores those non-PII signals. Anything that could identify a person travels from your website into your own per-tenant confidential enclave, not into HiveSilo's shared platform. An anonymous session has a score but no Adobe profile or lead. The link is made when the visitor identifies themselves on your website, for example through an enquiry form. That match happens inside your enclave, and the scored profile record or Marketo Engage lead is written to your Adobe account from there. [HS3] [HS4] What your Adobe Experience team does The connection is configuration in your Adobe accounts plus activation on the HiveSilo side. These are the steps on your side. Skip the ones for Adobe products you do not run. Define the schema fields. In Adobe Experience Platform, add the fields for score, tier and reason to your schema through the Schema Registry. They sit in your tenant namespace. [P708-D06] Create the streaming connection. Create an HTTP API streaming connection and note the endpoint URL it returns. Adobe says data with personal information should use an authenticated connection. [P708-D04] Grant Experience Platform access. Create OAuth Server-to-Server credentials in Adobe Developer Console, tied to a product profile, and have a system administrator grant the permissions the dataset needs. [P708-D05] Set up Marketo Engage access. Create an API-Only user with a role limited to the agreed writes, and attach it to a custom service that provides the Client ID and Client Secret. [P708-D08] [P708-D09] Choose the lead fields and any custom activity. Name the lookup field and the lead fields for score and tier. If a custom activity is used, create and approve its type before records are added. [P708-D07] [P708-D17] Test in a development sandbox first. Adobe documents development sandboxes for development and testing with non-production profiles, named in the x-sandbox-name header. The syncValidation query parameter, intended for development purposes, returns immediate feedback on a streamed record. [P708-D12] [P708-D02] Switch on production. Repeat the connection and schema in your production sandbox once the development result is accepted. [P708-D04] [P708-D12] HiveSilo's published typical deployment is approximately 72 hours to set up and 7 days to live mapping and go-live, subject to fit, customer readiness and agreed scope. The Adobe steps above run on your own change process. [HSF1] Who, what, when, where, how and why Who Enterprises that run Adobe Experience Platform, Real-Time CDP or Marketo Engage and want those teams to see buying intent from the company website. Your Adobe administrators grant the access. [P708-D05] [P708-D08] What A scored lead or profile record, a buyer score, an intent tier, a short reason for them, a suggested next step, and campaign and source context. [P708-D02] [P708-D07] When When a visitor identifies themselves on your website, for example through an enquiry form, and again when a returning buyer's score changes. [HS1] Where In your own Adobe organization and sandbox, or your own Marketo Engage instance, in the dataset or on the lead your teams already use. [P708-D04] [P708-D07] [HS4] How Outbound calls to Adobe's documented APIs: streaming ingestion to an HTTP API connection you create, and the Marketo Engage Leads REST endpoints with a Bearer token in the Authorization header. [P708-D02] [P708-D07] [P708-D08] Why Adobe brings your customer data together and acts on it. HiveSilo knows how the buyer behaved on your website before the enquiry. Together your teams work from both. [HS1] [HS2] See the intelligence behind the next move Profile records, streamed to your connection. Your team creates an HTTP API streaming connection in Adobe Experience Platform. HiveSilo posts records to the endpoint that connection returns. The fields that hold the score sit in your own schema, in your tenant namespace. [P708-D02] [P708-D04] [P708-D06] Useful output: A profile record carrying a buyer score and intent tier in fields you define. A Marketo Engage lead, created or updated. HiveSilo sends leads to the Marketo Engage Leads endpoint with the createOrUpdate action, matched on the lookup field you choose. Adobe documents that one request can create or update up to 300 records. [P708-D07] Useful output: One lead per buyer, with score and tier in standard or custom fields. Mapping on your side, if you prefer. Adobe documents a raw data type for the HTTP API source, with Data Prep functions that map incoming data to an XDM-compliant dataset. Your team can keep the mapping inside Adobe Experience Platform. [P708-D03] [P708-D04] Useful output: Scored records mapped to your schema by rules your team owns. Two new leads. One nurture program. Who goes to sales? Illustrative workflow: two people fill in the same form on one morning and both become leads in Marketo Engage. One shows strong buying intent and is qualified Tier 1; the other shows little and is Tier 3. Start with Adobe Experience Marketo Engage stores both leads and runs the programs and scoring your team has configured. That process stays as it is. Bring the relevant context together The lead as it exists in Marketo Engage, with its program and source. HiveSilo's score and Tier 1, Tier 2 or Tier 3 qualification for the website sessions behind each enquiry, in the fields your administrator chose. A short reason for each score, including any invalid-traffic concern. Make the decision The team passes the Tier 1 buyer to sales and leaves the second lead in the standard program. A useful output Two leads whose fields show HiveSilo's score and tier, available to the rules and views your team builds. Keep responsibility clear Your marketing operations team owns the programs and the hand-off rule, and the lead owner decides the outreach. HiveSilo supplies evidence; it does not send messages on their behalf in this workflow. Hold and ask Hold automated outreach when the score is low, the traffic-quality concern is unresolved or contact permission is unclear. Record the outcome Your team records the outcome in Marketo Engage as usual, so your own reporting can compare score with result. HiveSilo does not read that outcome back in this workflow. [P708-D07] Require control before AI acts. A score informs your team. It does not act for them. Decide in advance which Adobe actions a score may start and which need a person. Writing a field is different from adding someone to an audience or pushing a lead into a program. Keep the Marketo API-Only user's role limited to the agreed writes, grant the Experience Platform credential only the permissions the dataset needs, and route anything outside that scope to the named owner first. 1 Request An AI proposes an action 2 Check Policy and authority 3 Approve Named owner, when required 4 Act Within permitted scope 5 Record Keep the action, outcome and accountable owner traceable. Unclear authority? Hold the action. Resolve with the named, authorized owner before proceeding. Controls apply to actions routed through the configured HiveSilo boundary. Read the governance and escalation requirements Make accountable authorization a condition of putting AI to work. HiveSilo describes an operating layer that combines buyer intelligence, customer-data privacy and governance. Your deployment should establish the responsible owner and permitted scope before an agent can change records, contact buyers or trigger campaigns. HiveSilo documents policy checks before execution, default denial when authorization is unclear, human checkpoints, scoped stop controls and decision receipts. These controls apply to actions routed through its policy boundary. Keep decisions, required approvals and held actions traceable as the workflow progresses, then record the action, outcome and accountable owner. [HS6] [HS7] Who Identify the acting agent or person and name the business owner accountable for this workflow. What Define the action and permitted data categories before execution. Where Specify the approved system, destination and customer custody boundary. How Require an approved execution path, access scope and applicable policy checks. When Set the permitted conditions and approval validity; recheck authority before a held action resumes. Why Record the business purpose and the basis for allowing, denying or holding the action. An edge case should stop the affected action. For the deployment, require unresolved authority, an unapproved destination or an out-of-policy action to remain on hold. A timeout or unanswered approval request must not become permission to proceed. Who gets the question? Agree a named owner and authorized delegate for each workflow. A proposed responsibility model is: sales for buyer outreach and lead handling; marketing for campaign spend and audiences; security or privacy for data-access exceptions; the platform owner for connector or runtime changes. Test the escalation route. If no authorized reviewer is available, keep the action held. Named-owner routing is configured and demonstrated for each deployment. Governance covers actions routed through its configured boundary; external systems remain responsible for actions outside that scope. Make responsibility part of the AI rollout. Use the AI implementation layer to put policy checks, approval checkpoints and decision records around the actions in scope. Your enterprise agreement defines the legal responsibilities and any agreed liability allocation or transfer. [HS7] [HS10] Explore the AI implementation layer · How enterprise agreements govern the engagement Your client list stays yours. Your Adobe customer profile stays in your Adobe organization. Explore the security architecture Your client records stay with your business under HiveSilo’s published architecture. How your data stays under your control The profile's or lead's identity is written to your own Adobe account from the environment you control. HiveSilo's shared platform receives permitted non-PII signals and scores. Adobe product profiles, access control permissions and Marketo roles continue to govern who can read what is written. [P708-D04] [P708-D05] [HS3] [HS4] [HS4] Your controlled environment Customer identities stay in your Adobe organization Identities and re-identifiable records stay here. Your enclave. Your keys. Only permitted non-PII signals and scores Permitted non-PII website signals and buyer scores HiveSilo intelligence HiveSilo: buyer score, tier and reasons No customer identity transfer to HiveSilo. Published architecture. Confirm the data boundary for your deployment. Customer-controlled keys Documented BYOK options cover AWS, Azure and GCP. Review key ownership, revocation and the deployment's access policy with your security team. [HS3] Protected processing The architecture describes confidential computing and trusted execution environments. Request deployment-specific attestation and data-flow evidence for your CISO's review. [HS3] Scoped destinations and actions Agree which systems receive outputs and what actions are authorized. Keep identity handling within the documented customer boundary. [HS2] [HS4] Control through the full relationship Review permitted use, export, retention, deletion and offboarding terms. Customer-controlled keys are one control; they do not establish every contractual exit right. [HS3] [HS4] The profile's or lead's identity is written to your own Adobe account from the environment you control. HiveSilo's shared platform works with permitted non-PII signals and scores. Adobe recommends an authenticated streaming connection for data that includes personal information, your schema sets which fields exist, and Adobe's own permissions continue to apply to everyone who reads them. An Adobe Experience review of the connection should confirm which product is in scope, the schema fields and the permissions the credentials hold. [P708-D04] [P708-D05] [HS3] [HS4] Customer identity custody is separate from HiveSilo account, billing and support records. Re-identifiable pseudonymous data is not anonymous. What you could gain. Bring website buying evidence to the Adobe Experience profile and the Marketo Engage lead, so the audience, the hand-off and the source review start from the same facts. Explore HiveSilo case studies Contact HiveSilo Select a benefit to explore Pause rotation Buyer scoring Scale winners Less waste Bot protection Find revenue 3,790 of 5,000 · UHNW buyer score 3 , 7 9 0 of 5,000 Illustrative score 4–6× · Reported conversion lift 4 – 6 × Closed-revenue outcomes Up to 31% · Reported ad-spend savings Up to 3 1 % Bot and invalid-traffic filtering 99.9999% · Bot detection 9 9 . 9 9 9 9 % Observed client results 5–21% · Revenue lift from existing data 5 – 2 1 % HiveSilo-reported client results Sharper scoring. Clearer intent. 3,790 of 5,000 · UHNW buyer score Illustrative score Rank Marketo Engage leads and Adobe Experience Platform profiles by observed buying intent. Find more clients like your best. 4–6× · Reported conversion lift Closed-revenue outcomes Find the sources and pages your strongest Adobe Experience profiles have in common, then do more of that. Put more of your budget to work. Up to 31% · Reported ad-spend savings Bot and invalid-traffic filtering Review spend on sources whose leads score low and rarely progress in Marketo Engage. Keep evolving your protection. 99.9999% · Bot detection Observed client results Screen invalid traffic before it becomes a lead or profile your Adobe programs have to work. Goal, not an achieved result: toward 99.9999999% bot detection as the hive evolves. Observed client results vary. Find revenue in data you already own. 5–21% · Revenue lift from existing data HiveSilo-reported client results Revisit existing Adobe profiles and leads whose website behavior shows renewed interest. Published outcomes include client-reported results and illustrative, unaudited ranges. The owned-data revenue range was supplied by HiveSilo; request the measurement context in your briefing. Results vary. Measure what matters Define the result. Then require the evidence. Focus on better-directed follow-up, less acquisition waste, protected customer identity custody and accountable AI execution. Agree the baseline, success measures and scope for your business. CEO: a clearer decision about the opportunities that merit attention. CFO: an agreed baseline, evaluation costs and attributable outcomes before any ROI claim. CTO: a demonstrated, permitted connection and a usable handoff into the agreed system. CISO: verified identity custody and pre-action authorization, with tested hold, approval and revocation behavior. Explore HiveSilo’s published outcomes and the measurement context behind them. [HS5] [HS8] [HS9] Make your next conversation count. Bring your Adobe Experience workflow. Map the decision, the data you control and a measurable next step with HiveSilo. Enterprise CRM & customer data · Sales, marketing operations, technology & security Contact HiveSilo Mention Adobe Experience and your business question. No client records or credentials. A closer look, when you need it. Product scope, a practical workflow and source-backed answers for your team and its research tools. Read fact sheet Structured JSON RSS updates Reviewed November 2026 Contact HiveSilo Adobe Experience connection & briefing scope Agree the Adobe product, the schema and the access. Confirm which Adobe Experience product is the target: Adobe Experience Platform with Real-Time CDP, Marketo Engage, or both. For Experience Platform, your team creates the HTTP API streaming connection and the schema fields that hold the score and tier. For Marketo Engage, your administrator creates the API-Only user, its role and the custom service, and names the lookup field. The connection is available and is activated for each client on request. Public documentation establishes what the Adobe APIs support; your licensed products, your agreements with Adobe and your agreement with HiveSilo determine the scope that is switched on. When you review Adobe Experience with HiveSilo, ask which audience or sales decision a website buyer score would change. [P708-D04] [P708-D05] [HS3] [HS4] [P708-D04] [P708-D06] [P708-D08] [HS10] A useful fit when Most useful where Adobe Experience Platform or Marketo Engage is where customer data is acted on and the website is a material source of leads. Enterprises that build audiences in Real-Time CDP and want a first-party intent attribute. Marketing operations teams that hand leads from Marketo Engage to sales. Teams able to name the schema fields, the lead fields and the decision a score should inform. Consider the fit Adobe's own scoring, audience and journey tools may already answer the question for some teams. Adobe Experience Platform fields must exist in your schema before a record can carry them. The Marketo Engage daily quota and rate limit are shared with your other integrations. Adobe Experience covers more products than those named here. Ask about any other product before assuming it is in scope. In your enquiry, name Adobe Experience and the business decision. Please leave out client records, credentials and sensitive samples. Eight questions before your briefing 1. Does HiveSilo connect to Adobe Experience? Yes. The Adobe Experience connection is available and is activated for each client on request. It covers Adobe Experience Platform with Real-Time CDP, and Marketo Engage, using Adobe's documented APIs with access your administrators grant. [P708-D02] [P708-D07] [HS2] 2. Which Adobe Experience products and objects are in scope? Adobe Experience Platform and Real-Time CDP: profile records streamed to an HTTP API source connection, in fields of your own schema. Marketo Engage: leads, their standard and custom fields, program attribution through Push Lead, and custom activities. Other Adobe Experience products and objects are agreed for each client and are not described here. [P708-D03] [P708-D04] [P708-D07] [P708-D17] 3. Can the Adobe connection be tested before production? Yes, in Adobe Experience Platform. Your team creates the HTTP API streaming connection in a development sandbox, which Adobe documents for development and testing with non-production profiles, and HiveSilo posts records to the endpoint URL it returns. The syncValidation parameter gives immediate feedback on a record, at up to 60 requests per minute. [P708-D02] [P708-D04] [P708-D12] 4. Will it create duplicate leads in Marketo Engage? The Leads call uses the createOrUpdate action, which Adobe documents as the default, with a lookup field that defaults to email. A lead that matches is updated and one that does not is created. Your own deduplication rules still apply. [P708-D07] 5. How is access granted and removed? In Adobe Experience Platform, through OAuth Server-to-Server credentials tied to a product profile and permissions a system administrator grants. In Marketo Engage, through a custom service owned by an API-Only user. Both are managed, and can be withdrawn, in your Adobe accounts. [P708-D05] [P708-D08] 6. Does HiveSilo read data back from Adobe? Not in this workflow. HiveSilo writes the score, tier and reason; audiences, journeys and reporting on them stay with your team in Adobe. Reading leads or opportunities would be a separate permission you grant on the Marketo API-Only user. The Marketo token travels in the Authorization header; Adobe removed the access_token query parameter in August 2026. [P708-D08] [P708-D19] 7. Does it use up our Marketo Engage API quota? Each call counts toward your subscription's daily allocation, which Adobe gives as 50,000 calls, and the instance limit of 100 calls per 20 seconds. Capacity is shared by all API services in the instance, so batches of up to 300 records keep the call count down. [P708-D07] [P708-D09] [P708-D10] 8. Is HiveSilo listed in the Adobe Experience Platform catalog? No listing or program membership is claimed. Adobe adds productized destinations to its catalog through Destination SDK and its own review. This connection instead sends data into a streaming connection your team creates in your own organization. [P708-D11] Sources, scope & verification Adobe Experience Platform: Streaming Ingestion Overview [P708-D01] Streaming ingestion lets users stream profile records and ExperienceEvents to Experience Platform; guidance is 1000 requests per second, or 10000 individual messages per second; the enforced limit becomes 60 requests per minute when using synchronous validation; guardrails are bound to the organization's license usage entitlement. Reviewed November 2026 Adobe Experience Platform: Stream Record Data Using Streaming Ingestion APIs [P708-D02] Record data is sent with POST /collection/{CONNECTION_ID} on https://dcs.adobedc.net, with an optional syncValidation=true query parameter that Adobe describes as intended for development purposes and rate limited to 60 times per minute per CONNECTION_ID; the body names the schema in schemaRef and carries the record in xdmEntity; the tutorial builds the schema on the XDM Individual Profile class. Reviewed November 2026 Adobe Experience Platform: HTTP API Source Connector Overview [P708-D03] The HTTP API source connector streams data to Experience Platform and is supported by Data Prep functions, which map non XDM-compliant data to an XDM-compliant dataset. Reviewed November 2026 Adobe Experience Platform: Create an HTTP API Streaming Connection Using the Flow Service API [P708-D04] POST /flowservice/connections on https://platform.adobe.io/data/foundation creates the streaming connection; dataType supports xdm and raw; setting authenticationRequired to true creates an authenticated connection, which Adobe says users sending Personally Identifiable Information should create; the streaming endpoint URL is returned as inletUrl; an authenticated connection rejects a missing or expired Authorization header with HTTP 401. Reviewed November 2026 Adobe Experience Platform: Authenticate and Access Experience Platform APIs [P708-D05] OAuth Server-to-Server is the only token generation method supported moving forward and the Service Account (JWT) method is deprecated; calls carry Authorization: Bearer, x-api-key and x-gw-ims-org-id; a new access token must be generated every 24 hours; the account needs developer and user permissions for an Experience Platform product profile, and a system administrator grants attribute-based access control permissions. Reviewed November 2026 Adobe Experience Platform: Getting Started with the Schema Registry API [P708-D06] The TENANT_ID ensures that resources an organization creates are namespaced properly and contained within that organization; Schema Registry calls use the x-sandbox-name header and https://platform.adobe.io/data/foundation/schemaregistry paths. Reviewed November 2026 Adobe Marketo Engage Developer Guide: Leads [P708-D07] POST /rest/v1/leads.json creates or updates up to 300 records per request; action accepts createOrUpdate, createOnly, updateOnly or createDuplicate and defaults to createOrUpdate; lookupField defaults to email; the lead object has standard fields and optional custom fields; POST /rest/v1/leads/push.json requires programName and input and accepts optional source and reason; leads are read with GET /rest/v1/leads.json and a filterType. Reviewed November 2026 Adobe Marketo Engage Developer Guide: Authentication [P708-D08] Marketo REST APIs use 2-legged OAuth 2.0; a custom service that belongs to an API-Only user provides the Client ID and Client Secret; a new access token has a lifespan of 3,600 seconds; support for the access_token query parameter was removed in August 2026 and the Authorization header is to be used. Reviewed November 2026 Adobe Marketo Engage Developer Guide: REST API [P708-D09] Each subscription is allocated 50,000 API calls per day; each instance is limited to 100 API calls per 20 seconds and ten concurrent API calls; standard calls have a maximum body size of 1 MB; the SOAP API is deprecated as of July 31st, 2026; an API Only user is given a role and attached to a Custom service in LaunchPoint. Reviewed November 2026 Adobe Marketo Engage Developer Guide: Marketo Integration Best Practices [P708-D10] API quota, rate and concurrency capacity is shared by all API services and users in an instance; exceeding the rate limit returns error code 606; Adobe suggests each third-party integration stay at 50 calls per 20 seconds or fewer and batch records into as few calls as possible. Reviewed November 2026 Adobe Experience Platform: Destination SDK Overview [P708-D11] Destination SDK is how a productized destination is added to the Experience Platform catalog, with access through the Adobe Technology Partner Program and submission for Adobe's review. HiveSilo does not claim a catalog listing. Reviewed November 2026 Adobe Experience Platform: Sandboxes Overview [P708-D12] Sandboxes partition a single Experience Platform instance into separate virtual environments; a development sandbox can be used exclusively for development and testing with non-production profiles; API calls name the sandbox in the x-sandbox-name header; access to non-production sandboxes is granted through the Adobe Admin Console. Reviewed November 2026 Adobe Experience Platform: Audit Logs Overview [P708-D13] Audit logs record who performed what action and when, for resources including datasets, destinations and sandboxes; viewing and exporting them needs the View User Activity Log access control permission; logs are retained for 365 days. Reviewed November 2026 Adobe Experience Platform: Segmentation Service Overview [P708-D14] Segmentation Service creates audiences through segment definitions or other sources from Real-Time Customer Profile data; supported evaluation methods are streaming segmentation, batch segmentation and edge segmentation. Reviewed November 2026 Adobe Experience Platform: Destinations Overview [P708-D15] Destinations are pre-built integrations that send audiences or datasets from Experience Platform to marketing automation platforms, digital advertising platforms and more; activating them is governed by access control permissions such as View Destinations. Reviewed November 2026 Adobe Experience Platform: Data Governance Overview [P708-D16] Data Governance has three elements, Labels, Policies and Enforcement; data usage labels are applied at the schema field level, including Identity \"I\" labels for data that can identify or contact a specific person; data usage policies describe which marketing actions are allowed on labeled data. Reviewed November 2026 Adobe Marketo Engage Developer Guide: Activities [P708-D17] POST /rest/v1/activities/external.json adds custom activities to lead records, up to 300 activity records at a time; a custom activity type must be approved before records are added; maximum 10 custom activities and 20 attributes each; an approved type gets a corresponding Smart List trigger and filter. Reviewed November 2026 Adobe Marketo Engage Developer Guide: Smart Campaigns [P708-D18] POST /rest/v1/campaigns/{id}/trigger.json (Request Campaign) passes leads through a trigger campaign whose flow uses a Campaign is Requested trigger with Web Service API as its source; each call accepts a maximum of 100 leads. Reviewed November 2026 Adobe Marketo Engage Developer Guide: Opportunities [P708-D19] Marketo provides APIs for reading and writing opportunity records, queried with GET /rest/v1/opportunities.json; the Opportunity Role object links opportunities to leads; Opportunity APIs are read-only for subscriptions with SFDC Sync or Microsoft Dynamics Sync enabled. Reviewed November 2026 HiveSilo capability overview [HSF1] Published HiveSilo capabilities: buyer intelligence with Tier 1, Tier 2 and Tier 3 qualification, Revenue Seeker, AdBrain, offline conversion feedback, AI Governance & Control, bot defense, business insights and client-controlled privacy; typical deployment of approximately 72 hours to set up and 7 days to go-live, subject to fit, readiness and scope. Reviewed November 2026 HiveSilo: industry coverage [HS0] First-party description of buyer intelligence across 12 luxury niches. Reviewed October 2026 HiveSilo: platform [HS1] Published intent, sales-prioritization and traffic-quality capabilities. Reviewed October 2026 HiveSilo: integration scope [HS2] Named destinations, scoped activation and customer-controlled dispatch. Reviewed October 2026 HiveSilo: security architecture [HS3] Documented confidential processing, BYOK and customer control. Reviewed October 2026 HiveSilo: data handling [HS4] Customer identity custody, pseudonymous-data boundaries and separate account records. Reviewed October 2026 HiveSilo: published outcomes [HS5] Existing first-party outcomes material, with client-reported and illustrative descriptions. Reviewed October 2026 HiveSilo: AI agentic governance [HS6] Published pre-action policy checks, default denial, human checkpoints, scoped stop controls and governance receipts. Reviewed October 2026 HiveSilo: AI implementation layer [HS7] Published combined implementation model for intelligence, confidential processing and AI governance. Reviewed October 2026 HiveSilo: bot-detection results and buyer-score specimen [HS8] The homepage presents 99.9999% bot detection as observed client results, 99.9999999% as a goal, and a 3,790-of-5,000 UHNW buyer-score specimen. Reviewed October 2026 HiveSilo: owned-data revenue result briefing [HS9] HiveSilo supplied a 5–21% client revenue increase range for existing-data workflows in October 2026. Reviewed October 2026 HiveSilo: enterprise agreements and responsibility [HS10] Signed enterprise agreements govern the engagement and take precedence over website summaries. Reviewed October 2026 Vendor sources describe their own product. The workflows on this page describe a HiveSilo application, scoped to customer permissions, contracts and the selected product edition. HiveSilo’s reported outcomes retain their original measurement context; the illustrative score and future bot-detection goal are identified in the outcomes section. Independent HiveSilo use-case page. Adobe Experience is identified to explain the workflow; no endorsement, certification or partnership is implied. Your next move starts with a conversation. Contact HiveSilo"
}
