Server-to-Server (S2S) Postback Integration

14 min

overview server to server (s2s) postback integration allows advertisers to send measurement and conversion events directly to momentscience from their server this method provides a reliable way to track conversions without requiring client side implementation on conversion pages when momentscience sends traffic to your landing pages, we include an adpx click id parameter in the url you store this identifier with the user session, then send it back to us via postback when conversions occur key benefits no client side dependencies track conversions without javascript, ideal when browser based tracking is restricted or unreliable multi event attribution record multiple conversion actions per user session with dynamic payout values privacy compliant meet gdpr/ccpa requirements with server side data handling cross platform support works with mobile apps, backend systems, and any environment that can make http requests prerequisites before you begin, ensure you have technical capability to capture url parameters from incoming traffic server infrastructure to store click identifiers and trigger postbacks how s2s postback works momentscience sends traffic to your landing page with adpx click id parameter your system captures the adpx click id and stores it with the user session user completes an action (purchase, signup, etc ) your server sends a postback to momentscience with conversion details integration steps step 1 capture the click id from incoming traffic when momentscience sends traffic to your landing page, capture the adpx click id parameter from the url and store the adpx click id value with the user's session the method depends on your technology stack the adpx click id must be stored reliably if this value is lost, you won't be able to attribute conversions back to momentscience example landing page url https //yourdomain com/landing page?adpx click id=abc123def456\&other param=value step 2 configure your postback url configure your system to send postbacks to the momentscience tracking endpoint examples track a measurement event \https //trk pubtailer com/track/?click id={adpx click id}\&measurement=1\&event={event}\ track a payable event (cpa only) \https //trk pubtailer com/track/?click id={adpx click id}\&measurement=1\&event={event}\&payout={payout}\ track a payable event with sale value (roas) \https //trk pubtailer com/track/?click id={adpx click id}\&measurement=1\&event={event}\&payout={payout}\&sale amount={amount}\ for the event parameter, you can use any event identifier that your offer supports common choices include mosci , conversion , purchase , or any custom event name url parameters reference parameter type required description click id string yes the adpx click id value received from incoming traffic measurement integer conditional must be set to 1 required whenever you send an event , with or without a payout event string conditional event type identifier (e g , purchase , signup , conversion ) required for event based and variable payout tracking; can be sent without payout for no payout event tracking payout decimal conditional payout amount for the conversion in usd (e g , 25 50 ) only required when the event carries a payout, omit it for no payout event tracking sale amount decimal no sale amount for cps goal tracking step 3 trigger postbacks on conversion events when a user completes a conversion action, send a postback to momentscience with the stored adpx click id example postback urls signup event (no payout) curl x get "https //trk pubtailer com/track/?click id=abc123def456\&measurement=1\&event=signup" h "accept / " h "cache control no cache" purchase event with payout curl x get "https //trk pubtailer com/track/?click id=abc123def456\&measurement=1\&event=conversion\&payout=25 00" h "accept / " h "cache control no cache" lead generation curl x get "https //trk pubtailer com/track/?click id=abc123def456\&measurement=1\&event=lead\&payout=5 00" h "accept / " subscription with payout and sale amount (for cps) curl x get "https //trk pubtailer com/track/?click id=abc123def456\&measurement=1\&event=subscription\&payout=29 99\&sale amount=149 99" h "accept / " use lowercase event names with underscores (e g , profile complete , trial start ) keep names descriptive but concise, avoid special characters except underscores, and limit to 50 characters maximum you can send multiple postbacks for the same adpx click id if multiple conversion events occur for example, a user might sign up (first event) and then make a purchase (second event) within your defined conversion window postback response codes momentscience returns http status codes to indicate the result of your postback request status code meaning action required 200 ok conversion successfully recorded no action needed do not resend any other status request failed or error occurred retry the request with exponential backoff only retry postbacks that receive a non 200 status code if you receive a 200 ok response, the conversion has been recorded successfully and should not be sent again if you encounter any issues during integration or have questions about s2s postback tracking, contact us help\@momentscience com mailto\ help\@momentscience com