Tealium Learning Center

I've had a similar situation with another vendor's tag, where there were multiple keys for different sites.   **This way is advanced, however when in place, a tidier way to link multiple API keys to the tag - Consult Tealium before comitting to this route**   Within the tag template for Soasta M-Pulse you can view the actual javascript made to call the Soasta tag; at this point I haven't tested on the Soasta tag itself, but it appears to be rather similar to a tag in which I have used this method on. The only downside to this is that the maintainence is limited to editing this version of the Soasta template and therefore some options (such as the api key option) in the menu will no longer work.   Anyhow, here goes:   1.) Open up the tag template for Soasta through "Manage Templates". 2.) Copy code into a Text Editor, handy having syntax colouring on as it makes it easier to read 3.) Look for the section of the code which normally pulls in the API key from the tag, labelled "##UTVARconfig_apikey##". This is where the tag menu is setting the api key that you enter in; this is where we need to dynamically set the API Key. 4.) My recommendation is to set up a function which looks at a particular parameter on the page that identifies which site you're on and then sets the key based on that parameter. For example see below if I was to set this up by document.domain:   var setApiKey = function(domain) { var apiKey = ""; if(domain == "www.test123.com") { apiKey = "abc123"; } else if(domain == "www.123test.com") { apiKey = "123abc"; } else { //Catch all apiKey = "321cba"; } return apiKey; } All I would need to do now in terms of the Soasta template code would be to edit the string which is being generated "js.src":   doc.open()._l = function () { var js = this.createElement("script"); if (dom) this.domain = dom; js.id = "boomr-if-as"; // This is where the key needs to be generated js.src='//c.go-mpulse.net/boomerang/' + setApiKey(document.domain); // End BOOMR_lstart = new Date().getTime(); this.body.appendChild(js); };   A really important thing to remember if you're thinking of doing it this way is that the variable which you're checking against needs to be populated before this tag fires every single time otherwise each hit might be defaulted to the catch all API key.   Now in terms of "certain pages", it might be worth you giving us an example and if possible a description of how many pages you're looking to get this tracked on as you might be able to use a positive list of pages to match in the same template.   **This is untested as I don't have genuine API keys for Soasta, but is a very similar method I used for a very similar vendor tag**   ... View more

Hi @andre_molnar,   Another option to the above, if you're still wanting to use the same eVar would be set up a success event along side setting your eVar.   So eVar75 = "mini" and event75   When setting up your eVar, tell Adobe in the Admin Panel that it expires on seeing event75.  Very similar to how the Purchase event works with an eVar set up to capture Order IDs on an ecommerce site.   That way when eVar75 is seen, it also sets event 75 and then resets the eVar. List Vars are very scarce in Adobe SiteCat, so be very wise how and when you use them :-)   To be honest, I'd have to agree with the above and potentially re-think a different way of doing this   Thanks,   Tom ... View more

Hi @alex_clemmons,   Yes they are, you can put both your plugins AND doPlugins code into an extension and scope it to your site catalyst tag.   Plugins are the standard Adobe plugins that they support out of the box; we pretty much use them all in our s_code.js. doPlugins are the customised functions which you may want to add yourself (depending on how advanced you are with javascript).   Here at my company, we heavily rely on doPlugins to rebuild data before sending off to Site Catalyst.  ... View more