<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tool Governance on</title><link>https://carney.wiki/tags/tool-governance/</link><description>Recent content in Tool Governance on</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Wed, 15 Feb 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://carney.wiki/tags/tool-governance/index.xml" rel="self" type="application/rss+xml"/><item><title>Building the machine</title><link>https://carney.wiki/blog/whats-your-martech-stack-look-like/</link><pubDate>Wed, 15 Feb 2023 00:00:00 +0000</pubDate><guid>https://carney.wiki/blog/whats-your-martech-stack-look-like/</guid><description>Documenting your Martech stack What&amp;rsquo;s your standardized Martech stack? Do you know what&amp;rsquo;s running? Do you know the overlaps and are you willing to accept them?
The purpose of documenting the stack is to consolidate for continuity and control. Some of the vendors you work with may collect PII (Personal Identifiable Information) or PD (Personal Data) on your behalf or may not integrate into your databases of record for subscription management.</description></item></channel></rss>