Build a first generation Coregistration application for HealthGuru Platform

[khaled]

Construct a version 1 Coregistration application that allows for offers to be created in the back office and users to accept the offers on the front end.

[khaled]

See attached files for mockup and art for use with CoRegistration?.

[khaled]

Contains closed (transfered) tickets #55 and #91

[khaled]

Delaying release to Beta 12 (clean up) release. Most Coreg functionality will exist in Beta 11, but will be suppressed by maintaining inactive or empty offers.

[khaled]

Handles four forms of coregistration:

Video Watch Page (/content/video/watch/XXXXXX).
Survey Question Page (/applications/survey/srvyid/X).
Survey Results Page (/applications/surveyresults/sryvid/X).
User Registration Page (/user/register).

CoReg? utilizes four main functional tables to handle the various information process:
hg_coreg_offers
hg_coreg_partners
hg_coreg_campaigns
hg_coreg_protocols

A number of secondary (support) tables are used and Coregistration also leverages the Registrant Model and the Custom Fields Model and their associated tables.

Coreg introduces a model of it's own Coregistration Model (CoregModel?) and the support Class Coregistration.

The back office requires the user to provide information for Transmission Protocols, Partners, Campaigns, and Offers. Additionally, the user needs to upload special Media packs for coregistration offers. The user is also required to provide the name map between the offer's custom fields and the field names being used by the partner protocol.

Coreg currently only supports HTTP/GET transfer methods. As additional protocols are provided, support will be extended.

There is a current known bug with the Parameter matching. Parameter offer matching is thus not supported at this time.

[brent]

Comments from Brent 062309

1. need DDLB's in lightboxes
2. Would be nice if we could replace the co-reg boxes w/artwork to function as a submit button
3. Would be nice to see some motion in the watch page co-reg offer box so that it comes in after a few seconds and leaves if user closes.
4. would like to suppress co-reg displays when googlebot comes for a visit
5. would like to see reporting to include the following

• Abandons (by campaign, offer, user, Etc...)
• transmissions (by campaign, offer, user, Etc...)
• daily activity
• Earned revenue (reqires storage of cpm/cpa)

[brent]

6. all offers should have close boxes... if the user closes the offer it should dissapear and that offer should not be shown again to that user.
7. the display box should grow to fit all of the copy on the watch page.

[brent]

8. Results from Cross-Browser tests

- Firefox -
User Registration Page (/user/register) display is all jacked up and only shows one offer.

• IE6 -

Video Watch Page (/content/video/watch/XXXXXX) display is off.
Survey Question Page (/applications/survey/srvyid/X). display is off.
User Registration Page (/user/register). Only shows one offer at a time

• IE7 -

Video Watch Page (/content/video/watch/XXXXXX) display is off.
Survey Question Page (/applications/survey/srvyid/X). display is off.
User Registration Page (/user/register). Only shows one offer at a time

• IE8 -

(not tested)

• Safari -

(not tested)

[khaled]

Current Fix Report:

1. Fixed, Custom Fields now support two types of drop down boxes, dates and comboboxs. If a combobox is specified, the user must supply a list of options for the combo box. The format of this list is <value1>:<name1>,<value2>:<name2>,<value3>:<name3>...
2. In progress. Trying to implement a simple templating system for offers.
3. Coreg offer slides in after x seconds (currently x is 1, can easily be altered). Requires a fix to the Watch Page Video holder box. Currently the slide in causes issues with the box display. Fix in progress (see 7).
4. Coreg should be suppressed for any HTTP_USER_AGENTS that have Googlebot in their name.
5. In progress. Reporting manager is done, needs integration with Coreg logging.
6. All offers now have close boxes. Need to do some additional cleanup when boxes close.
7. In progress. Reworking how the whole stupid watch page works.

Notable: We can now run tests against the Ever Save Prospectiv sample. There is some content work to do to make it happen, but I'll add that.

[khaled]

Current Fix Report:
2. In progress. May release without this feature at this time / implementation is relatively trivial but needs some design input for sizing and controls.

5. Rudimentary reporting in place (simple activity records, request results, clicks). The goal here is to develop some richer information tools that compare some additional factors such as abandonment (user with session id clicks on item, but then never performs a send). Also, aggregate reporting is probably needed (some way of looking at each in terms of unique user clicks, clicks versus requests). Additionally, filtering by campaign or partner is probably useful.

7. Watch page functionality has been recoded. Currently awaiting style / front-end fixing. See ticket #114.

[khaled]

Current Fix Update:

2. Mostly done. Requires an additional image size definition for full size coreg offers.

[khaled]

Issues and resolutions:

1. Drop down boxes added to the sign up form.
2. Basic full button version of coreg has been added for Video Watch page. This will be extended to the other coreg locations (survey questions and results, registration). Will release with only first version since there is still some work to do to make this work.
3. Coreg Offer Slides in after a specified number of seconds (modifiable).
4. Googlebot does not see Coreg
5. Basic reporting in place. Will be expanded to include requested reports. Building aggregation extensions to the report maker as well as graphical (chart) generation.
6. Rejected offers are gone for good.
7. Watch page changes allow for growing content in the coreg box.

Tested in Firefox 3.5, 3.0 and IE 7

Known bug: Getting a local (dev server) error with displaying the eversave ad on Sex and WWW video watch pages. No ad is delivered. May be a problem with the channel naming system (in which case it is an artifact of the dev server).

[brent]

8. phone field does not work when entered without dashes.... should either show as 3 separate boxes or put the dashes in automatically

9. we should be able to control the order the fields appear for an offer

10. after completing an offer it should close out the box.

11. should be a way to control the format a field is delivered based on the advertiser raqther based solely on the field confirguration

12. we probably ought to hide the co-reg offer prior to sliding it in and give it another second before it appears.

[khaled]

Fix Report (Khaled)
8. Dashes are added by javascript. This is not perfect yet but it works pretty decently.
10. Offer slides out after user accepts it.
12. Offer starts invisible and then is made visible by javascript.

[khaled]

To change the delay before the coreg offer slides in on the video watch page:

Add system variable : 'coreg_offer_appear_time'
Set it to be the number of millisecond before the offer should appear (i.e. 1000 = 1 sec).
This is done from the Admin Tools->System Variables menu

It defaults to 3 seconds if not set.