StackAdapt
Datafly Signal delivers conversion events to StackAdapt server-to-server for programmatic campaign attribution, audience targeting, and multi-channel performance measurement.
Why route StackAdapt 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, and Safari’s ITP shortens the cookies it can set. Signal sends the event from your own server, so the conversions StackAdapt optimises against are not filtered by the browser.
- Email is hashed before leaving your infrastructure. Signal normalises (trim and lowercase) and applies SHA-256 inside your own deployment, so StackAdapt receives match keys rather than raw personal data.
- Client IP and user agent are preserved. Server-to-server delivery normally loses both, which weakens matching. Signal forwards the genuine visitor values as request headers so StackAdapt attributes the event to the right session.
- One consent decision governs every destination. StackAdapt 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
Before configuring StackAdapt in Signal, you need:
- A StackAdapt advertiser account
- An API token generated from the StackAdapt platform
- Your Advertiser ID
Get your StackAdapt credentials
- Sign in to StackAdapt.
- Go to Settings → API and generate a new API token.
- Your Advertiser ID is shown on the account settings page.
See StackAdapt’s engineering resources for additional reference.
Configure the integration in Signal
- In the Management UI, go to Integrations → Add Integration.
- Select StackAdapt from the catalogue.
- Give the integration a name (for your reference).
- Fill in the required fields:
| Field | Required | Description |
|---|---|---|
api_token | Yes | StackAdapt API token. |
advertiser_id | Yes | StackAdapt advertiser ID. |
- Choose which pipeline(s) this integration should run on.
- Select consent categories (defaults to marketing).
- Click Save.
API endpoint
GET https://tags.srv.stackadapt.com/convAllow egress to tags.srv.stackadapt.com from the network your delivery workers run on.
Event mapping
| Signal event | StackAdapt event |
|---|---|
page | page_view |
Product Viewed | view_content |
Product Added | add_to_cart |
Order Completed | purchase |
To customise, edit the integration’s Field Mappings.
Identity
Signal sends the following identity signals to StackAdapt, subject to consent and availability:
| Capability | Notes |
|---|---|
| Hashed email | SHA-256 (lowercase, trimmed) |
| Client IP / User-Agent | Forwarded from the original request |
Consent
This integration is gated on the marketing canonical consent category.
Verify it’s working
- In the Management UI, open Pipelines → your pipeline → Live Events and trigger a test event.
- The event appears in the live feed; inspect the payload sent to StackAdapt.
- Check the StackAdapt dashboard for conversion attribution.
Troubleshooting
401 Unauthorized.
Regenerate the API token in StackAdapt and update the integration.