The documentation for mobile tracking can be a bit spread out. You linked to a tutorial, but https://developer.adobe.com/client-sdks/home/getting-started/get-the-sdk/ has some other details (and if you're on React Native, there's a whole different set of docs to keep in mind). 

By "doesn't work", do you mean you aren't seeing click events sent to AEP when looking in the network tab or AEP debugger? Is that true of all of the click events? Are your page view events working?I have the same set up as your screenshot, and do see click tracking working - you can see it at https...

I've had similar issues, where "", null, and nullify() all throw errors (eg, The source field iif(xdm.web.webPageDetails.name.equals("Subscribe"),1,"") is null or not found) when the condition isn't matched. BUT... for me it has only ever affected that field. The errors don't seem to affect anything...

I don't know about "best practices" as I'm still muddling through figuring it out myself. If you're simply mapping one XDM field to another, then it is pretty straightforward. Things get trickier once you start using calculated fields. Some tips:I will say, at least in my own experience, I've found ...

Alas, I don't think that would quite do what we need. We're feeding the responses into Marketo fields, and we really need it as JSON, but Target will only return stringified JSON. 

Beyond the great points made by @Harveer_SinghGi1, I think it's mostly a matter of preference. Personally, if the requirements for both are generally the same, I think it'd be easier to maintain a single schema, though perhaps different datastreams and/or datasets. 

Oh wow, that was on old post:). That tool does still work as far as I know, though, as pointed out, only shows your variable configurations.There is another third party tool that can also show you all your components (calculated metrics, segments, workspace projects, etc) and when/how they're used- ...

Any idea where this ticket stands? I'm having the same issue, but unfortunately can't seem to get the legacy API to work. 

I agree, I don't think the order things appears in matters nearly as much as the end results. Sounds like you're well on your way to figuring it out.

The way it usually works is, the initial gtag js will load whenever this runs:<script async src="https://www.googletagmanager.com/gtag/js?id=TAG_ID">BUT for each time you run the config line:  gtag('config', 'TAG_ID');If the Tag ID of your config line doesn't match the js you already loaded, it will...