Integrations / Analytics
Amplitude
Server-side event tracking to Amplitude via the HTTP V2 API for product analytics, user behavior, and conversion analysis.
Datafly Signal delivers first-party events to Amplitude server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Amplitude expects.
Why route Amplitude through Datafly Signal
Your numbers stop depending on what the browser allows
Client-side analytics loses every visit where the tag is blocked or the page unloads early. Signal delivers from the server, so Amplitude receives the complete event stream.
Client IP and user agent are carried in the payload
Both are taken from the original visitor request rather than your server, which is what Amplitude needs to attribute the event to the right session.
Delivery is batched, rate-limited, and retried
Signal buffers to Kafka, respects the Amplitude rate limit, and retries on 429 or transient failure rather than dropping the event.
One consent decision governs every destination
Amplitude 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_payment_infoadd_shipping_infoadd_to_cartadd_to_wishlistbegin_checkoutcontent_likedcontent_savedcontent_sharedcontent_viewedcoupon_appliedcoupon_deniedcta_clickedfeature_usedgenerate_leadinvitation_sentloginlogoutonboarding_completedonboarding_startedpagepayment_completedpayment_failedproduct_reviewedproduct_sharedpurchaserefundremove_from_cartsearchselect_itemselect_promotionsign_upsubscription_cancelledsubscription_downgradedsubscription_startedsubscription_upgradedsupport_ticket_createdtrial_expiredtrial_startedvideo_ad_completedvideo_ad_skippedvideo_ad_startedvideo_content_completedvideo_content_startedvideo_playback_completedvideo_playback_pausedvideo_playback_resumedvideo_playback_startedview_cartview_itemview_item_listview_promotionVertical presets
Retail, B2B / SaaS, Media. 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 Amplitude documentation.
Frequently asked questions
Does Datafly Signal integrate with Amplitude?
Yes. Datafly Signal delivers first-party events to Amplitude server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Amplitude expects. The integration is included in every deployment at no additional cost.
How is server-side Amplitude tracking different from the Amplitude tag?
The Amplitude 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 Amplitude from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Amplitude?
The blueprint ships with mappings for add_payment_info, add_shipping_info, add_to_cart, add_to_wishlist, begin_checkout, content_liked, content_saved, content_shared, and more. Any event in your schema can be mapped to Amplitude through pipeline configuration without a code change.
Do I need to keep the Amplitude tag on my site?
No. Signal delivers to Amplitude from the server, so no client-side Amplitude script is required on your site.
Other analytics integrations
Ready to move Amplitude server-side?
See how Datafly Signal delivers first-party events to Amplitude from infrastructure you control, with hashed identity and consent enforcement built in.