Difference between revisions of "ChannelTracking"
(first cut at new task by Ward with John's assistance) |
Arif Iqbal (talk | contribs) (Added the missing noinclude taag) |
||
|
(7 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
<noinclude><big>[[OurWork]] < [[DevelopmentTeam]] < [[DevelopmentTeamPriorities|Priorities]] < </noinclude>('''[[PairDays?|?]]''') [[ChannelTracking]] ('''[[Who?|?]]''') {{JustTinyEditIcon|ChannelTracking}}<noinclude></big> | <noinclude><big>[[OurWork]] < [[DevelopmentTeam]] < [[DevelopmentTeamPriorities|Priorities]] < </noinclude>('''[[PairDays?|?]]''') [[ChannelTracking]] ('''[[Who?|?]]''') {{JustTinyEditIcon|ChannelTracking}}<noinclude></big> | ||
__NOTOC__ | __NOTOC__ | ||
== What (summary) == | == What (summary) == | ||
| − | AdSense can attribute ad revenue to "channels" that are setup on the AdSense website. This project is to | + | AdSense can attribute ad revenue to "channels" that are setup on the AdSense website. This project is to associate AdSense channel ids with <portal-tracking> names and to emit those ids on AdSense of content codes. |
| − | It is assumed that portals will have their own channels. Our [[Content Team]] will manage AdSense channels and | + | It is assumed that portals will have their own channels. Our [[Content Team]] will manage AdSense channels and use a staff-only compost interface to bind names to ids. Not all portal names will have ids but no id will be emitted without being associated with a portal name and that name appearing in a <portal-tracking> tag. |
https://www.google.com/adsense/code | https://www.google.com/adsense/code | ||
| + | |||
| + | AdSense limitations allow for up to five channels attributed with one ad code, and on the order of 190 channels total. This means that channels cannot be used to track revenue for our portal sponsors once we have more than 190 sponsors. | ||
| + | |||
| + | :[[Image:AdSenseChannelLimit190.png]] | ||
| + | |||
| + | AdSense limitations also mean that we will only track the first five ids that we encounter on any page. That is, if aboutus.org is part of eight portals, at most five of these can have ad revenue attributed to their corresponding channels | ||
== Why this is important == | == Why this is important == | ||
| Line 17: | Line 22: | ||
* We will know that this is done when the content team can ... | * We will know that this is done when the content team can ... | ||
** create a new channel, | ** create a new channel, | ||
| − | ** tag pages with a channel | + | ** tag pages with a channel id |
** see revenue the next day that is attributed to that channel. | ** see revenue the next day that is attributed to that channel. | ||
| + | |||
| + | * We must test that multiple channels are handled properly | ||
| + | |||
| + | * We must also check that ad revenue attributed to channels is not subtracted from our current reports. We believe this to be the case but must check too. | ||
== Steps to get to [[DoneDone]] == | == Steps to get to [[DoneDone]] == | ||
| − | + | * create a database table for associating portal names with ids | |
| + | * create a CRUD interface to this table with the same access restrictions as our credit-card transaction interface | ||
| + | * emit ids as a variable definition that can be examined by our skin | ||
| + | * modify our google ads to include channel id info (see below) | ||
| + | * test by ... | ||
| + | ** changing channels, and | ||
| + | ** changing other ad parameters that are recorded elsewhere in aboutus software | ||
| + | |||
| + | == AdSense code format == | ||
| + | |||
| + | This project requires understanding and dynamically modifying AdSense generated code. This appears to be straightforward since hand generated code with multiple channels has these included into the add code with the reasonably obvious addition: | ||
| + | ://2007-12-31: Portland Tech, AboutUs.org | ||
| + | :google_ad_channel = "5511508489+2208325199"; | ||
| + | Presumably the comment is optional and the 5511508489+2208325199 part would be constructed from the ids associated with all applicable portal-tracking tags. | ||
</noinclude> | </noinclude> | ||
Latest revision as of 06:39, 1 January 2008
What (summary)
AdSense can attribute ad revenue to "channels" that are setup on the AdSense website. This project is to associate AdSense channel ids with
Why this is important
Channel tracking gives us the ability to relate ad revenue to the effort we expend to earn it (ROI).
DoneDone
- We will know that this is done when the content team can ...
- create a new channel,
- tag pages with a channel id
- see revenue the next day that is attributed to that channel.
- We must test that multiple channels are handled properly
- We must also check that ad revenue attributed to channels is not subtracted from our current reports. We believe this to be the case but must check too.
Steps to get to DoneDone
- create a database table for associating portal names with ids
- create a CRUD interface to this table with the same access restrictions as our credit-card transaction interface
- emit ids as a variable definition that can be examined by our skin
- modify our google ads to include channel id info (see below)
- test by ...
- changing channels, and
- changing other ad parameters that are recorded elsewhere in aboutus software
AdSense code format
This project requires understanding and dynamically modifying AdSense generated code. This appears to be straightforward since hand generated code with multiple channels has these included into the add code with the reasonably obvious addition:
- //2007-12-31: Portland Tech, AboutUs.org
- google_ad_channel = "5511508489+2208325199";
Presumably the comment is optional and the 5511508489+2208325199 part would be constructed from the ids associated with all applicable portal-tracking tags.