Cancellation
Cancellation Procedure & Deactivation ABconsent CMP
To ensure the effective termination of billing and avoid costs related to residual calls (hits), a technical deactivation procedure must be strictly followed.
A simple cancellation notice by email does not cut off technical data flows. As long as the script is present on your site and the configuration is "Live," generated hits will continue to be counted and invoiced.
1. Tag Removal (De-tagging)
The first step is to remove the Sirdata source code from your digital environment to prevent user browsers from continuing to call our servers.
Hard-coded Integration: Remove the code from the
<head>section of your website.
Google Tag Manager (GTM): Pause or delete the Sirdata tag, then publish the new version of your GTM container.
2. Technical Deactivation in the Interface
To permanently stop communication between your domain and the Sirdata infrastructure, you must unpublish your configuration.
Steps to follow:
Log in to your Sirdata Dashboard.
Go to the section for your product (e.g., My CMP Configurations).
Locate the relevant configuration.
Click on the More Actions menu (...).
Select Unpublish.
Consequences of Unpublishing
Immediate Stop of Hits: No further calls are processed by our servers, thus stopping usage-based billing.
Service Inaccessibility: If the script remains on your site after unpublishing, the CMP (or DMP) will no longer load. This may block your tracking tags (Google Ads, Meta, Bing) that depend on consent signals.
Configuration Status: A "Published" configuration remains active and billable. Only the "Unpublished" status guarantees the total termination of the SaaS service.
Mis à jour
Ce contenu vous a-t-il été utile ?