Integrations / Marketing Automation
Postscript
Server-side delivery of subscriber events to Postscript's Custom Events API (POST /api/v2/events) to trigger SMS Flows. Matches subscribers by raw phone (E.164), email, or subscriber_id and forwards event properties for Flow filtering and merge tags.
Datafly Signal delivers first-party events to Postscript server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Postscript expects.
Why route Postscript through Datafly Signal
Profiles update from the server, not the browser
Events reach Postscript even when a tracker blocker or a failed page unload would have dropped a client-side call, so the profile reflects what actually happened.
One consent decision governs every destination
Postscript 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
add_to_cartbegin_checkoutpagepurchasesign_upview_itemVertical presets
Default. 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 Postscript documentation.
Frequently asked questions
Does Datafly Signal integrate with Postscript?
Yes. Datafly Signal delivers first-party events to Postscript server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Postscript expects. The integration is included in every deployment at no additional cost.
How is server-side Postscript tracking different from the Postscript tag?
The Postscript 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 Postscript from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Postscript?
The blueprint ships with mappings for add_to_cart, begin_checkout, page, purchase, sign_up, view_item. Any event in your schema can be mapped to Postscript through pipeline configuration without a code change.
Do I need to keep the Postscript tag on my site?
No. Signal delivers to Postscript from the server, so no client-side Postscript script is required on your site.
Other marketing automation integrations
Ready to move Postscript server-side?
See how Datafly Signal delivers first-party events to Postscript from infrastructure you control, with hashed identity and consent enforcement built in.