Any thoughts about this data being saved with a registration rather than with submission of a webform?

Suppose any "conversion goal" action might want to trigger storing this info.
Landing on a node and downloading a file, reading the article or adding the product to your cart all might constitute a great time to snag the visitor path.

Thanks.

Comments

doublejosh’s picture

doublejosh commented

Still love the concept of this module, but wondering again about other conversion goals. Mentioned previously user registration, but also now (for another project) thinking about node creation specifically in conjunction with the UberCart Node Checkout module.
That implementation of node creation could store valuable path data when filling out an e-commerce order. But with generic node creation it would be useful on sites where the first action upon registation is creating a node like so many Drupal web type projects. For example: forum topic, blog post, or any other digital creation.

May take this one on since this module would be SOO useful for marketing data without using a third party like Eloqua or Salesforce.

Will post here if so. Anyone?