AnsweredAssumed Answered

Facebook Atlas tagging issue - help please!

Question asked by 425726de269336bd613bbd6d3a1efcbb12c23da5 on Jan 26, 2017
Latest reply on Feb 12, 2017 by 5af8ea3707752b24bdd22d6b6fcbc24337e657cf

Hi community!


We are trying to implement an Atlas dynamic tag within our Marketo assets (specifically eDMs) so we can track user registered opens and clicks.


Atlas dynamic tracking tags are macro-enabled to streamline campaign creation and tagging setup to align with Atlas measurement. This enables us to leverage the macros in platforms ((in this case Marketo) outside of Atlas to avoid creating create a large of amount of Atlas tracking tags. Instead, the values generated from these macros are sent directly in the Atlas view and click tags and Atlas will automatically store and report out on all the different combinations of values passed to Atlas.


In terms of macros for Marketo, we’ve identified we can potentially use the Marketo tokens as the macros and input them into the code. The first token we’ve used is the token using the label: {{ me}}


As a test, we used this program token and put it into an Atlas view tag and then placed the code into an email template in the hope it would fire an open or a ‘view’ in Atlas, unfortunately this hasn’t worked and we’re currently going back and forth with Atlas to identify the issue, but aren't getting anywhere.


The question now is, has anyone tried to implement an Atlas dynamic tracking tag or any dynamic tracking tag which uses the marketo tokens into an email template?  And if so, is there any insight you could please give us on what we might be doing wrong?


Below is a link of the tag used :;adv=11232200877684;ec=11232200918161;c.a={{}};s.a={{}};p.a={{}};as.a={{}};a.a={{}};



I have also attached screenshots from Atlas’s guide to creating these tags in external profiles.


Many thanks