Is this the real request adscapi sends?

Yes. The endpoint, headers, and body shape are extracted from the library dispatcher for this platform. Secrets and hashed values appear as placeholders.

Why are emails shown as ?

adscapi normalizes and SHA-256 hashes PII before dispatch. You pass raw values to track(); the platform only ever receives the hash.

Can I preview an event other than purchase?

The preview fixes one purchase example so the pages stay fast and static. The event-name table shows how every canonical event maps for this platform.

How do I send this payload myself?

Install adscapi, set the platform's secrets, and call track() with a canonical event. The library builds and posts this exact payload for you.

Tencent Ads CAPI Payload Preview

The server-side request adscapi builds when you track() a purchase and Tencent Ads is configured. Secrets and hashed values show as placeholders.

Request

POST

Endpoint

https://api.e.qq.com/v1.3/user_actions/add?access_token={TENCENT_ADS_TOKEN}&timestamp={TIMESTAMP}&nonce={NONCE}

Headers

Content-Type: application/json

Body (purchase example)

{
  "account_id": "",
  "user_action_set_id": "{TENCENT_PIXEL_ID}",
  "actions": [
    {
      "external_action_id": "order_1001",
      "action_time": 1739452800,
      "action_type": "COMPLETE_ORDER",
      "user_id": {
        "email": "<sha256(normalized-email)>",
        "phone": "<sha256(e164-phone)>"
      }
    }
  ]
}

Verified against the library dispatcher (src/dispatchers/tencent.ts). See the Tencent Ads setup guide for where to get each secret.

Required secrets

TENCENT_PIXEL_IDTENCENT_ADS_TOKEN

Tencent Ads activates when every secret is present. One missing key and the platform no-ops — the rest still receive the event.

Event-name mapping

Canonical event	Tencent Ads receives
`page_view`	`PAGE_VIEW`
`lead`	`LEAVE_INFORMATION`
`signup_start`	`signup_start` (custom event passthrough)
`signup`	`REGISTER`
`checkout_created`	`INITIATE_CHECKOUT`
`purchase`	`COMPLETE_ORDER`
`reply_generated`	`reply_generated` (custom event passthrough)
`upgrade_clicked`	`upgrade_clicked` (custom event passthrough)

Good to know

The token goes in the access_token query parameter; the dispatcher also appends a timestamp (current unix seconds) and a random nonce query parameter on every call.
account_id comes from event.properties.tencent_account_id (empty string when unset) — TENCENT_PIXEL_ID is sent as user_action_set_id.
No value or currency is sent; user_id appears only when hashed email/phone exist, which requires adUserData consent.
Unmapped canonical names pass through raw and the API rejects them — send only mapped events.

Frequently Asked Questions

Related Tools

Discover more free tools to fix your tracking

Event Payload Playground

Pick a canonical conversion event, fill the fields, and see the exact JSON payload adscapi builds — before you write a line of code.

Try it now

PII Hash Previewer

Type 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 now

Platform Coverage Explorer

Search all 26 ad platforms adscapi dispatches to — support level, required secrets, and setup docs, always in sync with the library registry.

Try it now

Ready to track Tencent Ads conversions server-side?

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

Get started npm install adscapi