Add 3rd party pixel

Again, this will really depend on what type of pixel you are using, and the code will be specific (with a few modifications) to that pixel.

For instance, I like to initialize my variables at the start (I pull the data element values using _satellite.getVar(), just so I can use a nice short name in the code) and I like to add try/catch to ensure that if something fails, it fails more gracefully. Then I determine in one chunk of code (for page level tracking) based on page type, what pixels will fire...

In this sample:

• Add the providers code to the page (technically this is optional, if your developers already have the providers code on the site, then you may not need this... but odds are, you are trying to add completely new pixel(s)
• Trigger the init (you may want to add some code to check if the pixel has already been initialized
• Trigger the standard "pageview" pixel
• Check page type
  • if "article" then trigger the view content pixel
  • if it's a "purchase-success" then trigger a purchase pixel
  • if it's "another-page" then trigger a custom pixel

var pixelId = _satellite.getVar('PixelId');
var pageType = _satellite.getVar('PageType');

try {
  !function(f,b,e,v,n,t,s){if(f.fbq)return;n=f.fbq=function(){n.callMethod?
  n.callMethod.apply(n,arguments):n.queue.push(arguments)};if(!f._fbq)f._fbq=n;
  n.push=n;n.loaded=!0;n.version='2.0';n.queue=[];t=b.createElement(e);t.async=!0;
  t.src=v;s=b.getElementsByTagName(e)[0];s.parentNode.insertBefore(t,s)}(window,
  document,'script','https://connect.facebook.net/en_US/fbevents.js');
}
catch (e){
}

fbq('init', pixelId);
fbq('track', 'PageView');

if (pageType === "article"){ 
  fbq('track', 'ViewContent'); 
} 
else if (pageType === "purchase-success"){ 
  fbq('track', 'Purchase', {value: 0.00, currency: 'USD'});
}
else if (pageType === "another-page"){
  fbq('trackCustom', 'CustomEvent', {value: "x"}); 
}

If I need to trigger multiple different types of pixels on the same pages, I can use the same structure... but in that case I may want to wrap the main code for each pixel in it's own try/catch, then use the same if statement to drive the pixels like:

var fbPixelId = _satellite.getVar('FBPixelId');
var twitterPixelId = _satellite.getVar('TwitterPixelId');
var otherPixelId = _satellite.getVar('OtherPixelId');
var pageType = _satellite.getVar('PageType');

// FB Code
try {
  !function(f,b,e,v,n,t,s){if(f.fbq)return;n=f.fbq=function(){n.callMethod?
  n.callMethod.apply(n,arguments):n.queue.push(arguments)};if(!f._fbq)f._fbq=n;
  n.push=n;n.loaded=!0;n.version='2.0';n.queue=[];t=b.createElement(e);t.async=!0;
  t.src=v;s=b.getElementsByTagName(e)[0];s.parentNode.insertBefore(t,s)}(window,
  document,'script','https://connect.facebook.net/en_US/fbevents.js');
}
catch (e){
}

// Twitter Code
try {
  !function(e,t,n,s,u,a){e.twq||(s=e.twq=function(){s.exe?s.exe.apply(s,arguments):s.queue.push(arguments);
    },s.version='1.1',s.queue=[],u=t.createElement(n),u.async=!0,u.src='//static.ads-twitter.com/uwt.js',
    a=t.getElementsByTagName(n)[0],a.parentNode.insertBefore(u,a))}(window,document,'script');
}
catch (e){
}

// Other Code
try {
  // code from other service here
}
catch (e){
}

fbq('init', fbPixelId);
fbq('track', 'PageView');
twq('init',twitterPixelId);
twq('track','PageView');
// Init and PV trigger for "otherPixel" here

if (pageType === "article"){ 
  fbq('track', 'ViewContent'); 
  // there no specific pixels here, so only FB is loaded
} 
else if (pageType === "purchase-success"){ 
  fbq('track', 'Purchase', {value: 0.00, currency: 'USD'});
  // Add other pixel "purchase" event here
}
else if (pageType === "another-page"){
  fbq('trackCustom', 'CustomEvent', {value: "x"}); 
  // Add other pixel "custom event" here
}

For pixels that trigger on clicks, you could use similar code to above... but remember, the code should already be on the page and has been initialized... so you would only need to trigger the pixel, and your clicks would already be specifically targeted so you probably won't need the if statements, unless there is some extra logic to only fire on the clicks under certain conditions.

If you use the extension as suggested, I don't know of any "all in one / generic" extension, since each system has its own code and syntax.

Extensions are a valid way to add the code, but for my uses, I didn't really want to install multiple extensions and create a lot of different rules to trigger all our pixel needs (and this is assuming that there is an extension for everything you need... major players like FB and Twitter have extensions, but some other systems may not)

Whichever way you go, I'm sure you will get it working in no time.