Enterprise data, advertising & messaging

DSP retargeting + HiveSilo

AvailableView scope

DSP retargeting. Aim programmatic spend at real buyers.

Your demand-side platform buys the impressions. HiveSilo scores the visitors on your own website and sends qualified-lead events and exclusion lists to your seat on Display & Video 360, The Trade Desk or Amazon DSP, through the routes each platform documents.

Start with a conversation. No client records needed.

Illustrative enterprise office at dusk for the DSP retargeting integration workflow

Your seat on the platform.
A buyer signal it can use.

Your client list stays yours.

Retargeting follows every visitor. Should it?

A demand-side platform retargets the audiences it is given. It was not on your website to see which visitors behaved like buyers.

Who should a retargeting budget follow?

A site-visitor audience treats every visit the same. A visitor showing strong buying intent sits in the same segment as a passing visit, and as traffic that was not a person at all. Impressions bought against that segment are spread across all three.

Display & Video 360, The Trade Desk and Amazon DSP each provide their own pixels, audiences and traffic-quality controls, and those stay in place. HiveSilo adds evidence from your own website: which enquiries qualified and which traffic it screened as invalid. That evidence is sent to your seat as conversion events and as lists your trading team can target or exclude.

A DSP retargeting review should start with the site audiences and line items your trading team already runs. [P730-D03] [P730-D06] [P730-D09] [HS3] [HS4]

Give the platform a list worth bidding on, and one to leave out.

HiveSilo does not place bids or build line items. It supplies qualified-lead events and exclusion lists to the platform account you own, and your trading team decides how they are used.

Talk through your use case
Who to retarget.
Build retargeting on visitors who qualified, alongside the site audiences you already run.
Who to leave out.
Keep a list of invalid traffic and disqualified enquiries for your team to exclude.
What counts as a result.
Report a qualified lead to the platform as a conversion event it can attribute.

AvailableThe connection is activated for each client on request, against that client's own seat on the demand-side platform they use, with the audiences and events their administrator approves and the access approval that platform requires.

How HiveSilo connects DSP retargeting

Your demand-side platform buys the impressions. HiveSilo scores visitors on your own website, screens invalid traffic and sends Tier 1, Tier 2 and Tier 3 qualified-lead events and exclusion lists to your own seat on Display & Video 360, The Trade Desk or Amazon DSP, through each platform's documented API and consent fields. HiveSilo writes only. Customer identities stay in your confidential environment. [P730-D01] [P730-D06] [P730-D09] [HSF1] [HS4]

What your DSP seat receives

conversionType
LEAD
Event name
Qualified_Lead, a name your team chooses
HiveSilo qualification behind the event
Tier 1
eventSource
WEBSITE
value and currencyCode
The amount your team assigns to Tier 1
consent
The consent values recorded on your website for this visitor

Platform report

Conversion available for attribution

On The Trade Desk and Display & Video 360 the same qualification travels through the routes listed above. Match keys are hashed before they are sent. Which line items use the event or the audience stays with your trading lead.

Illustrative example, not a platform screen. It is shown in the shape of an Amazon DSP conversion event; event names, values and audience names are chosen by your administrator. No personal data is shown.
What HiveSilo sends and the route DSP retargeting documents

This page covers three demand-side platforms: Google Display & Video 360, The Trade Desk and Amazon DSP. Every row below names a route in that platform's public documentation. HiveSilo calls the API outbound to write lists and events, with access you grant and can withdraw. It does not read your line items or reports in this workflow; any read would need a separate permission from you.

