Which fields should be mandatory in a tracking change ticket?
Mandatory: Purpose of the change, affected websites or apps, affected tags and tools, data points, recipients, third-country reference, consent category, legal basis per purpose, risk assessment, test plan, rollback plan, owner, go-live date, evidence such as preview screenshots and updated web service documentation. Services: /es/leistungen
Consulting & Next Steps
If this topic is relevant to your organization, you can book a suitable consultation or module directly.
Schema (copy & paste)
<script type="application/ld+json">{"@context": "https://schema.org", "@type": "Article", "@id": "https://www.lj-partner.com/wissensdatenbank/welche-felder-sollten-in-einem-tracking-change-ticket-pflicht-sein#article", "headline": "Welche Felder sollten in einem Tracking Change Ticket Pflicht sein?", "description": "Pflicht: Zweck der Änderung, betroffene Websites oder Apps, betroffene Tags und Tools, Datenpunkte, Empfänger, Drittlandbezug, Consent Kategorie, Rechtsgrundlag", "url": "https://www.lj-partner.com/wissensdatenbank/welche-felder-sollten-in-einem-tracking-change-ticket-pflicht-sein", "inLanguage": "de", "author": {"@type": "Person", "name": "Lars Jurischka"}, "publisher": {"@type": "Organization", "name": "LJ & Partner", "url": "https://www.lj-partner.com"}}</script>
Book now