Server-to-Server Installation

Set up backend tracking with server-to-server (S2S) installation on Blockchain-Ads, suitable for secure or app events.

This guide helps you configure S2S to send event data from your server.

Steps for S2S Installation

Configure S2S in minutes:

1. Log in to the HUB dashboard, go to "Tracking" > "Setup Tracking," and select "Server-to-Server."
2. Follow the provided instructions: copy the endpoint URL and parameters from HUB.
3. Configure your server or backend to send event data (e.g., POST request with event name, user ID, timestamp).
4. Include required parameters like event_type, value, currency for conversions.
5. Test by sending a sample event from your server.
6. Verify in the HUB Conversions tab (status changes to Verified after events received).
7. Use S2S for events like purchases or sign-ups not captured client-side.

Best Practices: Use S2S for privacy-sensitive events; include all parameters for accurate attribution; test with curl or Postman before going live; log your requests for debugging; integrate with your CRM for automatic event sending.

Troubleshooting: No events in HUB? Check the endpoint URL and parameter format. 400 error? Validate JSON structure and required fields. Data delayed? S2S processing may take 5-15 minutes. Unverified status? Send more test events or contact support@blockchain-ads.com.

Table: S2S Parameters

FAQs

• What is S2S? Backend-to-backend tracking that doesn’t require a client-side script.
• What are required parameters? Event_type, timestamp, and hashed user_id.
• How to test events? Send a sample POST request and check HUB Conversions tab.
• Is S2S for apps? Yes, ideal for mobile or server-side events.
• Security considerations? Use HTTPS for requests; hash sensitive data like user IDs.
• Multi-event setup? Create separate configurations for each event type in HUB.
• Integration with servers? Use APIs like Node.js or PHP to send POST requests automatically.