What HiveSilo sends to each demand-side platform and the documented route for each item
HiveSilo sendsHow the platform uses itDocumented route
A qualified-lead or exclusion list, for Display & Video 360Members of a Customer Match audience, by contact information or mobile IDA Data Manager API audienceMembers.ingest request with the audience id as the productDestinationId. Google's upgrade note on the Display & Video 360 API guide points new Customer Match work to this API. [P730-D01] [P730-D02]
The same list, where an existing Display & Video 360 API workflow is keptAdded or removed members of a CUSTOMER_MATCH_CONTACT_INFO or CUSTOMER_MATCH_DEVICE_ID audiencePOST https://displayvideo.googleapis.com/v4/firstPartyAndPartnerAudiences/{firstPartyAndPartnerAudienceId}:editCustomerMatchMembers. Membership lasts at most 540 days. [P730-D03] [P730-D04]
A qualified-lead or exclusion list, for The Trade DeskA targeting or conversion segment on your advertiserThe First-Party Data Uploader (GraphQL), through a single-use drop endpoint generated for each upload. ID types include EmailHashedUnifiedId2, UID2, TDID and DAID. [P730-D05] [P730-D06]
A qualified-lead conversion event, for The Trade DeskAn event used for retargeting and attributionPOST /track/realtimeconversion, the endpoint of the Real-Time Conversion Events API (The Trade Desk's product name), with a supported user ID and its type. [P730-D07]
A qualified-lead conversion event, for Amazon DSPA conversion used for attribution and measurement in Amazon DSP reportsPOST /adsApi/v1/create/events with the Amazon-Ads-ClientId and Amazon-Ads-AccountId headers. A request holds 1 to 500 events; conversionType accepts LEAD. [P730-D09]
A qualified-lead or exclusion list, for Amazon DSPA data provider audience, usable like any other Amazon DSP audiencePOST /dp/records/hashed, then POST v2/dp/audiencemetadata/, then PATCH /v2/dp/audience to associate the records. PATCH /v2/dp/users removes user data. [P730-D10]
Approval: Display & Video 360
Google says your Display & Video 360 partner must meet set requirements before uploading Customer Match data, and the user needs an Admin or Standard role for the partner or advertiser that owns the audience. [P730-D01] [P730-D02]
Approval: The Trade Desk
The Trade Desk says to contact your Technical Account Manager for API permissions. Email addresses, phone numbers and other directly identifiable IDs are available only to advertisers and partners who have signed the UID agreement. Anonymous IDs do not require it. [P730-D05] [P730-D06]
Approval: Amazon DSP
Amazon says you must apply for Amazon Ads API access and be approved, using a Login with Amazon client, and that approval may take up to 1 business day. The data provider API needs a further request, a Jira support ticket with the Symptom Path /dp Data Provider. [P730-D08] [P730-D11]
Consent rules to know
Display & Video 360 returns an error if adUserData or adPersonalization consent is denied, and Google removes EEA members from Customer Match lists owned by a partner rather than an advertiser. Amazon requires consent information for EU advertisers. The Trade Desk lists EUID among the user IDs it supports. [P730-D01] [P730-D03] [P730-D07] [P730-D09]
Hashing
Display & Video 360 takes SHA256 hashed email and phone. The Trade Desk takes a Base64-encoded SHA-256 hash of a normalized email as EmailHashedUnifiedId2. Amazon takes SHA-256 hashed PII match keys. Hashing is done in the environment you control. [P730-D03] [P730-D06] [P730-D09]
Route change to know
Google states that it does not recommend implementing new Customer Match workflows using the Display & Video 360 API and directs them to the Data Manager API. The Trade Desk labels its CRM Data API as legacy and recommends the First-Party Data Uploader. [P730-D02] [P730-D05]
Where each HiveSilo capability meets DSP retargeting

Each row pairs a published HiveSilo capability with the feature it works with on Display & Video 360, The Trade Desk or Amazon DSP. Scope is agreed for each client and each platform. Any read from a platform needs a separate permission from your administrator.

Where each HiveSilo capability meets DSP retargeting
HiveSilo capabilityDSP retargeting feature it works withWhat you gain
Buyer intelligence and three-tier qualificationAmazon Events API events with conversionType LEAD, a value and a currencyCode; The Trade Desk custom fields TD1 to TD10 for conversion event metadataTier 1, Tier 2 and Tier 3 can travel with the conversion as a named event, a value or a metadata field, so the platform is told which visitors qualified and at which tier. [P730-D07] [P730-D09] [HSF1]
Offline conversions, qualified-demand scaling and outcome measurementFloodlight offline conversions for Display & Video 360 through the Data Manager API; The Trade Desk conversion segments and conversion events; the Amazon Events APIQualified leads are reported to the platform as conversions it can attribute, so your trading team can measure line items by qualified demand. [P730-D12] [P730-D06] [P730-D07] [P730-D09] [HSF1]
AdBrainAmazon DSP reports, where Events API conversions are used for attribution; The Trade Desk conversion segments attached to a campaignQualified-lead conversions appear in the platform reports your team already reads, which informs retargeting, audience and budget decisions. [P730-D06] [P730-D09] [HSF1]
AI firewall, bot defense and site protectionCustomer Match audiences in Display & Video 360, targeting segments in The Trade Desk and data provider audiences in Amazon DSPInvalid traffic and disqualified enquiries sit on a list in your own seat that your trading team can exclude from retargeting. [P730-D01] [P730-D06] [P730-D10] [HSF1]
Client-controlled privacy and verificationSHA-256 hashed identifiers, anonymous IDs such as TDID, the adUserData and adPersonalization consent fields in Display & Video 360 and the consent object on Amazon eventsWhere a platform matches on contact information, values leave your confidential environment hashed and with the consent your website recorded. [P730-D03] [P730-D05] [P730-D09] [HS4] [HSF1]
AI Governance & ControlEach platform's access approval: an Admin or Standard role in Display & Video 360, API permissions from your Technical Account Manager at The Trade Desk, and Amazon Ads API approvalAccess is held by your account owner and can be withdrawn on each platform, and line items, bids and audience use stay with your trading team. [P730-D02] [P730-D06] [P730-D08] [HS6]
How the buying signals are captured and linked

Lightweight first-party instrumentation on your own website reads pseudonymous behavior from your visitors, and 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 no identity. Where a platform accepts its own pseudonymous identifier, the list can be built on that. A session is linked to a known person only when the visitor identifies themselves on your website, for example through an enquiry form, and that match happens inside your enclave. Hashed contact identifiers, where a platform uses them, are prepared there before anything is sent. [HS3] [HS4] [P730-D05]

What your DSP retargeting team does

Only the steps for the platform you use apply. Each is configuration in your own seat, as the platform documents it, plus activation on the HiveSilo side.

  1. Display & Video 360: confirm requirements and role.Google says your partner must meet set requirements before uploading Customer Match data, and the user needs an Admin or Standard role for the partner or advertiser that will own the audience. [P730-D01] [P730-D02]
  2. Display & Video 360: create the audience.Create the Customer Match audience and note its id. That id is passed as the productDestinationId on each upload. Google removes EEA members from lists owned by a partner, so decide whether the advertiser should own the list. [P730-D01]
  3. The Trade Desk: request API permissions.Contact your Technical Account Manager for the permissions. If email addresses or phone numbers will be used, a signed UID agreement is required; anonymous IDs do not need it. [P730-D05] [P730-D06]
  4. The Trade Desk: create the segment.Create a TARGETING or CONVERSION segment for your advertiser. The Trade Desk says a conversion segment must be attached to a campaign before uploaded data can be attributed. [P730-D06]
  5. The Trade Desk: check an event with the debug field.The Trade Desk documents a debug field with a value of 1 on a conversion request, to troubleshoot missing parameters, consent mismatches or implementation errors. [P730-D07]
  6. Amazon DSP: apply for API access.Create a Login with Amazon client and apply for Amazon Ads API access; Amazon says approval may take up to 1 business day. For audiences, submit the Jira ticket with the Symptom Path /dp Data Provider. [P730-D08] [P730-D11]
  7. Name the consent source.Confirm where your website records consent. Display & Video 360 returns an error when adUserData or adPersonalization is denied, and Amazon requires consent information for EU advertisers. [P730-D03] [P730-D09]

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 platform steps above, including each platform's own access approval, run on your own change process and the platform's. [HSF1]

Who, what, when, where, how and why
Who
Advertisers and their trading teams who retarget website visitors through Display & Video 360, The Trade Desk or Amazon DSP. The administrator of your seat authorizes the connection and holds the platform approvals. [P730-D02] [P730-D06] [P730-D08]
What
Qualified-lead conversion events, a list of qualified visitors to retarget, and a list of invalid traffic and disqualified enquiries to exclude. HiveSilo does not create line items or place bids. [P730-D01] [P730-D05] [P730-D09]
When
When an enquiry from your website qualifies, and when a list changes. Each platform processes uploads on its own schedule. [P730-D07] [HS1]
Where
In your own account on the platform: a Customer Match audience in Display & Video 360, a first-party segment in The Trade Desk, or a data provider audience and conversion events in Amazon DSP. [P730-D01] [P730-D06] [P730-D10]
How
Outbound calls to each platform's documented API: the Data Manager API for Display & Video 360, the First-Party Data Uploader and conversion events endpoint for The Trade Desk, and the Events API and Data Provider API for Amazon DSP. [P730-D01] [P730-D06] [P730-D09] [P730-D10]
Why
The platform knows the inventory and the auction. HiveSilo knows which visitors behaved like buyers on your website. Together retargeting spend follows the visitors worth following. [HS1] [HS2]
See the intelligence behind the next move

Display & Video 360: Customer Match audiences.

Lists are uploaded to a Customer Match audience through the Data Manager API's audienceMembers.ingest request. Google no longer recommends building new Customer Match workflows on the Display & Video 360 API itself and points to the Data Manager API. [P730-D01] [P730-D02]

Useful output: A Customer Match audience in your Display & Video 360 account.

The Trade Desk: segments and conversion events.

Lists are sent through the First-Party Data Uploader, which The Trade Desk recommends, as targeting or conversion segments. Conversion events go to the POST /track/realtimeconversion endpoint with a supported user ID. [P730-D05] [P730-D06] [P730-D07]

Useful output: A first-party segment and conversion events on your advertiser.

Amazon DSP: Events API and Data Provider API.

Qualified leads are sent as events with POST /adsApi/v1/create/events, where conversionType accepts LEAD. Audience lists are uploaded as hashed records and associated with a data provider audience. [P730-D09] [P730-D10]

Useful output: Conversion events and an audience in your Amazon DSP account.

One site audience. Three kinds of visitor.

Illustrative workflow: a retargeting line item follows everyone who visited the product pages in the past month. HiveSilo's scoring shows three groups inside that audience: visitors who qualified, visitors who showed little intent, and sessions screened as invalid traffic.

Start with DSP retargeting

The demand-side platform builds the site audience from its own pixel and applies its own traffic-quality controls. That stays as it is.

Bring the relevant context together

  • The platform identifier or hashed contact identifier available for each visitor.
  • HiveSilo's qualification result for the sessions behind each enquiry.
  • The current list of invalid traffic and disqualified enquiries.
  • The consent state recorded for each visitor.

Make the decision

The trading team targets the qualified list, excludes the second list, and leaves the general site audience at a lower bid.

A useful output

Two audiences in the platform account, one to target and one to exclude, plus qualified-lead conversion events for attribution.

Keep responsibility clear

Your trading lead owns the line items, bids and audience use. HiveSilo supplies lists and events.

Hold and ask

Hold an upload when the platform approval is not in place, when the consent state does not permit it, or when no identifier the platform accepts is available.

Record the outcome

Keep the audience names and their purpose in your trading plan, and review audience size in the platform after each upload. [P730-D01] [P730-D06] [P730-D10]

Require control before AI acts.

A list informs targeting. Your trading team decides where the budget goes.

Agree in advance which audiences HiveSilo may write to on each platform and who applies them to line items. Name each audience for what it is: qualified leads, disqualified enquiries, invalid traffic. Lists are built on lead qualification and traffic validity. Keep each platform's access approval and terms with the account owner.

  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 a platform uses them, are hashed in the environment you control before they are sent. HiveSilo's shared platform receives permitted non-PII signals and scores. Each demand-side platform's consent fields, regional rules and terms continue to govern how your seat may use the data. [P730-D03] [P730-D06] [P730-D09] [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 scoresPermitted non-PII website signals and buyer scores

HiveSilo intelligence

HiveSilo: qualified-lead events and exclusion lists

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]

Where a platform matches on contact information, it requires hashed values, and that hashing is done in the environment you control. Where a platform accepts its own pseudonymous identifiers, those are used instead. HiveSilo's shared platform works with permitted non-PII signals and scores. Each platform's consent fields and regional rules apply to every upload, including Google's removal of EEA members from partner-owned lists and Amazon's consent requirement for EU advertisers.

A DSP retargeting review of the connection should confirm the platform's access approval, the identifier type and the consent source. [P730-D03] [P730-D06] [P730-D09] [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.

Give your demand-side platform a qualified list to follow and an invalid list to leave out, so retargeting spend reaches real buyers.

Explore HiveSilo case studiesContact HiveSilo
Select a benefit to explore
3,790 of 5,000 · UHNW buyer scoreIllustrative score
4–6× · Reported conversion liftClosed-revenue outcomes
Up to 31% · Reported ad-spend savingsBot and invalid-traffic filtering
99.9999% · Bot detectionObserved client results
5–21% · Revenue lift from existing dataHiveSilo-reported client results

Sharper scoring. Clearer intent.

3,790 of 5,000 · UHNW buyer scoreIllustrative score

Build DSP retargeting audiences from visitors who scored as real buyers.

Find more clients like your best.

4–6× · Reported conversion liftClosed-revenue outcomes

See which DSP retargeting line items reach qualified leads, then give them more room.

Put more of your budget to work.

Up to 31% · Reported ad-spend savingsBot and invalid-traffic filtering

Stop DSP retargeting impressions against visitors whose enquiries were disqualified.

Keep evolving your protection.

99.9999% · Bot detectionObserved client results

Keep traffic screened as invalid on an exclusion list for DSP retargeting. 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 dataHiveSilo-reported client results

Bring returning high-intent visitors already in your data back into DSP retargeting.

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 DSP retargeting 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 DSP retargeting 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.

Reviewed

Contact HiveSilo
DSP retargeting connection & briefing scope

Agree the platform, the audiences and the approval.

Confirm which demand-side platform you use, the account or advertiser that will own the audiences, the identifier type the platform will match on, and where your website records consent. Your account owner confirms the platform's access approval: the Customer Match requirements for Display & Video 360, the Technical Account Manager permissions and UID agreement for The Trade Desk, or Amazon Ads API approval and the data provider request for Amazon DSP.

The connection is available and is activated for each client on request. Public documentation establishes what each platform's API supports; your seat, your agreements with the platform and your agreement with HiveSilo determine the scope that is switched on.

When reviewing DSP retargeting with HiveSilo, ask which line item a qualified-visitor audience would change. [P730-D03] [P730-D06] [P730-D09] [HS3] [HS4]

[P730-D02] [P730-D05] [P730-D08] [P730-D11] [HS10]

A useful fit when

Most useful where programmatic retargeting is a material budget line and visitor quality varies widely.

  • Advertisers with their own seat or a managed seat on Display & Video 360, The Trade Desk or Amazon DSP.
  • Trading teams that already run site-visitor retargeting and want a tighter audience.
  • Businesses with a considered purchase, where following the right visitor changes the result.

Consider the fit

  • Each platform's own audiences and pixels may already meet the need for some advertisers.
  • Each platform requires its own access approval, which your account owner must hold before any upload.
  • Amazon states a table size of between 10,000 and 5,000,000 rows for its hashing template, so small lists may not suit that route.

In your enquiry, name DSP retargeting and the business decision. Please leave out client records, credentials and sensitive samples.

Eight questions before your briefing
  1. 1.Does HiveSilo connect to DSP retargeting platforms?

    Yes. The connection is available and is activated for each client on request. It covers Google Display & Video 360, The Trade Desk and Amazon DSP, each through its documented API with access your account owner authorizes. [P730-D01] [P730-D05] [P730-D09] [HS2]

  2. 2.Which route is used for Display & Video 360?

    The Data Manager API, which uploads Customer Match members with an audienceMembers.ingest request. Google says it does not recommend new Customer Match workflows on the Display & Video 360 API. [P730-D01] [P730-D02]

  3. 3.What access does The Trade Desk require?

    API permissions arranged through your Technical Account Manager. Uploading email addresses, phone numbers or other directly identifiable IDs also requires a signed UID agreement. Anonymous IDs such as TDID do not. [P730-D05] [P730-D06]

  4. 4.What access does Amazon DSP require?

    Amazon Ads API access, which you apply for and which Amazon says may take up to 1 business day to approve. The data provider API needs a further Jira support ticket with the Symptom Path /dp Data Provider. [P730-D08] [P730-D11]

  5. 5.How are qualified leads sent as conversions?

    To The Trade Desk through POST /track/realtimeconversion with a supported user ID. To Amazon DSP through POST /adsApi/v1/create/events, where conversionType accepts LEAD and a request holds 1 to 500 events. For Display & Video 360, Google documents Floodlight offline conversions through the Data Manager API. [P730-D07] [P730-D09] [P730-D12]

  6. 6.Which platform features are in scope, and does HiveSilo read data back?

    Audiences and conversions on three platforms: Customer Match audiences and Floodlight offline conversions for Display & Video 360, first-party segments and conversion events for The Trade Desk, and data provider audiences and Events API conversions for Amazon DSP. HiveSilo writes only. Reading line items or reports is not part of this workflow and would need a separate permission from you. [P730-D01] [P730-D06] [P730-D10] [P730-D12]

  7. 7.What happens to European audience members?

    Google removes EEA members from Customer Match lists owned by a Display & Video 360 partner, and applies consent settings to lists owned by an advertiser. Amazon requires consent information for EU advertisers. The Trade Desk lists EUID among the user IDs it supports. [P730-D01] [P730-D07] [P730-D09]

  8. 8.Are email addresses sent in clear text?

    No. Where a platform matches on contact information, values are hashed in the environment you control: SHA256 for Display & Video 360, a Base64-encoded SHA-256 hash for The Trade Desk, and SHA-256 for Amazon. [P730-D03] [P730-D06] [P730-D09] [HS4]

Sources, scope & verification
  1. Data Manager API: Customer Match overview (Display & Video 360) [P730-D01]

    The Data Manager API uploads Customer Match members to Display & Video 360 through audienceMembers.ingest; the partner must meet set requirements; EEA audience members are automatically removed from a Customer Match list owned by a Display & Video 360 partner.

    Reviewed November 2026

  2. Display & Video 360 API: Upload Customer Match audience, Overview [P730-D02]

    Google does not recommend implementing new Customer Match workflows with the Display & Video 360 API and points to the Data Manager API; the partner must meet the Customer Match requirements and the user needs an Admin or Standard role.

    Reviewed November 2026

  3. Display & Video 360 API: REST Resource firstPartyAndPartnerAudiences [P730-D03]

    Audience types CUSTOMER_MATCH_CONTACT_INFO and CUSTOMER_MATCH_DEVICE_ID; membershipDurationDays must be greater than 0 and at most 540; contact information is SHA256 hashed; a consent value of CONSENT_STATUS_DENIED for adUserData or adPersonalization returns an error.

    Reviewed November 2026

  4. Display & Video 360 API: Method firstPartyAndPartnerAudiences.editCustomerMatchMembers [P730-D04]

    POST https://displayvideo.googleapis.com/v4/firstPartyAndPartnerAudiences/{firstPartyAndPartnerAudienceId}:editCustomerMatchMembers adds or removes members; OAuth scope https://www.googleapis.com/auth/display-video.

    Reviewed November 2026

  5. The Trade Desk: ID-based first-party data [P730-D05]

    Upload methods are the First-Party Data Uploader (recommended, GraphQL or CSV), the legacy CRM Data API and the Data API; directly identifiable IDs are available only to advertisers and partners who have signed the UID agreement; anonymous IDs do not require it.

    Reviewed November 2026

  6. The Trade Desk: First-Party Data Uploader, Send any ID types [P730-D06]

    Supported ID types include EmailHashedUnifiedId2 (a Base64-encoded SHA-256 hash of a normalized email address), UID2, TDID and DAID; API permissions come from the Technical Account Manager; segments are targeting or conversion; each upload uses a single-use drop endpoint.

    Reviewed November 2026

  7. The Trade Desk: Real-Time Conversion Events API [P730-D07]

    Conversion events are sent to POST /track/realtimeconversion with a supported user ID such as a UID2 or EUID token, TDID, device ID or RampID; which ID to use and access for generating it is arranged with the Technical Account Manager.

    Reviewed November 2026

  8. Amazon Ads API: Onboarding overview [P730-D08]

    To use the Amazon Ads API you must apply for access and be approved; requests are made by a Login with Amazon client application; application approval may take up to 1 business day.

    Reviewed November 2026

  9. Amazon Ads API: Events API [P730-D09]

    Amazon DSP advertisers send conversion events with POST /adsApi/v1/create/events; conversionType values include LEAD and CONTACT; each request holds 1 to 500 events; PII match keys are SHA-256 hashed; consent information is required for EU advertisers.

    Reviewed November 2026

  10. Amazon Ads API: Get started with the Data Provider API [P730-D10]

    Hashed customer records are uploaded with POST /dp/records/hashed, an audience is created with POST v2/dp/audiencemetadata/ and records are associated with PATCH /v2/dp/audience, which has a 100TPS throttle and a 1MB payload limit; PATCH /v2/dp/users removes user data.

    Reviewed November 2026

  11. Amazon Ads API: Additional setup steps for the data provider API [P730-D11]

    Access to the data provider API is requested through a Jira support ticket with the Symptom Path /dp Data Provider.

    Reviewed November 2026

  12. Data Manager API: Events overview [P730-D12]

    The Data Manager API sends Floodlight offline conversions for Google Marketing Platform products, including Campaign Manager 360, Search Ads 360 and Display & Video 360.

    Reviewed November 2026

  13. 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, 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

  14. HiveSilo: industry coverage [HS0]

    First-party description of buyer intelligence across 12 luxury niches.

    Reviewed October 2026

  15. HiveSilo: platform [HS1]

    Published intent, sales-prioritization and traffic-quality capabilities.

    Reviewed October 2026

  16. HiveSilo: integration scope [HS2]

    Named destinations, scoped activation and customer-controlled dispatch.

    Reviewed October 2026

  17. HiveSilo: security architecture [HS3]

    Documented confidential processing, BYOK and customer control.

    Reviewed October 2026

  18. HiveSilo: data handling [HS4]

    Customer identity custody, pseudonymous-data boundaries and separate account records.

    Reviewed October 2026

  19. HiveSilo: published outcomes [HS5]

    Existing first-party outcomes material, with client-reported and illustrative descriptions.

    Reviewed October 2026

  20. HiveSilo: AI agentic governance [HS6]

    Published pre-action policy checks, default denial, human checkpoints, scoped stop controls and governance receipts.

    Reviewed October 2026

  21. HiveSilo: AI implementation layer [HS7]

    Published combined implementation model for intelligence, confidential processing and AI governance.

    Reviewed October 2026

  22. 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

  23. 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

  24. 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. DSP retargeting is identified to explain the workflow; no endorsement, certification or partnership is implied.

Your next move starts with a conversation.

Contact HiveSilo

Make your next conversation count.

Tell us about your DSP retargeting workflow and the decision you want to improve.

For enterprises that want buyer intelligence delivered into the data, advertising and team tools they already run.

One quick form

These fields are qualifiers only: we use them to assess fit and to tailor our reply, never to profile you.

No spam, no list-selling. A real person replies within hours, 9am to 6pm ET, Monday to Friday.

A real person replies within hours, 9am to 6pm ET, Monday to Friday.

No spam, no list-selling.