Integrations / Attribution
ShareASale
Server-to-server affiliate conversion tracking for ShareASale (an Awin network). Registers sales and leads against your Merchant ID by calling the sale.cfm tracking endpoint, crediting the referring affiliate via the captured ShareASale click identifier (sscid) or your order ID. No PII is hashed or sent — ShareASale attributes on the click ID + order ID alone.
Datafly Signal delivers first-party events to ShareASale server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload ShareASale expects.
Why route ShareASale 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 ShareASale optimises against are not filtered by the browser.
One consent decision governs every destination
ShareASale is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
What ships in the blueprint
Mapped events
_comment_conversion_onlygenerate_leadpurchaseVertical presets
Default, Retail. Each preset starts from a working configuration for that vertical rather than a blank field map.
Full field mappings, configuration fields, and troubleshooting are in the ShareASale documentation.
Frequently asked questions
Does Datafly Signal integrate with ShareASale?
Yes. Datafly Signal delivers first-party events to ShareASale server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload ShareASale expects. The integration is included in every deployment at no additional cost.
How is server-side ShareASale tracking different from the ShareASale tag?
The ShareASale tag runs in the visitor's browser, so it is subject to ad blockers, tracking prevention, and page-unload races. Signal collects the event through a first-party endpoint on your own domain and delivers it to ShareASale from your server, so delivery does not depend on browser conditions.
Which events can Signal send to ShareASale?
The blueprint ships with mappings for _comment_conversion_only, generate_lead, purchase. Any event in your schema can be mapped to ShareASale through pipeline configuration without a code change.
Do I need to keep the ShareASale tag on my site?
No. Server-side delivery is designed to replace the tag. Most teams run both briefly during migration, using shared event IDs so ShareASale deduplicates, then remove the tag once server-side volume matches.
Other attribution integrations
Ready to move ShareASale server-side?
See how Datafly Signal delivers first-party events to ShareASale from infrastructure you control, with hashed identity and consent enforcement built in.