StackAdapt

This skill is a product-agnostic adapter for the shared conversion hub. It maps one canonical event to the vendor event, sends it after payment confirmation, and makes an absent STACKADAPT_TOKEN a logged no-op.

The three-layer conversion model

1. Client tag. Load the vendor pixel or approved data source on the browser.
2. Server conversion path. Send the canonical event from the server when the payment provider confirms the charge. Use one stable event ID across both paths.
3. Attribution layer. Configure the vendor conversion action and reporting surface. A 2xx response does not prove that an ad received credit.

Official tracking reference: StackAdapt pixel or measurement docs.

Client tag

Install the exact tag generated by the vendor console. Do not copy an old blog snippet or mirror a vendor script through your own CDN.

⚠ UNVERIFIED — confirm the current init call, script origin, pixel ID field, and purchase event shape at StackAdapt tracking reference.

Use STACKADAPT_PIXEL_ID or STACKADAPT_TAG_ID for the public identifier, as the vendor names it. Send event_id when the platform supports client/server deduplication.

Server-side conversion API

Server endpoint: GET https://www.stackadapt.com/ is an official API or console root, not a claimed conversion endpoint.

⚠ UNVERIFIED — confirm the current conversion POST path, authorization header, timestamp unit, deduplication field, and JSON payload at StackAdapt API documentation.

Do not invent a CAPI body from an SDK or old help article.

Get a token and validate it

1. Open the official StackAdapt console or request access from the account team.
2. Create the advertiser, pixel, data source, or API connection.
3. Generate the credential required by the official API. Store it as STACKADAPT_TOKEN.
4. Keep the credential in a server-side secret store.

StackAdapt integration details are account and partner gated. This entry remains a stub until StackAdapt publishes a stable public API reference for pixel, CAPI, token, and audience contracts.

Token validation:

curl -sS 'https://www.stackadapt.com/' -H "Authorization: Bearer $STACKADAPT_TOKEN"

⚠ UNVERIFIED — confirm the endpoint, token type, and required headers at StackAdapt authentication reference before using this command.

Audience, retargeting, and lookalike expansion

Use the platform's official site-audience, customer-list, CRM, or conversion audience workflow. Normalize email by trimming and lowercasing before SHA-256 hashing when the official product requires hashed contacts.

StackAdapt integration details are account and partner gated. This entry remains a stub until StackAdapt publishes a stable public API reference for pixel, CAPI, token, and audience contracts.

⚠ UNVERIFIED — confirm the current customer-list fields, minimum usable size, match-rate rules, lookalike product, and audience eligibility at StackAdapt audience documentation.

Verify the audience status in the console or with the official read endpoint. A successful upload response is not proof that the audience can serve.

Deduplication and event rules

• Use the payment transaction ID as the shared event ID.
• Do not require a click ID before sending a server event.
• Persist the click ID in first-party storage when the platform requires it later.
• Hash first-party identifiers only after consent. Never send raw email or phone data.
• Read the vendor's current timestamp unit. Do not assume seconds or milliseconds.

Small-budget campaign launch

• Run one audience, geo, creative, and conversion goal per test.
• Disable broad expansion, network, placement, and automatic targeting defaults until they fit the hypothesis.
• Start with traffic or click optimization when no conversion history exists.
• Set a hard spend cap where the product supports one.
• Check the campaign's review, billing, and delivery status before increasing spend.
• ⚠ UNVERIFIED — confirm current bid floors, learning thresholds, budget minimums, and default placements at StackAdapt API documentation.

Verification

Use the official test-event view, status endpoint, or reporting API. Reconcile the result with payment-provider succeeded charges. A zero count before deploy is expected. A real charge with zero platform events is a tracking failure.

⚠ UNVERIFIED — confirm the current event-test or reporting query at StackAdapt API documentation.

Hub conventions

Pair this skill with ad-conversion-hub for canonical taxonomy, consent, hashing, secret names, and multi-platform dispatch. Pair it with ad-experiments for seed sizing, narrow tests, PII-export authorization, and ground truth. Keep this adapter thin. A vendor error must not fail checkout or a payment webhook.

Common pitfalls

• A browser tag can fire while server events remain absent.
• A successful upload can return partial warnings or a non-servable audience.
• Partner-gated APIs often need account approval before a token works.
• Build-time secrets need a redeploy after they change.
• Do not infer attribution from the presence of an event in a debug view.

Security

Load client code only from the vendor's official HTTPS origin. Keep STACKADAPT_TOKEN server-side. Never log or commit it. Send only consented and hashed identifiers.

Official sources checked (2026-08-11)

• https://www.stackadapt.com/
• https://www.stackadapt.com/