View source for MAS:NATS codes


== Preservation of NATS referring codes throughout MAS tour pages ==

In case you are using [https://www.toomuchmedia.com/pp_nats.htm NATS] by TooMuchMedia, you need to take special care about your affiliate referring codes to make sure they are properly carried over through all MAS-generated tour pages all the way to the join page. Otherwise your affiliates might not get credited for the traffic they referred.

Note that nothing of this will be required if you use [http://mpa3.com MPA3] by Mansion Productions!


Most likely NATS have provided a code like this to use at the join links:
* <code><a href="//<tt>join.site.com</tt>/signup/signup.php?nats=<?=$_REQUEST['nats']?$_REQUEST['nats']:'<tt>MDowOjE</tt>'?>&amp;step=2"><tt>JOIN</tt></a></code>

Do not use that, but follow the steps below.


At the top of all of your tour templates put this piece of code:

<syntaxhighlight lang="php">
<?php if (!$uvar) { if ($nats) $uvar=$nats; else $nats='MDowOjE'; } else { if (!$nats) $nats=$uvar; } ?>
</syntaxhighlight>
and there replace <code>MDowOjE</code> with your NATS code for default type-in tracking.


Then, further down the template, use this code to link to join page:
* <code><a href="<tt>//join.site.com</tt>/signup/signup.php?nats=<?=$nats;?>&amp;step=2"><tt>JOIN</tt></a></code>
Of course, edit the link above to match your site actual join page, the <tt>&step=</tt> parameter etc. The only important MAS-related thing in this link is this part: <code>?nats=<?=$nats;?></code>

The cross-assignment between the <tt>nats</tt> and <tt>uvar</tt> variables makes sure that the code will be carried over through any MAS-generated page links (result of <code>[ahref] [groupref] [relref] [nextpage] [prevpage] [pages]</code> tags), it will make it through the gallery and container pages as well. 



== Carrying the nats/uvar variables between pages in the main navigation. ==

MAS will be taking care of adding the uvar/nats variables to page links it has generated, but will not do it to any hard-coded links in the templates, including the main site navigation.
To do so, you have to use append the tag <code>[uvarpass]</code> to all such links, for example:
* <code><a href="show.php?a=101_1<tt>[uvarpass]</tt></code>
* <code><a href="index.php<tt>?[uvarpass]</tt></code>
Note, in the second example, if the URL you're appending <code>[uvarpass]</code> to does not contain a query string ''(a question mark followed by list of name=value parameters)'', you need to add the question mark before the tag.

To pass the nats code to an external page (not one of the MAS aux files):
: append <code><?=$nats?"<tt>?</tt>nats=$nats":"";?></code> to the link URL if it does not have a query string, or
: append <code><?=$nats?"<tt>&</tt>nats=$nats":"";?></code> to the link URL if it does 
For example:
* <code><a href="/blog/<tt><?=$nats?"?nats=$nats":"";?></tt>">BLOG</a></code>
* <code><a href="/script.php?a=1&b=2<tt><?=$nats?"&nats=$nats":"";?></tt>">title</a></code>


== Carrying the nats/uvar variables through search functions ==

If your tour templates are utilizing MAS search functions, then follow the guidelines below; otherwise - ignore.

* In search forms, located in section templates, the following code must be added beneath the hidden input form fields:
: <code><?=($uvar?'<input type="hidden" name="uvar" value="'.$uvar.'">':"");?></code>

* In JavaScript search() functions (copied from the MAS manual), the last line of code (somewhere present with <code>eval('self.location...')</code>, somewhere with <code>'location.href=...</code>) must be changed to:
: <code>location.href="search.php?q="+what+"&sid="+SearchPageID+"&ref="+HomePageID+"&at="+SearchAt<tt><?=($uvar?'+"&uvar='.$uvar.'"':"")?></tt>;</code>

: Pay special attention if your template implementation of the <tt>search()</tt> function does include a <code>"&categories=..."</code> value in that line of code, or looks somewhat different than the above example. If it does, please contact support for additional help with the correct syntax.