Difference between revisions of "NATS4 Post URLs Usage"

From TMM Wiki
Jump to navigationJump to search
 
(18 intermediate revisions by 6 users not shown)
Line 1: Line 1:
You can have NATS post to a URL of your choosing when different biller events happen.
+
{{NATS4 Manual
 +
| show_sites_admin_section = true
 +
}}
  
[[File:postback_urls.png| 500px]]<br/>
 
  
For example, with '''Rebill Post URL''' you can have NATS post to this URL when on each rebill.
+
[[NATS4]] gives you the option of posting to a URL of your choosing when different biller events occur. This allows you to track and keep logs of [[ct#Surfer|surfers]] when they perform a specific action on your site, such as choosing a username, joining, and rebilling. You can find these settings by visiting the [[NATS4 Sites Admin|Sites Admin]], selecting "Edit" next to the tour you wish to edit, and expanding the Postback URLs section with Show/Hide Advanced Settings. For other postback examples, please check this article: [[NATS4 Postbacks and Post URLs]]
  
With each post back you have access to several fields.
+
[[File:postback_urls.png| 450px]]<br/>
  
For a list of the fields in the post please see the wiki page [[Nats4 Post URL Variables]].
+
There are additional post urls available in the 'Show/Hide Advanced Settings' for the 'Approval/Denial/Upgrade' section.
 +
 
 +
[[File:Approval denial upgrade.PNG| 450px]]<br/>
 +
 
 +
For example, with the '''Rebill Post URL''' field you can have NATS post information to your specified URL on each [[ct#Member|member]] rebill.
 +
 
 +
Continuing with the '''Rebill Post URL''' example, [[NATS]] allows you to use [[Smarty]] scripts at the URL page to further organize transaction information. The [[Smarty]] script here allows you to put your information into a log file:
 +
 
 +
<pre>
 +
<?
 +
$file = fopen("log.txt", "a");
 +
fwrite($file, print_r($_REQUEST, true));
 +
fclose($file);
 +
?>
 +
</pre>
 +
 
 +
With each post back you have access to several fields, allowing a great deal of customization in recording user transactions and information.
 +
 
 +
For a list of the fields in the post please see the wiki page [[Nats4 Post URL Variables]].<br/>
 
For an example of these fields please see the wiki page [[NATS4 Post URLs]].
 
For an example of these fields please see the wiki page [[NATS4 Post URLs]].
 +
 +
== Username Post URL vs. User Management URL ==
 +
 +
[[NATS]] can use both username post URLs and user management URLs to keep track of member details and availability. The main difference between the two is that a Username Post URL is specifically for checking username availability, and is only called on during initial signup to verify username availability. A User Management URL will get a variety of calls, including add, check, delete, expire, etc.
 +
 +
Username post URLs will send all of the following variables to your script:
 +
 +
* username
 +
* email
 +
* siteid
 +
* tourid
 +
* programid
 +
* loginid
 +
 +
Your script should echo "*exists*" if the username is already taken.  This will refresh the page a prompt the surfer to choose a new username.
 +
 +
[[Category:NATS4 Sites]]

Latest revision as of 14:17, 24 February 2018

NATS 4
Members Admin
The Members Admin
View Member Details
Add Member
MySQL Auth
Mod Authn DB
Multisite Access
Member Logging
Member Password Retrieval
OpenID Connect
Mod Auth OpenIDC
ID Numbers
Sites Admin
The Sites Admin
Sites
Site Setup
Site Templates
Tour Setup
Join Options
No Cost Registration
Special Pricing Options
Join Option Rules
Post URL Usage
Post URLs in NATS4
Approval/Upgrade/Denial Variables
Approval/Upgrade/Denial Template Variables
Mobile Tours
Token Sites
ID Numbers
Site Partner
Site User Management
Example Postbacks for Site User Management
Configure Redirects
Split A-B Testing
Username Checking
Form Validation
Post-Biller Templates
Send Information To Special Biller
Join Option Box vs Button
Qualified Join Page Hits
Allowed languages
Customize Join Form
Package Plus
Token Plus
Signup Plus
Type-In Traffic
Coupon Codes
Setting Rules
Site Groups
Options Simulator
ATVOD Verification Process


NATS4 gives you the option of posting to a URL of your choosing when different biller events occur. This allows you to track and keep logs of surfers when they perform a specific action on your site, such as choosing a username, joining, and rebilling. You can find these settings by visiting the Sites Admin, selecting "Edit" next to the tour you wish to edit, and expanding the Postback URLs section with Show/Hide Advanced Settings. For other postback examples, please check this article: NATS4 Postbacks and Post URLs

Postback urls.png

There are additional post urls available in the 'Show/Hide Advanced Settings' for the 'Approval/Denial/Upgrade' section.

Approval denial upgrade.PNG

For example, with the Rebill Post URL field you can have NATS post information to your specified URL on each member rebill.

Continuing with the Rebill Post URL example, NATS allows you to use Smarty scripts at the URL page to further organize transaction information. The Smarty script here allows you to put your information into a log file:

<?
$file = fopen("log.txt", "a");
 fwrite($file, print_r($_REQUEST, true));
 fclose($file);
?>

With each post back you have access to several fields, allowing a great deal of customization in recording user transactions and information.

For a list of the fields in the post please see the wiki page Nats4 Post URL Variables.
For an example of these fields please see the wiki page NATS4 Post URLs.

Username Post URL vs. User Management URL

NATS can use both username post URLs and user management URLs to keep track of member details and availability. The main difference between the two is that a Username Post URL is specifically for checking username availability, and is only called on during initial signup to verify username availability. A User Management URL will get a variety of calls, including add, check, delete, expire, etc.

Username post URLs will send all of the following variables to your script:

  • username
  • email
  • siteid
  • tourid
  • programid
  • loginid

Your script should echo "*exists*" if the username is already taken. This will refresh the page a prompt the surfer to choose a new username.