Pick a canonical conversion event, fill the fields, and see the exact JSON payload adscapi builds — before you write a line of code.
track(). adscapi maps and hashes it per platform.{
"name": "purchase",
"transactionId": "order_1001",
"value": 49.99,
"currency": "USD",
"consent": {
"adUserData": true,
"adPersonalization": true
}
}Pass this object to adscapi.track(). The library maps the event name, SHA-256 hashes the identity fields, and dispatches to every configured platform.
Each platform receives its native event name. Platforms without a mapping get the canonical name as a custom event.
PurchaseRedditPURCHASETikTokPurchaseLinkedInPURCHASEPinterestcheckoutSnapchatPURCHASEX (Twitter)purchaseAmazon AdsOFF_AMAZON_PURCHASESQuoraPurchaseBaidupurchaseTencent AdsCOMPLETE_ORDERLINEpurchaseYahoo! JapanpurchaseYandexpurchaseGA4 (Google Analytics)purchaseYelppurchaseNextdoorpurchaseRokuPURCHASETaboolapurchaseVKpurchaseDouyinactive_payKuaishou3Weibo1007ChatGPTorder_createdBing (Microsoft Ads)purchaseOutbrainpurchaseDiscover more free tools to fix your tracking
The exact Conversions API request adscapi sends per platform — endpoint, headers, and JSON body for a real purchase event, straight from the library dispatchers.
Try it nowType a raw email or phone number and see the normalized value plus its SHA-256 hash — the exact rules adscapi applies per platform. Nothing leaves the browser.
Try it nowSearch all 26 ad platforms adscapi dispatches to — support level, required secrets, and setup docs, always in sync with the library registry.
Try it nowadscapi is free and open source. Set your platform tokens, call track() once, and every configured Conversions API receives the event — hashed the way each platform expects.