canmove, Confirmed users
640
edits
CloudServices/Roadmaps/Campaign-Manager: Difference between revisions
Jump to navigation
Jump to search
CloudServices/Roadmaps/Campaign-Manager (view source)
Revision as of 01:24, 26 October 2012
, 26 October 2012no edit summary
No edit summary |
|||
| Line 146: | Line 146: | ||
* TODO: which redirect code will avoid duplicate hits and not screw up caches? | * TODO: which redirect code will avoid duplicate hits and not screw up caches? | ||
** Currently using a reasonably meaningless ID based on campaign creation time + random value. (e.g. "1tjzaJ112") | ** Currently using a reasonably meaningless ID based on campaign creation time + random value. (e.g. "1tjzaJ112") | ||
** rnewman: I meant "which HTTP redirect response code". | |||
* TODO: do we have a query param on the redirector to allow tracking? Talking with JR I think we do | * TODO: do we have a query param on the redirector to allow tracking? Talking with JR I think we do | ||
** Not so sure about that. The tracking param would be integrated into the click URL (e.g. the many redirectors out there that then boot to a proper URL) | ** Not so sure about that. The tracking param would be integrated into the click URL (e.g. the many redirectors out there that then boot to a proper URL) | ||
** Put it this way: when Firefox hits the redirector URL, it will not be including the platform/version/channel etc. information that you need to compute clickthrough rates. You need to add a parameter to the redirector URL returned in each snippet, which could feasibly be the chunk of URI that arrived with the request. | |||
= Operations = | = Operations = | ||