Cancellation

Cancellation Procedure: Server-Side Services

Terminating a Server-Side service requires technical intervention to stop server resource allocation and end billing for processed hits.

Unlike client-side solutions, an active Server-Side container continues to consume cloud resources. Simply removing the tag from your website is not enough to stop the dedicated server instance.

1. Traffic Redirection (Client-Side)

Before shutting down the server, you must redirect or stop data transmission to the Sirdata transport URL:

• Update your tags in your Web container so they no longer point to the Sirdata endpoint.

• Remove specific clients/tags in your Server-Side GTM if you are using a hybrid architecture.

• GTM Script Update: If you have implemented URL rewriting, GTM might be loading via the created subdomain. You must re-insert the classic GTM script to ensure you do not lose any tracking.

2. Server-Side Container Deactivation

To stop infrastructure-related billing:

1. Log in to your Sirdata Interface.

2. Go to the Server-Side / My Containers tab.

3. Access the desired container.

4. Select Deactivate.

---

Key Considerations

• Residual Hits: Any hit reaching a "Live" instance will be invoiced, even if no data is forwarded to third-party platforms (Google Ads, GA4, etc.).

• Service Interruption: Deactivation will immediately cut off Server-Side data collection. Ensure you have switched your flows back to Client-Side beforehand if you wish to maintain minimal tracking.