Note: You are viewing an old version of this page. View the current version.

Differences between version 16 and previous revision of RobertButler.

Other diffs: Previous Major Revision, Previous Author

Newer page: version 16 Last edited on Tuesday, 28 March 2017 10:54:19 by RobertButler Revert
Older page: version 15 Last edited on Tuesday, 28 March 2017 10:54:02 by RobertButler Revert
@@ -20,43 +20,4 @@
  # Processed 
  # Returned 
  # OptOuts 
  # Cache 
-<<<<<<< Your version  
-=======  
-  
-== Tables  
-  
-* === Campaigns  
- # id  
- # name  
- # status  
- # created_on  
- # updated_on  
-* === Processed  
- # id  
- # idnum  
- # status  
- # timestamp  
-* === Returned  
- # id  
- # group  
- # status  
- # timestamp  
-* === OptOuts  
- # id  
- # idnum  
- # reason  
- # timestamp  
-* === Cache  
- # idnum  
- # first  
- # middle  
- # last  
- # address  
- # city  
- # state  
- # zip  
- # entered  
- # submttd  
- # uid  
->>>>>>> Other version  

version 16

EMAIL CAMPAIGN MANAGER DESCRIPTION

  • Email Manager Back-end Component

    1. Manages Email Campaigns internally
    2. Requests email tokens from the front-end (PHP) website.
    3. Delivers emails to addresses with with thankyou and optout tokens, taking note of bounces.
    4. Updates shared database (SQLite, Pgsql?) for the front-end to be able to display campaign status

  • Email Manager Front-end Component

    1. written in PHP, uses shared database to update user(s) on campaign status, progress, bounces, opt-outs, etc.
    2. Uses kohana Web/MVC framework.
    3. Requests Campaign information (create, delete, start, stop, etc.)

Database Schema

  • Tables

    1. Campaigns
    2. Processed
    3. Returned
    4. OptOuts?
    5. Cache