{
  "schemaVersion": "1.2.0",
  "schema": "https://hivesilo.com/evidence/company-fact-sheet.schema.json",
  "slug": "meta",
  "product": "Meta",
  "url": "https://hivesilo.com/integrations/meta",
  "title": "Meta Integration: Conversions API for Qualified Leads | HiveSilo",
  "description": "Meta integration with HiveSilo: qualified-lead events sent to your own dataset through the Conversions API, and exclusion lists as customer-file custom audiences.",
  "reviewed": "2026-11-11",
  "connectionStatus": "available",
  "image": {
    "width": 1800,
    "height": 1195,
    "group": "data",
    "alt": "Illustrative enterprise office at dusk for the Meta integration workflow",
    "heroVariants": [
      {
        "path": "/img/integrations/meta-integration-data-480.854e22807114.webp",
        "width": 480,
        "height": 319,
        "bytes": 21216
      },
      {
        "path": "/img/integrations/meta-integration-data-768.3a4946822424.webp",
        "width": 768,
        "height": 510,
        "bytes": 47770
      },
      {
        "path": "/img/integrations/meta-integration-data-1200.742eae743649.webp",
        "width": 1200,
        "height": 797,
        "bytes": 98032
      },
      {
        "path": "/img/integrations/meta-integration-data-1800.bc95e30e4f11.webp",
        "width": 1800,
        "height": 1195,
        "bytes": 169500
      }
    ],
    "socialImage": {
      "path": "/og/meta-integration-intelligence.6b3b9a66eb54.png",
      "width": 1200,
      "height": 630,
      "bytes": 766527
    },
    "retiredSocialImages": [],
    "sourceSha256": "40f59dc928a0",
    "source": "AI-generated illustrative scene; not a vendor or customer facility",
    "illustrative": true
  },
  "content": {
    "inventoryId": "P729",
    "slug": "meta",
    "product": "Meta",
    "shortName": "Meta",
    "niche": "data-ads-messaging",
    "connectionStatus": "available",
    "reviewed": "2026-11-11",
    "contentVersion": "1.2.0",
    "title": "Meta Integration: Conversions API for Qualified Leads | HiveSilo",
    "description": "Meta integration with HiveSilo: qualified-lead events sent to your own dataset through the Conversions API, and exclusion lists as customer-file custom audiences.",
    "primaryKeyword": "Meta integration",
    "secondaryKeywords": [
      "Meta Conversions API integration",
      "Meta qualified lead events",
      "Meta custom audience exclusion list",
      "Conversions API event deduplication",
      "HiveSilo Meta"
    ],
    "sources": [
      {
        "id": "P729-D01",
        "title": "Meta for Developers: Get started with the Conversions API",
        "url": "https://developers.facebook.com/documentation/ads-commerce/conversions-api/get-started",
        "supports": "The Conversions API needs a Pixel ID, a Meta Business Suite and an access token; a token generated in Events Manager needs no App Review; Meta says third-party providers offering Conversions API functions have different requirements.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P729-D02",
        "title": "Meta for Developers: Using the API - Conversions API",
        "url": "https://developers.facebook.com/documentation/ads-commerce/conversions-api/using-the-api",
        "supports": "Events are sent by POST to https://graph.facebook.com/{API_VERSION}/{PIXEL_ID}/events; up to 1,000 events per request; event_time can be up to 7 days in the past; test_event_code is for testing only; there is no specific rate limit for the Conversions API.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P729-D03",
        "title": "Meta for Developers: Server Event Parameters",
        "url": "https://developers.facebook.com/documentation/ads-commerce/conversions-api/parameters/server-event",
        "supports": "event_name, event_time, user_data and action_source are required; event_source_url is required for website events; event_id is recommended for deduplication; data_processing_options accepts LDU.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P729-D04",
        "title": "Meta for Developers: Customer Information Parameters",
        "url": "https://developers.facebook.com/documentation/ads-commerce/conversions-api/parameters/customer-information-parameters",
        "supports": "em and ph require hashing after normalization; hashing is recommended for external_id; client_ip_address and client_user_agent must not be hashed, and client_user_agent is required for website events.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P729-D05",
        "title": "Meta for Developers: Handling Duplicate Pixel and Conversions API Events",
        "url": "https://developers.facebook.com/documentation/ads-commerce/conversions-api/deduplicate-pixel-and-server-events",
        "supports": "A Pixel eventID must match the server event_id and the event names must match; events are deduplicated only if received within 48 hours of the first event with that event_id.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P729-D06",
        "title": "Meta for Developers: Customer File Custom Audiences",
        "url": "https://developers.facebook.com/documentation/ads-commerce/marketing-api/audiences/guides/custom-audiences",
        "supports": "Audiences are created at act_<AD_ACCOUNT_ID>/customaudiences with subtype CUSTOM and customer_file_source, and filled at /<CUSTOM_AUDIENCE_ID>/users with up to 10,000 users per request, hashed as SHA256; beginning September 2, 2025 audiences suggesting specific health conditions or financial status are flagged, with operation_status 471.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P729-D07",
        "title": "Meta for Developers: Data processing options for US users - Marketing API",
        "url": "https://developers.facebook.com/documentation/ads-commerce/marketing-api/overview/data-processing-options",
        "supports": "Limited Data Use is enabled through data_processing_options with country and state values; for Customer List Custom Audiences it is available only for people in California.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P729-D08",
        "title": "Meta for Developers: Conversions API for CRM integration",
        "url": "https://developers.facebook.com/documentation/ads-commerce/conversions-api/conversion-leads-integration",
        "supports": "The Conversions API can upload down-funnel lead events from a CRM system as a separate integration with different required parameters; Meta says the Conversion Leads performance goal is currently only compatible with Lead Ads (Instant Forms) and lists fit guidelines including at least 200 leads per month and uploads at least once per day.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P729-D09",
        "title": "Meta for Developers: Standard Parameters",
        "url": "https://developers.facebook.com/documentation/ads-commerce/conversions-api/parameters/custom-data",
        "supports": "The value parameter is a numeric monetary amount, required for purchase events or any events that use value optimization; currency must be a valid ISO 4217 code.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P729-D10",
        "title": "Meta for Developers: Ads Insights API",
        "url": "https://developers.facebook.com/documentation/ads-commerce/marketing-api/insights",
        "supports": "The Ads Insights API provides performance data through /insights edges on the ad account, campaign, ad set and ad; access needs an app and the ads_read permission.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "HSF1",
        "title": "HiveSilo capability overview",
        "url": "https://hivesilo.com/evidence/features.md",
        "supports": "Published HiveSilo capabilities relied on here: buyer intelligence with Tier 1, Tier 2 and Tier 3 qualification, AdBrain, offline conversions with qualified-demand scaling and outcome measurement, AI Governance & Control, AI firewall and 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": "Meta. Tell the ad system which leads were real buyers.",
      "lede": "Meta delivers your ads and learns from the events it receives. HiveSilo scores the visitors those ads bring to your own website and sends qualified-lead events to your dataset through the Conversions API Meta documents.",
      "imageLines": [
        "Your ad account and dataset.",
        "An event worth optimizing for."
      ]
    },
    "problem": {
      "heading": "The Pixel saw a lead. Did sales?",
      "summary": "Meta counts the events it receives from your Pixel and your server. It does not see what happened to each enquiry afterwards.",
      "question": "Which event should ad delivery learn from?",
      "paragraphs": [
        "A lead campaign can deliver many form fills at a low cost while few of them become conversations. If the only event Meta receives is the form fill, delivery learns to find more people who fill in forms. The team paying for the campaign wants more people who buy.",
        "Meta provides the Pixel, the Conversions API and its own traffic-quality systems, and those stay in place. HiveSilo adds evidence from your own website: which sessions showed buying intent, which enquiries qualified and which were screened as invalid. That evidence is sent to your dataset as server events, and as a list your team can exclude."
      ]
    },
    "value": {
      "heading": "Give Meta a qualified-lead event to learn from.",
      "summary": "HiveSilo does not run campaigns or set budgets. It supplies qualified-lead events and an exclusion list to the Meta ad account and dataset you own, and your team decides how they are used.",
      "decisions": [
        {
          "title": "What delivery optimizes for.",
          "body": "Offer a qualified-lead event alongside the lead event your Pixel already sends."
        },
        {
          "title": "Who to stop reaching.",
          "body": "Keep a list of enquiries screened as invalid or disqualified for your team to exclude."
        },
        {
          "title": "Which ad sets bring buyers.",
          "body": "Compare ad sets by qualified leads in your own Meta reporting."
        }
      ],
      "capabilities": [
        {
          "heading": "A qualified-lead server event.",
          "body": "When an enquiry qualifies, HiveSilo posts an event to your dataset's events endpoint. Meta requires event_name, event_time, user_data and action_source on every event, and event_source_url for website events.",
          "output": "A server event in Events Manager that marks a qualified lead.",
          "sourceIds": [
            "P729-D02",
            "P729-D03"
          ]
        },
        {
          "heading": "No double counting with your Pixel.",
          "body": "Each event carries an event_id. Meta deduplicates a browser event and a server event when the Pixel eventID matches the server event_id, the event names match and both arrive within 48 hours.",
          "output": "One counted event per customer action.",
          "sourceIds": [
            "P729-D03",
            "P729-D05"
          ]
        },
        {
          "heading": "An exclusion list as a custom audience.",
          "body": "Enquiries screened as invalid or disqualified can be uploaded to a customer-file custom audience in your ad account, hashed as SHA256. Meta documents an audience label, DISQUALIFIED_LEADS, for leads that do not meet your qualification criteria.",
          "output": "A custom audience your team can exclude from ad sets.",
          "sourceIds": [
            "P729-D06"
          ]
        }
      ]
    },
    "integration": {
      "heading": "How HiveSilo connects to Meta",
      "statusNote": "The connection is activated for each client on request, against that client's own Meta dataset and ad account, with the events and audiences their administrator approves.",
      "summary": "Meta delivers your ads and learns from the events it receives. HiveSilo scores visitors on your own website, screens invalid traffic and sends Tier 1, Tier 2 and Tier 3 qualified-lead events to your dataset through the Conversions API, plus exclusion lists as customer-file custom audiences. HiveSilo writes only; reading ad performance needs the ads_read permission, which you grant separately. Customer identities stay in your confidential environment.",
      "summarySourceIds": [
        "P729-D02",
        "P729-D06",
        "P729-D10",
        "HSF1",
        "HS4"
      ],
      "intro": "Every row below names a route in Meta's public developer documentation. HiveSilo calls the API outbound to write events and audience members, with an access token you generate and can withdraw. It does not read your ad performance in this workflow; that would need the ads_read permission, granted separately. It does not ask Meta to call into your systems.",
      "tableCaption": "What HiveSilo sends to Meta and the documented route for each item",
      "columns": [
        "HiveSilo sends",
        "How Meta uses it",
        "Documented route"
      ],
      "flows": [
        {
          "sends": "A qualified-lead event",
          "lands": "A server event on your dataset, shown in Events Manager",
          "route": "POST https://graph.facebook.com/{API_VERSION}/{PIXEL_ID}/events. A request holds up to 1,000 events. Required parameters are event_name, event_time, user_data and action_source.",
          "sourceIds": [
            "P729-D02",
            "P729-D03"
          ]
        },
        {
          "sends": "An event_id shared with your Pixel",
          "lands": "Deduplication of the browser event and the server event",
          "route": "The event_id parameter, matched to the Pixel's eventID with the same event name. Meta deduplicates events received within 48 hours of the first.",
          "sourceIds": [
            "P729-D05"
          ]
        },
        {
          "sends": "Hashed contact identifiers, where you choose to send them",
          "lands": "Customer information Meta uses for matching only",
          "route": "The user_data object. Meta requires em and ph to be normalized and hashed, and says client_ip_address and client_user_agent must not be hashed. The hashing is done in the environment you control.",
          "sourceIds": [
            "P729-D04"
          ]
        },
        {
          "sends": "A list of enquiries screened as invalid or disqualified",
          "lands": "Members of a customer-file custom audience in your ad account",
          "route": "POST to act_<AD_ACCOUNT_ID>/customaudiences with subtype CUSTOM and customer_file_source, then POST to /<CUSTOM_AUDIENCE_ID>/users with up to 10,000 users per request. A DELETE call to the same endpoint removes members.",
          "sourceIds": [
            "P729-D06"
          ]
        },
        {
          "sends": "The data processing choice you have made for US visitors",
          "lands": "Limited Data Use handling of the event or record",
          "route": "The data_processing_options parameter with the value LDU, plus country and state values. For customer-list audiences Meta applies it only to people in California.",
          "sourceIds": [
            "P729-D03",
            "P729-D07"
          ]
        }
      ],
      "facts": [
        {
          "label": "Access you grant",
          "body": "A Pixel ID, a Meta Business Suite and an access token. Meta recommends generating the token in Events Manager, which creates a Conversions API app and system user and needs no App Review. Meta notes that third-party providers offering Conversions API functions have different requirements.",
          "sourceIds": [
            "P729-D01"
          ]
        },
        {
          "label": "Limits to plan for",
          "body": "Up to 1,000 events per request. event_time can be up to 7 days before the send; if any event is older, Meta returns an error for the whole request. Meta states there is no specific rate limit for the Conversions API.",
          "sourceIds": [
            "P729-D02",
            "P729-D03"
          ]
        },
        {
          "label": "Hashing",
          "body": "For custom audiences Meta accepts SHA256 only and supports no other hashing. For Conversions API events, email and phone are normalized and hashed before they are sent.",
          "sourceIds": [
            "P729-D04",
            "P729-D06"
          ]
        },
        {
          "label": "Audience policy to know",
          "body": "Meta states that beginning September 2, 2025 any custom audience or lookalike audience suggesting specific health conditions or financial status is flagged and prevented from being used to run ad campaigns, and that operation_status returns 471 for a flagged audience. Lists sent through this connection are limited to lead qualification and traffic validity.",
          "sourceIds": [
            "P729-D06"
          ]
        },
        {
          "label": "Terms and timing for audiences",
          "body": "Meta returns error 1870090 when the Custom Audience Terms have not been accepted for the account. It says changes to a custom audience usually take up to 24 hours.",
          "sourceIds": [
            "P729-D06"
          ]
        },
        {
          "label": "Testing",
          "body": "Events sent with a test_event_code appear in the Test Events tool. Meta says such events are not dropped and are still used for targeting and measurement, so the code must be removed from production payloads.",
          "sourceIds": [
            "P729-D02"
          ]
        }
      ],
      "features": {
        "heading": "Where each HiveSilo capability meets Meta",
        "intro": "Each row pairs a published HiveSilo capability with the Meta feature it works with. Scope is agreed for each client. Any row that reads from Meta needs a separate permission from your administrator.",
        "rows": [
          {
            "capability": "Buyer intelligence and three-tier qualification",
            "feature": "A standard or custom event_name on the Conversions API, with the value and currency parameters in custom_data",
            "gain": "Tier 1, Tier 2 and Tier 3 can each be a named event or a value your team sets, so Meta is told which leads qualified and at which tier.",
            "sourceIds": [
              "P729-D03",
              "P729-D09",
              "HSF1"
            ]
          },
          {
            "capability": "Offline conversions, qualified-demand scaling and outcome measurement",
            "feature": "Server events with an accurate action_source, and the Conversions API for CRM integration for later lead stages",
            "gain": "Qualification that happens after the form fill still reaches your dataset. Meta says its Conversion Leads performance goal currently works only with Lead Ads (Instant Forms), so that goal applies where you run them.",
            "sourceIds": [
              "P729-D02",
              "P729-D03",
              "P729-D08",
              "HSF1"
            ]
          },
          {
            "capability": "AdBrain",
            "feature": "The Ads Insights API /insights edges on ad account, campaign, ad set and ad, with the ads_read permission you grant",
            "gain": "Spend and delivery by campaign and ad set can be read beside qualified demand, so budget decisions rest on buyers and not on form fills.",
            "sourceIds": [
              "P729-D10",
              "HSF1"
            ]
          },
          {
            "capability": "AI firewall, bot defense and site protection",
            "feature": "Customer-file custom audiences with the audience labels QUALIFIED_LEADS and DISQUALIFIED_LEADS, and a DELETE call to remove members",
            "gain": "Enquiries screened as invalid or disqualified sit on a labelled audience your team can exclude, and entries can be taken off again.",
            "sourceIds": [
              "P729-D06",
              "HSF1"
            ]
          },
          {
            "capability": "Business insights and oversight",
            "feature": "Event deduplication on event_id and event_name, and the raw, matched and attributed event counts in Events Manager",
            "gain": "One counted event per customer action, and figures your team can reconcile against the qualified leads HiveSilo reported.",
            "sourceIds": [
              "P729-D02",
              "P729-D05",
              "HSF1"
            ]
          },
          {
            "capability": "Client-controlled privacy and verification",
            "feature": "Hashed customer information parameters (em, ph) and the data_processing_options parameter for Limited Data Use",
            "gain": "Where contact identifiers are sent at all, they leave your confidential environment normalized and hashed, with the data processing choice you have made.",
            "sourceIds": [
              "P729-D04",
              "P729-D07",
              "HS4",
              "HSF1"
            ]
          },
          {
            "capability": "AI Governance & Control",
            "feature": "An access token generated in Events Manager for a Conversions API system user, and the Test Events tool",
            "gain": "Access is held by your business and can be withdrawn, payloads can be inspected before go-live, and delivery decisions stay with a person.",
            "sourceIds": [
              "P729-D01",
              "P729-D02",
              "HS6"
            ]
          }
        ]
      },
      "capture": {
        "heading": "How the buying signals are captured and linked",
        "paragraphs": [
          "Lightweight first-party instrumentation on your own website reads pseudonymous behavior from the visitors your ads bring. HiveSilo scores those non-PII signals and screens invalid traffic. 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 is not a lead. The link to a person is made when the visitor identifies themselves on your website, for example through an enquiry form, and that match happens inside your enclave. The server event is built there, with the event_id your Pixel used. If you choose to send email or phone, Meta's normalization and hashing rules are applied there before the event leaves."
        ],
        "sourceIds": [
          "HS3",
          "HS4",
          "P729-D04"
        ]
      },
      "setup": {
        "heading": "What your Meta team does",
        "intro": "The connection is configuration in Events Manager and your ad account, plus activation on the HiveSilo side. These are the steps on your side, as Meta documents them.",
        "steps": [
          {
            "title": "Choose the Pixel and dataset.",
            "body": "Meta says to use the same Pixel ID for browser and server events if a Pixel is already set up for your website. You also need a Meta Business Suite.",
            "sourceIds": [
              "P729-D01"
            ]
          },
          {
            "title": "Generate the access token.",
            "body": "In Events Manager, a user with developer privileges for the business opens the Pixel settings and generates the token under the Conversions API section. Meta says this creates a Conversions API app and system user, with no App Review.",
            "sourceIds": [
              "P729-D01"
            ]
          },
          {
            "title": "Agree the event name and the event_id.",
            "body": "Name the event that marks a qualified lead. If your Pixel sends the same event, pass its eventID so the server event_id matches and Meta can deduplicate.",
            "sourceIds": [
              "P729-D03",
              "P729-D05"
            ]
          },
          {
            "title": "Prepare the exclusion audience.",
            "body": "Accept the Custom Audience Terms for the ad account, then create a customer-file custom audience with subtype CUSTOM, a customer_file_source and an audience label such as DISQUALIFIED_LEADS.",
            "sourceIds": [
              "P729-D06"
            ]
          },
          {
            "title": "Set your data processing choice.",
            "body": "Decide whether Limited Data Use applies, so data_processing_options can be sent with each event and record.",
            "sourceIds": [
              "P729-D07"
            ]
          },
          {
            "title": "Check a payload in the Test Events tool.",
            "body": "Send an event with the test_event_code the tool generates. Meta warns that these events are not dropped and are used for targeting and measurement, so use a real qualified lead and remove the code afterwards.",
            "sourceIds": [
              "P729-D02"
            ]
          },
          {
            "title": "Verify in Events Manager.",
            "body": "Meta says events can be verified within 20 minutes of sending, with the raw, matched and attributed counts and the connection method shown for each.",
            "sourceIds": [
              "P729-D02"
            ]
          }
        ],
        "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 Events Manager and ad account steps above run on your own change process.",
        "timelineSourceIds": [
          "HSF1"
        ]
      },
      "preview": {
        "heading": "What your Meta dataset receives",
        "note": "Illustrative example, not a Meta screen. The event name, the value and the audience names are chosen by your administrator. No personal data is shown.",
        "sourceIds": [],
        "fields": [
          {
            "label": "event_name",
            "value": "QualifiedLead, a custom event name your team chooses"
          },
          {
            "label": "HiveSilo qualification behind the event",
            "value": "Tier 1"
          },
          {
            "label": "action_source",
            "value": "website"
          },
          {
            "label": "custom_data: value and currency",
            "value": "The amount your team assigns to Tier 1"
          },
          {
            "label": "event_id",
            "value": "The same ID your Pixel sent, for deduplication"
          },
          {
            "label": "data_processing_options",
            "value": "Empty, or LDU, as your policy sets for this visitor"
          }
        ],
        "task": {
          "label": "Events Manager",
          "subject": "Server event received on your dataset",
          "body": "Deduplicated against the Pixel event with the same event_id and event name. Any contact identifier was normalized and hashed before it was sent. Which ad sets optimize toward this event stays with your paid social lead."
        }
      },
      "questionsHeading": "Who, what, when, where, how and why",
      "questions": [
        {
          "label": "Who",
          "body": "Advertisers who use Meta ads to bring buyers to their own website and want delivery to learn from lead quality. A person with developer privileges for your business in Events Manager generates the access token.",
          "sourceIds": [
            "P729-D01"
          ]
        },
        {
          "label": "What",
          "body": "Qualified-lead server events, and a list of enquiries screened as invalid or disqualified. HiveSilo does not create ads, ad sets or budgets.",
          "sourceIds": [
            "P729-D02",
            "P729-D06"
          ]
        },
        {
          "label": "When",
          "body": "When an enquiry from your website qualifies, and when the exclusion list changes. Meta accepts an event_time up to 7 days before the event is sent.",
          "sourceIds": [
            "P729-D02",
            "HS1"
          ]
        },
        {
          "label": "Where",
          "body": "On the dataset behind your own Pixel ID, and in custom audiences inside your own ad account.",
          "sourceIds": [
            "P729-D01",
            "P729-D06"
          ]
        },
        {
          "label": "How",
          "body": "Outbound calls to the Conversions API events endpoint and the Marketing API custom audience endpoints, with the access token you generated.",
          "sourceIds": [
            "P729-D02",
            "P729-D06"
          ]
        },
        {
          "label": "Why",
          "body": "Meta optimizes toward the events it receives. HiveSilo knows which of those visitors behaved like buyers on your website. A qualified-lead event gives delivery a clearer target.",
          "sourceIds": [
            "HS1",
            "HS2"
          ]
        }
      ]
    },
    "example": {
      "heading": "Sixty leads from one ad set. Eleven qualified.",
      "setup": "Illustrative workflow: a lead campaign produces sixty enquiries in a week. HiveSilo's scoring and your team's follow-up show eleven as qualified buyers. Some of the rest came from sessions screened as invalid traffic.",
      "nativeBaseline": "Meta records the lead events your Pixel sends and applies its own delivery and quality systems. That stays as it is.",
      "inputs": [
        "The event_id your website used for each Pixel lead event.",
        "HiveSilo's qualification result for the sessions behind each enquiry.",
        "The data processing choice that applies to each visitor.",
        "The current list of enquiries screened as invalid or disqualified."
      ],
      "decision": "Your team chooses whether an ad set should optimize toward the qualified-lead event.",
      "output": "Eleven qualified-lead events on the dataset, and an updated exclusion audience in the ad account.",
      "owner": "Your paid social lead owns the events used for optimization, the audiences and every delivery decision. HiveSilo supplies events and a list.",
      "hold": "Hold an event when it is more than 7 days old, when the required parameters are not available, or when the visitor's data processing choice does not permit it.",
      "record": "Confirm receipt in Events Manager, where Meta shows raw, matched and attributed events and the connection method for each.",
      "sourceIds": [
        "P729-D02",
        "P729-D03",
        "P729-D06"
      ]
    },
    "governance": {
      "intro": "An event informs delivery. Your team decides what delivery optimizes for.",
      "example": "Agree in advance which event name marks a qualified lead, which ad sets may optimize toward it and who may change that. Name each audience for what it is: qualified leads, disqualified leads, invalid traffic. Meta flags audiences that suggest health conditions or financial status, so audiences are named and built on lead qualification and traffic validity only."
    },
    "privacy": {
      "intro": "Customer identities stay in the environment you control.",
      "detail": "Meta says its systems are designed not to accept unhashed contact information, and that it uses hashed contact information for matching purposes only. Where contact identifiers are sent, they are normalized and hashed in the environment you control. HiveSilo's shared platform works with permitted non-PII signals and scores. Limited Data Use can be set on each event or record through the data processing options Meta documents."
    },
    "outcomes": {
      "intro": "Tell Meta which leads qualified and which enquiries to exclude, so the ad account optimizes toward real buyers.",
      "panels": [
        "Mark the Meta leads that scored as real buyers, so a qualified lead counts differently from a form fill.",
        "See which Meta campaigns and ad sets bring qualified leads, then give them more room.",
        "Review Meta spend on ad sets whose leads rarely qualify.",
        "Keep enquiries screened as invalid on a custom audience your team can exclude in Meta.",
        "Revisit earlier Meta leads whose visitors have since returned to your website and qualified."
      ]
    },
    "fit": {
      "intro": "Most useful where Meta ads are a material source of enquiries and lead quality varies by ad set.",
      "good": [
        "Advertisers with a considered purchase, where a qualified lead is worth far more than a form fill.",
        "Teams that already run the Meta Pixel on their website and can share an event_id with it.",
        "Accounts with enough lead volume for a qualified-lead event to inform delivery."
      ],
      "consider": [
        "Meta's own Pixel and Conversions API setup options may already meet the need for some accounts.",
        "Events older than 7 days are rejected, so late qualification decisions cannot be sent as events.",
        "Custom audiences need the Custom Audience Terms accepted for the account, and Meta restricts what an audience may suggest about people."
      ]
    },
    "connection": {
      "heading": "Agree the dataset, the event name and the audiences.",
      "paragraphs": [
        "Confirm the Pixel ID and dataset, the event name that will mark a qualified lead, the event_id your Pixel sends, and the ad account and audience names for exclusion lists. A person with developer privileges for your business generates the access token in Events Manager.",
        "The connection is available and is activated for each client on request. Public documentation establishes what Meta's APIs support; your account's standing, your agreements with Meta and your agreement with HiveSilo determine the scope that is switched on."
      ],
      "sourceIds": [
        "P729-D01",
        "P729-D05",
        "P729-D06",
        "HS10"
      ]
    },
    "faqs": [
      {
        "question": "Does HiveSilo connect to Meta?",
        "answer": "Yes. The Meta connection is available and is activated for each client on request. It uses Meta's documented Conversions API and custom audience endpoints with an access token you generate.",
        "sourceIds": [
          "P729-D01",
          "HS2"
        ]
      },
      {
        "question": "Which Meta features are in scope?",
        "answer": "The Conversions API events edge of your dataset, POST https://graph.facebook.com/{API_VERSION}/{PIXEL_ID}/events with up to 1,000 events per request, including deduplication with your Pixel; and customer-file custom audiences in your ad account for exclusion lists, with audience labels. Ads, ad sets and budgets are not created or changed.",
        "sourceIds": [
          "P729-D02",
          "P729-D05",
          "P729-D06"
        ]
      },
      {
        "question": "Can it be tested before production?",
        "answer": "Yes. Meta documents a Test Events tool in Events Manager: an event sent with the test_event_code it generates appears in the tool. Meta says such events are not dropped and are still used for targeting and measurement, so the code is removed from production payloads. Every event needs event_name, event_time, user_data and action_source.",
        "sourceIds": [
          "P729-D02",
          "P729-D03"
        ]
      },
      {
        "question": "Will server events double count with our Pixel?",
        "answer": "Not when deduplication is set up. Meta matches the Pixel's eventID to the server event_id with the same event name, for events received within 48 hours of the first.",
        "sourceIds": [
          "P729-D05"
        ]
      },
      {
        "question": "Are email addresses sent in clear text?",
        "answer": "No. Meta requires email and phone to be normalized and hashed, and accepts only SHA256 for custom audiences. Where they are sent, the hashing is done in the environment you control.",
        "sourceIds": [
          "P729-D04",
          "P729-D06",
          "HS4"
        ]
      },
      {
        "question": "How are exclusion lists sent?",
        "answer": "As a customer-file custom audience in your ad account. The audience is created at act_<AD_ACCOUNT_ID>/customaudiences and filled at /<CUSTOM_AUDIENCE_ID>/users, up to 10,000 users per request.",
        "sourceIds": [
          "P729-D06"
        ]
      },
      {
        "question": "What does Meta restrict about custom audiences?",
        "answer": "Meta states that beginning September 2, 2025 audiences suggesting specific health conditions or financial status are flagged and prevented from being used to run ad campaigns. This connection sends lists based on lead qualification and traffic validity only.",
        "sourceIds": [
          "P729-D06"
        ]
      },
      {
        "question": "Does HiveSilo read data back from Meta?",
        "answer": "Not in this workflow. HiveSilo writes events and audience members; receipt is confirmed in your own Events Manager. Reading ad performance through the Ads Insights API needs an app with the ads_read permission, which you would grant separately. For writing, Meta says a token generated in Events Manager needs no App Review, and that third-party providers have different requirements, which are confirmed during activation.",
        "sourceIds": [
          "P729-D01",
          "P729-D10"
        ]
      }
    ],
    "relationshipContext": {
      "privacyContext": "Contact identifiers, where used, are normalized and hashed in the environment you control before they are sent to Meta. HiveSilo's shared platform receives permitted non-PII signals and scores. Meta's data processing options and audience policies continue to govern how your account may use the data.",
      "diagramLabels": [
        "Customer identities stay in your environment",
        "Permitted non-PII website signals and buyer scores",
        "HiveSilo: qualified-lead events and exclusion list"
      ],
      "reviewIntentSentences": [
        "A Meta review should start with the Pixel events and optimization goals already set in your ad account.",
        "A Meta review of the connection should confirm the dataset, the access token and the event_id shared with the Pixel.",
        "When reviewing Meta with HiveSilo, ask which delivery decision a qualified-lead event would change."
      ],
      "sourceIds": [
        "P729-D01",
        "P729-D04",
        "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": "P729-D01",
      "title": "Meta for Developers: Get started with the Conversions API",
      "url": "https://developers.facebook.com/documentation/ads-commerce/conversions-api/get-started",
      "supports": "The Conversions API needs a Pixel ID, a Meta Business Suite and an access token; a token generated in Events Manager needs no App Review; Meta says third-party providers offering Conversions API functions have different requirements.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P729-D02",
      "title": "Meta for Developers: Using the API - Conversions API",
      "url": "https://developers.facebook.com/documentation/ads-commerce/conversions-api/using-the-api",
      "supports": "Events are sent by POST to https://graph.facebook.com/{API_VERSION}/{PIXEL_ID}/events; up to 1,000 events per request; event_time can be up to 7 days in the past; test_event_code is for testing only; there is no specific rate limit for the Conversions API.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P729-D03",
      "title": "Meta for Developers: Server Event Parameters",
      "url": "https://developers.facebook.com/documentation/ads-commerce/conversions-api/parameters/server-event",
      "supports": "event_name, event_time, user_data and action_source are required; event_source_url is required for website events; event_id is recommended for deduplication; data_processing_options accepts LDU.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P729-D04",
      "title": "Meta for Developers: Customer Information Parameters",
      "url": "https://developers.facebook.com/documentation/ads-commerce/conversions-api/parameters/customer-information-parameters",
      "supports": "em and ph require hashing after normalization; hashing is recommended for external_id; client_ip_address and client_user_agent must not be hashed, and client_user_agent is required for website events.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P729-D05",
      "title": "Meta for Developers: Handling Duplicate Pixel and Conversions API Events",
      "url": "https://developers.facebook.com/documentation/ads-commerce/conversions-api/deduplicate-pixel-and-server-events",
      "supports": "A Pixel eventID must match the server event_id and the event names must match; events are deduplicated only if received within 48 hours of the first event with that event_id.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P729-D06",
      "title": "Meta for Developers: Customer File Custom Audiences",
      "url": "https://developers.facebook.com/documentation/ads-commerce/marketing-api/audiences/guides/custom-audiences",
      "supports": "Audiences are created at act_<AD_ACCOUNT_ID>/customaudiences with subtype CUSTOM and customer_file_source, and filled at /<CUSTOM_AUDIENCE_ID>/users with up to 10,000 users per request, hashed as SHA256; beginning September 2, 2025 audiences suggesting specific health conditions or financial status are flagged, with operation_status 471.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P729-D07",
      "title": "Meta for Developers: Data processing options for US users - Marketing API",
      "url": "https://developers.facebook.com/documentation/ads-commerce/marketing-api/overview/data-processing-options",
      "supports": "Limited Data Use is enabled through data_processing_options with country and state values; for Customer List Custom Audiences it is available only for people in California.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P729-D08",
      "title": "Meta for Developers: Conversions API for CRM integration",
      "url": "https://developers.facebook.com/documentation/ads-commerce/conversions-api/conversion-leads-integration",
      "supports": "The Conversions API can upload down-funnel lead events from a CRM system as a separate integration with different required parameters; Meta says the Conversion Leads performance goal is currently only compatible with Lead Ads (Instant Forms) and lists fit guidelines including at least 200 leads per month and uploads at least once per day.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P729-D09",
      "title": "Meta for Developers: Standard Parameters",
      "url": "https://developers.facebook.com/documentation/ads-commerce/conversions-api/parameters/custom-data",
      "supports": "The value parameter is a numeric monetary amount, required for purchase events or any events that use value optimization; currency must be a valid ISO 4217 code.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P729-D10",
      "title": "Meta for Developers: Ads Insights API",
      "url": "https://developers.facebook.com/documentation/ads-commerce/marketing-api/insights",
      "supports": "The Ads Insights API provides performance data through /insights edges on the ad account, campaign, ad set and ad; access needs an app and the ads_read permission.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "HSF1",
      "title": "HiveSilo capability overview",
      "url": "https://hivesilo.com/evidence/features.md",
      "supports": "Published HiveSilo capabilities relied on here: buyer intelligence with Tier 1, Tier 2 and Tier 3 qualification, AdBrain, offline conversions with qualified-demand scaling and outcome measurement, AI Governance & Control, AI firewall and 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 data, advertising & messaging Meta + HiveSilo Available View scope HiveSilo / Integrations / Meta Meta. Tell the ad system which leads were real buyers. Meta delivers your ads and learns from the events it receives. HiveSilo scores the visitors those ads bring to your own website and sends qualified-lead events to your dataset through the Conversions API Meta documents. Contact HiveSilo Explore the fit Start with a conversation. No client records needed. Your ad account and dataset. An event worth optimizing for. Your client list stays yours. The value AI control Your data What you could gain Let’s talk FAQs & evidence The Pixel saw a lead. Did sales? Meta counts the events it receives from your Pixel and your server. It does not see what happened to each enquiry afterwards. Which event should ad delivery learn from? A lead campaign can deliver many form fills at a low cost while few of them become conversations. If the only event Meta receives is the form fill, delivery learns to find more people who fill in forms. The team paying for the campaign wants more people who buy. Meta provides the Pixel, the Conversions API and its own traffic-quality systems, and those stay in place. HiveSilo adds evidence from your own website: which sessions showed buying intent, which enquiries qualified and which were screened as invalid. That evidence is sent to your dataset as server events, and as a list your team can exclude. A Meta review should start with the Pixel events and optimization goals already set in your ad account. [P729-D01] [P729-D04] [HS3] [HS4] Give Meta a qualified-lead event to learn from. HiveSilo does not run campaigns or set budgets. It supplies qualified-lead events and an exclusion list to the Meta ad account and dataset you own, and your team decides how they are used. Talk through your use case What delivery optimizes for. Offer a qualified-lead event alongside the lead event your Pixel already sends. Who to stop reaching. Keep a list of enquiries screened as invalid or disqualified for your team to exclude. Which ad sets bring buyers. Compare ad sets by qualified leads in your own Meta reporting. Available The connection is activated for each client on request, against that client's own Meta dataset and ad account, with the events and audiences their administrator approves. How HiveSilo connects to Meta Meta delivers your ads and learns from the events it receives. HiveSilo scores visitors on your own website, screens invalid traffic and sends Tier 1, Tier 2 and Tier 3 qualified-lead events to your dataset through the Conversions API, plus exclusion lists as customer-file custom audiences. HiveSilo writes only; reading ad performance needs the ads_read permission, which you grant separately. Customer identities stay in your confidential environment. [P729-D02] [P729-D06] [P729-D10] [HSF1] [HS4] What your Meta dataset receives event_name QualifiedLead, a custom event name your team chooses HiveSilo qualification behind the event Tier 1 action_source website custom_data: value and currency The amount your team assigns to Tier 1 event_id The same ID your Pixel sent, for deduplication data_processing_options Empty, or LDU, as your policy sets for this visitor Events Manager Server event received on your dataset Deduplicated against the Pixel event with the same event_id and event name. Any contact identifier was normalized and hashed before it was sent. Which ad sets optimize toward this event stays with your paid social lead. Illustrative example, not a Meta screen. The event name, the value and the audience names are chosen by your administrator. No personal data is shown. What HiveSilo sends and the route Meta documents Every row below names a route in Meta's public developer documentation. HiveSilo calls the API outbound to write events and audience members, with an access token you generate and can withdraw. It does not read your ad performance in this workflow; that would need the ads_read permission, granted separately. It does not ask Meta to call into your systems. What HiveSilo sends to Meta and the documented route for each item HiveSilo sends How Meta uses it Documented route A qualified-lead event A server event on your dataset, shown in Events Manager POST https://graph.facebook.com/{API_VERSION}/{PIXEL_ID}/events. A request holds up to 1,000 events. Required parameters are event_name, event_time, user_data and action_source. [P729-D02] [P729-D03] An event_id shared with your Pixel Deduplication of the browser event and the server event The event_id parameter, matched to the Pixel's eventID with the same event name. Meta deduplicates events received within 48 hours of the first. [P729-D05] Hashed contact identifiers, where you choose to send them Customer information Meta uses for matching only The user_data object. Meta requires em and ph to be normalized and hashed, and says client_ip_address and client_user_agent must not be hashed. The hashing is done in the environment you control. [P729-D04] A list of enquiries screened as invalid or disqualified Members of a customer-file custom audience in your ad account POST to act_<AD_ACCOUNT_ID>/customaudiences with subtype CUSTOM and customer_file_source, then POST to /<CUSTOM_AUDIENCE_ID>/users with up to 10,000 users per request. A DELETE call to the same endpoint removes members. [P729-D06] The data processing choice you have made for US visitors Limited Data Use handling of the event or record The data_processing_options parameter with the value LDU, plus country and state values. For customer-list audiences Meta applies it only to people in California. [P729-D03] [P729-D07] Access you grant A Pixel ID, a Meta Business Suite and an access token. Meta recommends generating the token in Events Manager, which creates a Conversions API app and system user and needs no App Review. Meta notes that third-party providers offering Conversions API functions have different requirements. [P729-D01] Limits to plan for Up to 1,000 events per request. event_time can be up to 7 days before the send; if any event is older, Meta returns an error for the whole request. Meta states there is no specific rate limit for the Conversions API. [P729-D02] [P729-D03] Hashing For custom audiences Meta accepts SHA256 only and supports no other hashing. For Conversions API events, email and phone are normalized and hashed before they are sent. [P729-D04] [P729-D06] Audience policy to know Meta states that beginning September 2025 any custom audience or lookalike audience suggesting specific health conditions or financial status is flagged and prevented from being used to run ad campaigns, and that operation_status returns 471 for a flagged audience. Lists sent through this connection are limited to lead qualification and traffic validity. [P729-D06] Terms and timing for audiences Meta returns error 1870090 when the Custom Audience Terms have not been accepted for the account. It says changes to a custom audience usually take up to 24 hours. [P729-D06] Testing Events sent with a test_event_code appear in the Test Events tool. Meta says such events are not dropped and are still used for targeting and measurement, so the code must be removed from production payloads. [P729-D02] Where each HiveSilo capability meets Meta Each row pairs a published HiveSilo capability with the Meta feature it works with. Scope is agreed for each client. Any row that reads from Meta needs a separate permission from your administrator. Where each HiveSilo capability meets Meta HiveSilo capability Meta feature it works with What you gain Buyer intelligence and three-tier qualification A standard or custom event_name on the Conversions API, with the value and currency parameters in custom_data Tier 1, Tier 2 and Tier 3 can each be a named event or a value your team sets, so Meta is told which leads qualified and at which tier. [P729-D03] [P729-D09] [HSF1] Offline conversions, qualified-demand scaling and outcome measurement Server events with an accurate action_source, and the Conversions API for CRM integration for later lead stages Qualification that happens after the form fill still reaches your dataset. Meta says its Conversion Leads performance goal currently works only with Lead Ads (Instant Forms), so that goal applies where you run them. [P729-D02] [P729-D03] [P729-D08] [HSF1] AdBrain The Ads Insights API /insights edges on ad account, campaign, ad set and ad, with the ads_read permission you grant Spend and delivery by campaign and ad set can be read beside qualified demand, so budget decisions rest on buyers and not on form fills. [P729-D10] [HSF1] AI firewall, bot defense and site protection Customer-file custom audiences with the audience labels QUALIFIED_LEADS and DISQUALIFIED_LEADS, and a DELETE call to remove members Enquiries screened as invalid or disqualified sit on a labelled audience your team can exclude, and entries can be taken off again. [P729-D06] [HSF1] Business insights and oversight Event deduplication on event_id and event_name, and the raw, matched and attributed event counts in Events Manager One counted event per customer action, and figures your team can reconcile against the qualified leads HiveSilo reported. [P729-D02] [P729-D05] [HSF1] Client-controlled privacy and verification Hashed customer information parameters (em, ph) and the data_processing_options parameter for Limited Data Use Where contact identifiers are sent at all, they leave your confidential environment normalized and hashed, with the data processing choice you have made. [P729-D04] [P729-D07] [HS4] [HSF1] AI Governance & Control An access token generated in Events Manager for a Conversions API system user, and the Test Events tool Access is held by your business and can be withdrawn, payloads can be inspected before go-live, and delivery decisions stay with a person. [P729-D01] [P729-D02] [HS6] How the buying signals are captured and linked Lightweight first-party instrumentation on your own website reads pseudonymous behavior from the visitors your ads bring. HiveSilo scores those non-PII signals and screens invalid traffic. 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 is not a lead. The link to a person is made when the visitor identifies themselves on your website, for example through an enquiry form, and that match happens inside your enclave. The server event is built there, with the event_id your Pixel used. If you choose to send email or phone, Meta's normalization and hashing rules are applied there before the event leaves. [HS3] [HS4] [P729-D04] What your Meta team does The connection is configuration in Events Manager and your ad account, plus activation on the HiveSilo side. These are the steps on your side, as Meta documents them. Choose the Pixel and dataset. Meta says to use the same Pixel ID for browser and server events if a Pixel is already set up for your website. You also need a Meta Business Suite. [P729-D01] Generate the access token. In Events Manager, a user with developer privileges for the business opens the Pixel settings and generates the token under the Conversions API section. Meta says this creates a Conversions API app and system user, with no App Review. [P729-D01] Agree the event name and the event_id. Name the event that marks a qualified lead. If your Pixel sends the same event, pass its eventID so the server event_id matches and Meta can deduplicate. [P729-D03] [P729-D05] Prepare the exclusion audience. Accept the Custom Audience Terms for the ad account, then create a customer-file custom audience with subtype CUSTOM, a customer_file_source and an audience label such as DISQUALIFIED_LEADS. [P729-D06] Set your data processing choice. Decide whether Limited Data Use applies, so data_processing_options can be sent with each event and record. [P729-D07] Check a payload in the Test Events tool. Send an event with the test_event_code the tool generates. Meta warns that these events are not dropped and are used for targeting and measurement, so use a real qualified lead and remove the code afterwards. [P729-D02] Verify in Events Manager. Meta says events can be verified within 20 minutes of sending, with the raw, matched and attributed counts and the connection method shown for each. [P729-D02] 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 Events Manager and ad account steps above run on your own change process. [HSF1] Who, what, when, where, how and why Who Advertisers who use Meta ads to bring buyers to their own website and want delivery to learn from lead quality. A person with developer privileges for your business in Events Manager generates the access token. [P729-D01] What Qualified-lead server events, and a list of enquiries screened as invalid or disqualified. HiveSilo does not create ads, ad sets or budgets. [P729-D02] [P729-D06] When When an enquiry from your website qualifies, and when the exclusion list changes. Meta accepts an event_time up to 7 days before the event is sent. [P729-D02] [HS1] Where On the dataset behind your own Pixel ID, and in custom audiences inside your own ad account. [P729-D01] [P729-D06] How Outbound calls to the Conversions API events endpoint and the Marketing API custom audience endpoints, with the access token you generated. [P729-D02] [P729-D06] Why Meta optimizes toward the events it receives. HiveSilo knows which of those visitors behaved like buyers on your website. A qualified-lead event gives delivery a clearer target. [HS1] [HS2] See the intelligence behind the next move A qualified-lead server event. When an enquiry qualifies, HiveSilo posts an event to your dataset's events endpoint. Meta requires event_name, event_time, user_data and action_source on every event, and event_source_url for website events. [P729-D02] [P729-D03] Useful output: A server event in Events Manager that marks a qualified lead. No double counting with your Pixel. Each event carries an event_id. Meta deduplicates a browser event and a server event when the Pixel eventID matches the server event_id, the event names match and both arrive within 48 hours. [P729-D03] [P729-D05] Useful output: One counted event per customer action. An exclusion list as a custom audience. Enquiries screened as invalid or disqualified can be uploaded to a customer-file custom audience in your ad account, hashed as SHA256. Meta documents an audience label, DISQUALIFIED_LEADS, for leads that do not meet your qualification criteria. [P729-D06] Useful output: A custom audience your team can exclude from ad sets. Sixty leads from one ad set. Eleven qualified. Illustrative workflow: a lead campaign produces sixty enquiries in a week. HiveSilo's scoring and your team's follow-up show eleven as qualified buyers. Some of the rest came from sessions screened as invalid traffic. Start with Meta Meta records the lead events your Pixel sends and applies its own delivery and quality systems. That stays as it is. Bring the relevant context together The event_id your website used for each Pixel lead event. HiveSilo's qualification result for the sessions behind each enquiry. The data processing choice that applies to each visitor. The current list of enquiries screened as invalid or disqualified. Make the decision Your team chooses whether an ad set should optimize toward the qualified-lead event. A useful output Eleven qualified-lead events on the dataset, and an updated exclusion audience in the ad account. Keep responsibility clear Your paid social lead owns the events used for optimization, the audiences and every delivery decision. HiveSilo supplies events and a list. Hold and ask Hold an event when it is more than 7 days old, when the required parameters are not available, or when the visitor's data processing choice does not permit it. Record the outcome Confirm receipt in Events Manager, where Meta shows raw, matched and attributed events and the connection method for each. [P729-D02] [P729-D03] [P729-D06] Require control before AI acts. An event informs delivery. Your team decides what delivery optimizes for. Agree in advance which event name marks a qualified lead, which ad sets may optimize toward it and who may change that. Name each audience for what it is: qualified leads, disqualified leads, invalid traffic. Meta flags audiences that suggest health conditions or financial status, so audiences are named and built on lead qualification and traffic validity only. 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. Customer identities stay in the environment you control. Explore the security architecture Your client records stay with your business under HiveSilo’s published architecture. How your data stays under your control Contact identifiers, where used, are normalized and hashed in the environment you control before they are sent to Meta. HiveSilo's shared platform receives permitted non-PII signals and scores. Meta's data processing options and audience policies continue to govern how your account may use the data. [P729-D01] [P729-D04] [HS3] [HS4] [HS4] Your controlled environment Customer identities stay in your environment 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: qualified-lead events and exclusion list 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] Meta says its systems are designed not to accept unhashed contact information, and that it uses hashed contact information for matching purposes only. Where contact identifiers are sent, they are normalized and hashed in the environment you control. HiveSilo's shared platform works with permitted non-PII signals and scores. Limited Data Use can be set on each event or record through the data processing options Meta documents. A Meta review of the connection should confirm the dataset, the access token and the event_id shared with the Pixel. [P729-D01] [P729-D04] [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. Tell Meta which leads qualified and which enquiries to exclude, so the ad account optimizes toward real buyers. 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 Mark the Meta leads that scored as real buyers, so a qualified lead counts differently from a form fill. Find more clients like your best. 4–6× · Reported conversion lift Closed-revenue outcomes See which Meta campaigns and ad sets bring qualified leads, then give them more room. Put more of your budget to work. Up to 31% · Reported ad-spend savings Bot and invalid-traffic filtering Review Meta spend on ad sets whose leads rarely qualify. Keep evolving your protection. 99.9999% · Bot detection Observed client results Keep enquiries screened as invalid on a custom audience your team can exclude in Meta. 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 earlier Meta leads whose visitors have since returned to your website and qualified. 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 Meta workflow. Map the decision, the data you control and a measurable next step with HiveSilo. Enterprise data, advertising & messaging · Data, marketing, sales operations, technology & security Contact HiveSilo Mention Meta 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 Meta connection & briefing scope Agree the dataset, the event name and the audiences. Confirm the Pixel ID and dataset, the event name that will mark a qualified lead, the event_id your Pixel sends, and the ad account and audience names for exclusion lists. A person with developer privileges for your business generates the access token in Events Manager. The connection is available and is activated for each client on request. Public documentation establishes what Meta's APIs support; your account's standing, your agreements with Meta and your agreement with HiveSilo determine the scope that is switched on. When reviewing Meta with HiveSilo, ask which delivery decision a qualified-lead event would change. [P729-D01] [P729-D04] [HS3] [HS4] [P729-D01] [P729-D05] [P729-D06] [HS10] A useful fit when Most useful where Meta ads are a material source of enquiries and lead quality varies by ad set. Advertisers with a considered purchase, where a qualified lead is worth far more than a form fill. Teams that already run the Meta Pixel on their website and can share an event_id with it. Accounts with enough lead volume for a qualified-lead event to inform delivery. Consider the fit Meta's own Pixel and Conversions API setup options may already meet the need for some accounts. Events older than 7 days are rejected, so late qualification decisions cannot be sent as events. Custom audiences need the Custom Audience Terms accepted for the account, and Meta restricts what an audience may suggest about people. In your enquiry, name Meta and the business decision. Please leave out client records, credentials and sensitive samples. Eight questions before your briefing 1. Does HiveSilo connect to Meta? Yes. The Meta connection is available and is activated for each client on request. It uses Meta's documented Conversions API and custom audience endpoints with an access token you generate. [P729-D01] [HS2] 2. Which Meta features are in scope? The Conversions API events edge of your dataset, POST https://graph.facebook.com/{API_VERSION}/{PIXEL_ID}/events with up to 1,000 events per request, including deduplication with your Pixel; and customer-file custom audiences in your ad account for exclusion lists, with audience labels. Ads, ad sets and budgets are not created or changed. [P729-D02] [P729-D05] [P729-D06] 3. Can it be tested before production? Yes. Meta documents a Test Events tool in Events Manager: an event sent with the test_event_code it generates appears in the tool. Meta says such events are not dropped and are still used for targeting and measurement, so the code is removed from production payloads. Every event needs event_name, event_time, user_data and action_source. [P729-D02] [P729-D03] 4. Will server events double count with our Pixel? Not when deduplication is set up. Meta matches the Pixel's eventID to the server event_id with the same event name, for events received within 48 hours of the first. [P729-D05] 5. Are email addresses sent in clear text? No. Meta requires email and phone to be normalized and hashed, and accepts only SHA256 for custom audiences. Where they are sent, the hashing is done in the environment you control. [P729-D04] [P729-D06] [HS4] 6. How are exclusion lists sent? As a customer-file custom audience in your ad account. The audience is created at act_<AD_ACCOUNT_ID>/customaudiences and filled at /<CUSTOM_AUDIENCE_ID>/users, up to 10,000 users per request. [P729-D06] 7. What does Meta restrict about custom audiences? Meta states that beginning September 2025 audiences suggesting specific health conditions or financial status are flagged and prevented from being used to run ad campaigns. This connection sends lists based on lead qualification and traffic validity only. [P729-D06] 8. Does HiveSilo read data back from Meta? Not in this workflow. HiveSilo writes events and audience members; receipt is confirmed in your own Events Manager. Reading ad performance through the Ads Insights API needs an app with the ads_read permission, which you would grant separately. For writing, Meta says a token generated in Events Manager needs no App Review, and that third-party providers have different requirements, which are confirmed during activation. [P729-D01] [P729-D10] Sources, scope & verification Meta for Developers: Get started with the Conversions API [P729-D01] The Conversions API needs a Pixel ID, a Meta Business Suite and an access token; a token generated in Events Manager needs no App Review; Meta says third-party providers offering Conversions API functions have different requirements. Reviewed November 2026 Meta for Developers: Using the API - Conversions API [P729-D02] Events are sent by POST to https://graph.facebook.com/{API_VERSION}/{PIXEL_ID}/events; up to 1,000 events per request; event_time can be up to 7 days in the past; test_event_code is for testing only; there is no specific rate limit for the Conversions API. Reviewed November 2026 Meta for Developers: Server Event Parameters [P729-D03] event_name, event_time, user_data and action_source are required; event_source_url is required for website events; event_id is recommended for deduplication; data_processing_options accepts LDU. Reviewed November 2026 Meta for Developers: Customer Information Parameters [P729-D04] em and ph require hashing after normalization; hashing is recommended for external_id; client_ip_address and client_user_agent must not be hashed, and client_user_agent is required for website events. Reviewed November 2026 Meta for Developers: Handling Duplicate Pixel and Conversions API Events [P729-D05] A Pixel eventID must match the server event_id and the event names must match; events are deduplicated only if received within 48 hours of the first event with that event_id. Reviewed November 2026 Meta for Developers: Customer File Custom Audiences [P729-D06] Audiences are created at act_<AD_ACCOUNT_ID>/customaudiences with subtype CUSTOM and customer_file_source, and filled at /<CUSTOM_AUDIENCE_ID>/users with up to 10,000 users per request, hashed as SHA256; beginning September 2025 audiences suggesting specific health conditions or financial status are flagged, with operation_status 471. Reviewed November 2026 Meta for Developers: Data processing options for US users - Marketing API [P729-D07] Limited Data Use is enabled through data_processing_options with country and state values; for Customer List Custom Audiences it is available only for people in California. Reviewed November 2026 Meta for Developers: Conversions API for CRM integration [P729-D08] The Conversions API can upload down-funnel lead events from a CRM system as a separate integration with different required parameters; Meta says the Conversion Leads performance goal is currently only compatible with Lead Ads (Instant Forms) and lists fit guidelines including at least 200 leads per month and uploads at least once per day. Reviewed November 2026 Meta for Developers: Standard Parameters [P729-D09] The value parameter is a numeric monetary amount, required for purchase events or any events that use value optimization; currency must be a valid ISO 4217 code. Reviewed November 2026 Meta for Developers: Ads Insights API [P729-D10] The Ads Insights API provides performance data through /insights edges on the ad account, campaign, ad set and ad; access needs an app and the ads_read permission. Reviewed November 2026 HiveSilo capability overview [HSF1] Published HiveSilo capabilities relied on here: buyer intelligence with Tier 1, Tier 2 and Tier 3 qualification, AdBrain, offline conversions with qualified-demand scaling and outcome measurement, AI Governance & Control, AI firewall and 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. Meta is identified to explain the workflow; no endorsement, certification or partnership is implied. Your next move starts with a conversation. Contact HiveSilo"
}
