adMarketplace
Datafly Signal sends conversion and engagement events to adMarketplace’s Advertiser Event Data API, tied to the prior adMarketplace search click.
Why route adMarketplace through Datafly Signal
- Conversions survive ad blockers and tracking prevention. A browser tag served from an advertising domain is blocked outright for part of your traffic. Signal sends the event from your own server, so the conversions adMarketplace optimises against are not filtered by the browser.
- One consent decision governs every destination. adMarketplace is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
- No vendor tag on the page. Removing it removes its page weight and its independent access to your visitors.
Prerequisites
Get your credentials and event IDs
adMarketplace gives its API documentation to partners only. Ask your adMarketplace representative for the API endpoint URL, an access token, your advertiser ID and an event ID for each event you track.
Capture the click ID
adMarketplace appends a click ID to your landing page through a URL decorator. Collect it in Signal with an ID provider named admarketplace_click_id reading that parameter.
Configure in Signal
Configuration fields
| Field | Required | Description |
|---|---|---|
api_endpoint_url | Yes | The Advertiser Event Data API endpoint supplied by your adMarketplace representative. |
access_token | Yes | The Bearer token adMarketplace issued for the Advertiser Event Data API. Sent as ‘Authorization: Bearer <token>’. |
advertiser_id | Yes | Your adMarketplace advertiser ID (advertiser-id), sent on every request. |
event_id_page | No | The adMarketplace event-id for Page events. Leave blank to not send them. |
event_id_view_item_list | No | The adMarketplace event-id for Product List Viewed events. Leave blank to not send them. |
event_id_view_item | No | The adMarketplace event-id for Product Viewed events. Leave blank to not send them. |
event_id_add_to_cart | No | The adMarketplace event-id for Product Added events. Leave blank to not send them. |
event_id_remove_from_cart | No | The adMarketplace event-id for Product Removed events. Leave blank to not send them. |
event_id_view_cart | No | The adMarketplace event-id for Cart Viewed events. Leave blank to not send them. |
event_id_add_to_wishlist | No | The adMarketplace event-id for Product Added To Wishlist events. Leave blank to not send them. |
event_id_search | No | The adMarketplace event-id for Products Searched events. Leave blank to not send them. |
event_id_begin_checkout | No | The adMarketplace event-id for Checkout Started events. Leave blank to not send them. |
event_id_add_payment_info | No | The adMarketplace event-id for Payment Info Entered events. Leave blank to not send them. |
event_id_purchase | No | The adMarketplace event-id for Order Completed events. Leave blank to not send them. |
event_id_refund | No | The adMarketplace event-id for Order Refunded events. Leave blank to not send them. |
event_id_generate_lead | No | The adMarketplace event-id for Lead events. Leave blank to not send them. |
event_id_sign_up | No | The adMarketplace event-id for Sign Up events. Leave blank to not send them. |
Management UI setup
- Go to Integrations > Add Integration > adMarketplace.
- Choose a preset: Default (
default), E-commerce (ecommerce), Insurance (insurance). - Fill in the fields above and click Save.
Request format
GET <API endpoint URL>?advertiser-id=ADV-42&event-id=EV_PURCHASE&click-id=456825931450256319
&conversion-time=2026-09-22T00:13:20Z&conversion-time-source=1&custom-info=order_completed
&order-value=259.99&unique-id=ORD-1001
Authorization: Bearer <access token>An event whose event ID is blank in the integration settings is not sent. adMarketplace recommends at most 200 requests per second and URLs up to 4,096 characters.
Event mapping
| Signal event | Vendor event | Presets |
|---|---|---|
page | page_view | Default, E-commerce, Insurance |
view_item | product_viewed | Default, E-commerce |
add_to_cart | product_added | Default, E-commerce |
begin_checkout | checkout_started | Default, E-commerce |
purchase | order_completed | Default, E-commerce, Insurance |
view_item_list | product_list_viewed | E-commerce |
remove_from_cart | product_removed | E-commerce |
add_to_wishlist | product_added_to_wishlist | E-commerce |
view_cart | cart_viewed | E-commerce |
search | products_searched | E-commerce |
add_payment_info | payment_info_entered | E-commerce |
refund | order_refunded | E-commerce |
generate_lead | lead | Insurance |
Events not listed are not sent (the presets drop unmapped events). Each preset turns on the strict output contract, so only the mapped fields are sent.
Identity
Attribution is by the adMarketplace click ID. No personal data is sent.
Limitations
- adMarketplace publishes no API reference. The request follows adMarketplace’s partner integration on MetaRouter (read 2026-09-22); confirm it with your adMarketplace representative before going live.
Vendor documentation
adMarketplace (read 2026-09-22).